[ale]

The good and bad aspect of this approach to AI in tech is that it revealed really how many developers out there are merely happy with getting something to work and get it out the door before clocking out and not actually understanding the inner workings of their code.

[csmantle]

This is almost inevitable when something industrializes; people maximize profit by quickly shipping things that barely works. We need someone who try to excel in technology, and AI just amplifies this need.

[petesergeant]

> how many developers out there are merely happy with getting something to work and get it out the door

There's a very large number of cases where that's the right choice for the business.

[worldsayshi]

Also for small cli tools and scripts that otherwise wouldn't get written.

[bagacrap]

Except that "to work" really means "to seem to work on the first try"

[troupo]

I find it to be actually a boon for small throw away side projects that I don't care about, and just want to have [1]

Actual code/projects? Detrimental

[1] E.g. I spent an evening on this: https://github.com/dmitriid/mop

[almostgotcaught]

whenever people complain about someone being "merely happy with getting something to work and get it out the door before clocking out" i wonder to myself if i'm dealing with someone that has The Protestant Ethic and the Spirit of Capitalism on their nightstand, or has never read Economic and Philosophic Manuscripts of 1844, or simply does not understand the significance of these two essays.

like ... you expect people to actually be committed to "the value of a hard day's work" for its own sake? when owners aren't committed to value of a hard day's worker? and you think that your position is the respectable/wise one? lol

[Dylan16807]

Where did they say anything about a "hard day's work"? Are you making up arguments to attribute to them, lol

And are you assuming the alternative involves not clocking out? Because "clock out, finish when there's more time" is a very good option in many situations.

[hansmayer]

No, it's not about capitalism and exploitation, hard work propaganda etc. You can work to the contract (e.g. strictly whats in your work contract and not "above and beyond") while still retaining the quality of the work. So reduce the quantity but not the quality. This is about a ton of bootcamp developers that were created in the last 10ish years, for which, unlike the rest of us, it is just a better paid job.

[hitarpetar]

in general it's safe to assume your conversation partner has not read every single essay you have and come away with the same exact thoughts

[zdragnar]

Given the remainder of the comment is "and not understanding the inner workings" it's safe to assume that "getting something to work" does not imply that it worked correctly.

Back in the days of SVN, I'd have to deal with people who committed syntax errors, broken unit tests, and other things that either worked but were obviously broken, or just flat out didn't work.

Taking a bit of pride in your work is as much for your coworkers as it is for yourself. Not everything needs to be some silly proles vs bourge screed.