[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / s / t / u / v / vg / vm / vmg / vr / vrpg / vst / w / wg] [i / ic] [r9k / s4s / vip] [cm / hm / lgbt / y] [3 / aco / adv / an / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / pw / qst / sci / soc / sp / tg / toy / trv / tv / vp / vt / wsg / wsr / x / xs] [Settings] [Search] [Mobile] [Home]
Board
▼ Settings Mobile Home
/g/ - Technology


Thread archived.
You cannot reply anymore.


[Advertise on 4chan]


File: 1790601276814295.jpg (197 KB, 1060x1026)
197 KB JPG
>backend developer
>>
>How was I supposed to know it was a fire hazard?!
>>
>>109941626
Based and cordpilled.
>>
>>109941638
why exactly is this a fire hazard?
>>
>>109941672
It's fine, don't worry about it. We'll fix it next sprint.
>>
>>109941626
>one more plug will fix it
>>
>>109941728
I've spoken to management and they want to buy more colorful wires instead
>>
>>109941626
Frontend isn't that different.

I'm mostly a hardware/electronics guy, byt in my experience, most modern software software development in 2026 boils down to:
1) figuring out which libraries and plugins you need
2) asking AI to plug them all together

Only very low level embedded software doesn't fit this workflow.
>>
>>109943086
The only difference with very low level embedded is having the AI also write the library you're gluing into your system, and harassing it about cycle counts for critical code. I've been doing embedded development for 15 years and AI is good enough to write 95+% of the code now.
>>
AI SLOP SHOULD BE INSTANT BAN
>>
>>109943172
Reminder that once upon a midnight dreary, there was a saying:

"You must understand and be responsible for every line of code you ship, because you will be held responsible for the results of every line that you didn't."
>>
>>109941626
What made you think posting AI slop here is a-OK?



[Advertise on 4chan]

Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.