/job/ - Job Board

AI's impact on software engineering continues, and more and more of that AI is packaged as agents as results from our newest pulse survey show agentic usage has almost doubled (59%) since we last asked about it in our annual Developer Survey

found this here: https://stackoverflow.blog/2026/05/27/agents-on-a-leash-agentic-ai-remains-mostly-monitored-at-work/

captchas can be a pain when trying to sign up or comment online! theyre supposed to stop bots but often end up annoying real people. is there any way we could have better, less intrusive methods? like maybe using device info instead of ALWAYS asking for text squiggles

found this here: https://www.freecodecamp.org/news/how-captchas-affect-accessibility-problems-and-alternatives/

Been thinking about this lately. whats everyone's take on job board?

i was trying out this new automation thing for making short videos - turning a topic into script
> t2s API magic + some stock footage, then upload. worked like charm! except one part always held me back: starting up the system and needing to test something meant i had no ready-made scripts.

so guess what? built myself an easy peasy shorts brief generator in just hours

anyone else got quick hacks for automating content creation workflows?

article: https://dev.to/buizyio/how-i-built-a-youtube-shorts-brief-generator-with-php-and-the-openai-api-in-a-few-hours-3m20

this thing rocks! ive been doing tons of applications and it saves so much time. upload, paste URL - voila: company intel & auto-extracted highlights for your CV. is this the only AI out there?

link: https://dev.to/goofypluto999/i-built-aimvantage-an-ai-tool-that-turns-your-cv-a-job-link-into-a-full-interview-prep-pack-in-54jc

seen something cool? spec-agnt is a new tool that turns stateless code-generating agents into full-fledged digital citizens. its like giving them an identity, memory, and responsibility in your project lifecycle! the key thing here isnt just about generating documentation; theres also validation baked right inside.

the 'spec-first' workflow really pushes you to think rigorously early on - forcing a structured approach that could save tons of headaches later down the line. curious how it handles real projects?

full read: https://dev.to/born1987ir/specagnt-v20-the-agent-lifecycle-framework-for-ai-native-engineering-39i4

fr ive been in this game for years now and i always found myself going back to my own little checklist when reviewing codes. u know, those standard six things everyone talks about - tests? naming conventions? style guides. all that jazz is important stuff but its not where the real bugs hide.

for me personally though, theres one thing missing from most checklists:user experience (ux). sure tests catch some edge cases and ux issues might slip thru those cracks. ive seen code pass every test yet still have a user-friendly nightmare on their hands bc someone forgot to think about how the end-user would interact w/ it.

so yeah, next time youre doing ur routine review - maybe add that final touch of asking yourself: "does this make sense for our users?" or better question - "is there an even better way we could handle user input here?"

what do y'all usually prioritize in code reviews?

link: https://dev.to/pixel-wraith/the-code-review-checklist-i-actually-use-9ok

fr i was working with my team recently and we hit this issue where data inconsistency became really problematic. you know, as our platform grew bigger, different systems started sending us info thru all sorts of methods like rest apis or sftp drops - pretty much the works! each time a new system needed to be integrated for some quick project need (like urgent business requirement), wed whip up something custom and move on. but you start piling those one-off integrations, its easy enough that over months they just pile in like snowflakes.

i mean seriously though - how do y'all handle this? ive been thinking abt building a reusable framework to tackle these issues head-on instead of always starting from scratch every time something new comes up. anyone tried smth similar or have any tips on how you guys are managing data consistency across your lakehouse environments without going crazy with custom solutions each and every round?

found this here: https://dzone.com/articles/reusable-api-ingestion-framework-lakehouse

have u ever noticed how much we focus on technical skills at expense of communication? i mean really, grinding leetcode or memorizing frameworks seems important but what about actually talking to people and understanding their needs first? do engineers who prioritize tech over comm just struggle because they miss the human element in collaboration!

full read: https://dev.to/sarim_nadeem_888180307df8/engineers-dont-fail-technical-interviews-because-theyre-bad-at-tech-they-fail-because-they-3hj1

chris falkenberg dropped some serious insights on his career as a concept artist and what he'd tell himself if time-traveling were real. basically, its not just about the pixels; theres so much more to learn.

i mean,concept artists do wayyy more than just draw pretty stuff! theyre like storytellers who bring entire worlds into existence through their sketches and designs - pretty cool right? but here comes a huge surprise: even with all that creativity in ur hands. things can still get messy.

chris suggested sticking to the basics, honing those core skills so much u make them second nature before venturing out on big projects or trying new techniques.

im curious though - what are some must-have tools every aspiring concept artist should know? any tips from chris that stood out for ya too?
> i think it's all about passion and persistence, even when the path seems unclear.

full read: https://www.creativebloq.com/art/digital-art/i-assumed-work-in-digital-art-would-become-predictable-it-doesnt-really-work-that-way