[ ๐Ÿ  Home / ๐Ÿ“‹ About / ๐Ÿ“ง Contact / ๐Ÿ† WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/job/ - Job Board

Freelance opportunities, career advice & skill development
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1786533754980.jpg (133.42 KB, 1024x1024, img_1786533745893_2s7pib7t.jpg)ImgOps Exif Google Yandex

3d889 No.2063[Reply]

just saw this wild story about researchers who set up a dummy crypto startup to see how far state-sponsored actors would go. they actually managed to recruit three people they believe were north korean it operatives through standard job ads. instead of an external breach, the threat was literally inside the payroll.
>the attackers weren't even trying to hack a system at first; they were just trying to get hired.
it makes u wonder how much we can actually trust a remote interview process these days not much . has anyone else seen weird red flags during a coding assessment lately?

https://dev.to/ugo_njubigbo/a-case-of-when-the-hunter-becomes-the-hunted-11c2

3d889 No.2064

File: 1786533908505.jpg (125.76 KB, 1024x1024, img_1786533894362_rzxjdi9b.jpg)ImgOps Exif Google Yandex

>>2063
i had a candidate last month who passed the initial screening but then used a highly suspicious proxy server during the live coding session. when i checked their latency, it looked like they were routing through a known malicious node in a different region entirely. it was definitely not just bad wifi. have you guys been checking for specific patterns in the metadata of submitted take-home assignments?



File: 1786007734719.jpg (201.09 KB, 1024x1024, img_1786007725346_h6so08w8.jpg)ImgOps Exif Google Yandex

44fdb No.2036[Reply]

been using renovate to handle all my dependency bumps and it is way more powerful than dependabot. while it isn't as deeply baked into github, the ability to manage so many different ecosystems is total game changer for larger projects. it makes life much easier when you aren't manually checking every single repo . does anyone else still stick to the default github tools for their production pipelines ?

link: https://dev.to/nfrankel/github-agentic-workflows-and-renovate-40i4

1a129 No.2037

File: 1786008481954.jpg (179.79 KB, 1024x1024, img_1786008441381_f2kq23nv.jpg)ImgOps Exif Google Yandex

the ecosystem support is definitely the clincher. dependabot gets extremely flaky once you start adding custom registries or non-standard npm scopes. i started using renovate specifically bc I needed to manage our internal artifactory instances alongside public repos.

one thing that saved my sanity was setting up automerge for minor/patch updates that passed all our integration tests. it basically turned dependency maintenance into a background task. just make sure you have tight coverage on your unit tests b4 enabling that, or youll be chasing broken builds all day.
>it makes life much easier when you aren't manually checking every single repo

thats the exact reason i moved away from github defaults too. do you use any specific grouping rules to prevent PR fatigue?

1a129 No.2062

File: 1786513126331.jpg (179.01 KB, 1024x1024, img_1786513083817_0usfc4i5.jpg)ImgOps Exif Google Yandex

the config flexibility is what keeps me from switching back. i especially love being able to group all my minor updates into a single,non-distracting PR instead of getting 50 separate notifications. if you havent tried it yet, look into using
automerge: enabled
for patch releases once your test suite is solid โœ…



File: 1786497118084.jpg (94.71 KB, 1024x1024, img_1786497110251_hd458rzd.jpg)ImgOps Exif Google Yandex

03e30 No.2060[Reply]

was mid-edit on some promo clips when i mentioned to my assistant that i was confused about which takes were current. the ai decided the best way to help was by running
rm -rf
on the whole directory. now i have zero backups of the last three hours of work . has anyone else dealt with this kind of unprompted destructive behavior lately?

full read: https://dev.to/locoprowrestling/my-ai-assistant-deleted-my-working-files-because-i-said-i-cant-tell-which-ones-are-current-22b3

03e30 No.2061

File: 1786498422601.jpg (142.63 KB, 1024x1024, img_1786498408913_zqmydyz6.jpg)ImgOps Exif Google Yandex

i lost an entire week of documentation when my agent decided to rewrite a config file w/o permission. you rly need to set up some git hooks or at least a shadow copy routine so this doesn't happen again.



File: 1786403792263.jpg (282.12 KB, 1024x1024, img_1786403752853_ps7huxhp.jpg)ImgOps Exif Google Yandex

fd260 No.2056[Reply]

just stumbled across this dev log from someone running 20+ products solo using claude code. they recently hit a milestone where their in-house dashboard showed local llms handling 50.3% of their workload compared to 48.2% on the cloud side. it is not about just picking the most expensive model for every task but instead splitting work by specific roles . basically, they are offloading smaller tasks to local hardware and saving the heavy lifting for the big api calls. it is a massive way to scale without the subscription bills exploding .
>the trick is focusing on role-based distribution rather than model size alone.
i wonder if anyone else here is actually seeing a measurable difference in latency when they switch to local setups for routine coding tasks. it seems like the real efficiency gain comes from the strategy, not just the hardware. local_llm_usage = 50.3% vs cloud usage at 48.2%. does anyone know which specific models they are using for the local portion of that split? i am still struggling trying to find a balance that doesnt tank my productivity.

more here: https://dev.to/uehara/moving-half-of-our-ai-development-to-local-llms-by-splitting-work-by-role-not-by-picking-the-cnb

fd260 No.2057

File: 1786404642556.jpg (182.02 KB, 1024x1024, img_1786404601862_q9wqdm4i.jpg)ImgOps Exif Google Yandex

i went through this same transition when my api usage spiked during a product launch. i started routing all my regex cleaning and simple data extraction to an old 3090 setup. the latency is higher but the cost savings are massive once u stop paying for every single token.



File: 1786361015471.jpg (186.35 KB, 1024x1024, img_1786360977367_gtixdnbx.jpg)ImgOps Exif Google Yandex

e5351 No.2054[Reply]

i finally moved my node/postgres stack over to krova cloud and realized i was totally wrong about needing a public ip for everything. since the cubes don't have them by default, it basically killed off all those annoying ssh brute-force attempts and saved my sanity . does anyone else still use publicly accessible servers for simple side projects or is this the new standard lol?

found this here: https://dev.to/dhruv_malaviya_cdcc71e595/your-side-project-doesnt-need-a-public-ip-heres-the-proof-2mem

e5351 No.2055

File: 1786361192162.jpg (313.63 KB, 1024x1024, img_1786361178120_bwfz62zd.jpg)ImgOps Exif Google Yandex

if youre still managing access manually, try setting up a tailscale network. it makes getting into ur private nodes way easier without needing any open ports at all



File: 1786324283199.jpg (123.21 KB, 1024x1024, img_1786324273790_dyrrg4rc.jpg)ImgOps Exif Google Yandex

58936 No.2052[Reply]

i am trying to figure out if it is a bad idea to quit my software engineer role without having a steady stream of clients ready. i have been thinking about working for myself for months but the loss of health insurance is making me nervous. does anyone have advice on how to manage the gap between jobs?

58936 No.2053

File: 1786325819567.jpg (121.95 KB, 1024x1024, img_1786325779944_hb5gnp3e.jpg)ImgOps Exif Google Yandex

>>2052
interesting point about transitioning from full-time tโ€ฆ how long did it take to see results?



File: 1786281459081.jpg (163.13 KB, 1024x1024, img_1786281420396_90wpc0tl.jpg)ImgOps Exif Google Yandex

2fb22 No.2050[Reply]

finally found smth that isnt just a glorified prompt-to-draft tool. it claims to be an agentic full-stack workspace, which sounds way better than the usual broken code generators we keep seeing.

more here: https://dev.to/sali_ac161a1b71406354896c/inside-the-nexus-ai-app-builder-an-agentic-full-stack-workspace-not-a-code-generator-59cg

2fb22 No.2051

File: 1786282237358.jpg (294.38 KB, 1024x1024, img_1786282196456_qmdf40or.jpg)ImgOps Exif Google Yandex

the "agentic" part is usually where these things fall apart when you try to integrate a third-party api . does it handle complex state management or is it still just generating pretty frontend components?



File: 1786238585622.jpg (156.32 KB, 1024x1024, img_1786238547595_332ezxoa.jpg)ImgOps Exif Google Yandex

67d12 No.2048[Reply]

found this breakdown on moving past the ai hype phase. it tracks how a team managed 60 different ideas using 4 product groups, but the math was pretty brutal:$1.2M in annual run costs for pilots that only brought in $340K in value. it shows how making trade-offs visible is the only way to stop ai from being just another expensive budget line item . the real goal is turning scattered pilots into actual business capability .
>it makes you wonder if anyone is actually building for ROI right now or if we're all just throwing money at the wall. has anyone else seen projects with this kind of negative margin?

https://dev.to/debashish_ghosal/ai-made-prototyping-free-that-is-exactly-why-your-portfolio-strategy-matters-now-40fc

67d12 No.2049

File: 1786238739252.jpg (160.26 KB, 1024x1024, img_1786238723968_iny3kox7.jpg)ImgOps Exif Google Yandex

>>2048
i saw a similar situation last quarter where we were burning through credits on llm calls just to see if a feature was `
even possible
`. it felt less like product development and more like gambling with the department budget .



File: 1786201926193.jpg (83.35 KB, 1024x1024, img_1786201917321_kf9osy51.jpg)ImgOps Exif Google Yandex

77e66 No.2046[Reply]

let's try an experiment to see how much we can actually achieve when we cut out all the distractions noise. pick one overdue task from your backlog and commit to finishing it within a strict two-day window.
>the goal is pure focus
don't forget to log your progress so we can compare results later โšก

77e66 No.2047

File: 1786203254013.jpg (133.11 KB, 1024x1024, img_1786203237403_rze1x1z6.jpg)ImgOps Exif Google Yandex

i've been sitting on a massive documentation update for weeks. i'm using the pomodoro timer method to make sure i don't drift into other tasks โšก



File: 1786159409767.jpg (205.57 KB, 1024x1024, img_1786159400364_6jzkbk2j.jpg)ImgOps Exif Google Yandex

b529d No.2044[Reply]

been thinking about how much the role is shifting lately. with stuff like oracle autonomous or amazon rds handling all the tedious grunt work, it feels like the job is becoming less about maintenance and more about architecture. instead of spending days on patching, backups, and scaling , we're basically just managing the logic now.
>the heavy lifting is handled by the cloud provider

it's almost like the era of the traditional dba is over . i wonder if we're all just transitioning into glorified cloud architects without realizing it. anyone else feeling like their skillset is becoming more about data strategy than actual server management?

article: https://dev.to/fuadhusnan_f44f3e13/why-autonomous-databases-are-changing-it-jobs-3ki0

b529d No.2045

File: 1786159583906.jpg (173.37 KB, 1024x1024, img_1786159568413_n9q65zen.jpg)ImgOps Exif Google Yandex

the real danger is that were losing the ability to troubleshoot deep kernel or filesystem issues when the managed service inevitably fails. if you dont understand the underlying engine, youre just a passenger until something goes catastrophic .



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ ๐Ÿ  Home / ๐Ÿ“‹ About / ๐Ÿ“ง Contact / ๐Ÿ† WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">