←back to thread

288 points moonka | 1 comments | | HN request time: 0.21s | source
Show context
rqtwteye ◴[] No.43562536[source]
I have been in the workforce for almost 30 years now and I believe that everybody is getting more squeezed so they don’t have the time or energy to do a proper job. The expectation is to get it done as quickly as possible and not do more unless told so.

In SW development in the 90s I had much more time for experimentation to figure things out. In the last years you often have some manager where you basically have to justify every thing you do and always a huge pile of work that never gets smaller. So you just hurry through your tasks.

I think google had it right for a while with their 20% time where people could do wanted to do. As far as I know that’s over.

People need some slack if you want to see good work. They aren’t machines that can run constantly on 100% utilization.

replies(25): >>43562590 #>>43562601 #>>43562738 #>>43562748 #>>43562796 #>>43562875 #>>43562911 #>>43562955 #>>43562996 #>>43563116 #>>43563121 #>>43563253 #>>43563309 #>>43563487 #>>43563727 #>>43563795 #>>43563837 #>>43563965 #>>43563995 #>>43564861 #>>43567850 #>>43569250 #>>43569941 #>>43574512 #>>43579456 #
Sparkyte ◴[] No.43562911[source]
Definitely squeezed.

They say AI, but AI isn't eliminating programming. I've wrote a few applications with AI assistance. It probably would've been faster if I wrote it myself. The problem is that it doesn't have context and wildly assumes what your intentions are and cheats outcomes.

It will replace juniors for that one liner, it won't replace a senior developer who knows how to write code.

replies(2): >>43562958 #>>43592816 #
sumedh ◴[] No.43592816[source]
> The problem is that it doesn't have context

You are supposed to give it context, if you dont provide it context how will it know what its supposed to do?

replies(1): >>43599807 #
1. Sparkyte ◴[] No.43599807[source]
I really wish that was the case. You can give it only so much context before it starts to go down a path where the context doesn't even make sense to it, and yet if you explained it to a colleague they would instantly understand.

Context has layers and really 1st or 2nd layers ever get reached by AI but it can't dive further because it is too focused on the final output rather than the continuation of the output.

For example you write code and then tell it what the final expect output is, it some how always divorces itself from rudimentary implementations and poops out something that cut a lot holes out or shortcuts all of your work. Removes modularity in favor of that immediate outcome. AI is just not good enough to understand the complex relationship of maintainable code and deliverable code. So it poops out what is easily made to meet the deliverable.