I don’t like it, but that’s how im playing the game of life
2,195 karma · joined November 11, 2019
I don’t like it, but that’s how im playing the game of life
This is a feature, not a bug. Not for us (engineers), but for our bosses, ofc
It’s clear why it feels so good to use something like Lisp for personal projects. It’s also clear why the vast majority of companies don’t use it
- typically they are behind a single person. That’s usually bad because of spf
- typically they are achieved in a very short amount of time, so the author hasn’t acquired any discipline in creating the project. That means it’s unlikely the author is going to stick to the project in the mid and long term
- anyone that wants to contribute to the project needs to pay. Needs to pay tokens because it’s increasingly difficult to maintain these projects without AI
So, who wants to put something like this in production? Doesn’t make much sense
IMHO, this is a mistake. I guess we play with it because there’s isn’t anything better nowadays. Writing and maintaining “specs” in plain english is painful.
Why the email then? Wouldn’t a record of the decision (not via email , but in some confluence-like space) be enough? If the confirmation is really needed then a default action wouldn’t be possible, ofc
I don’t think i could have survived in this industry if I knew only 1 or 2 “stacks”.
I don’t think this scales. We recently have been doing “spec driven development” and we are committing the specs and prompts to our repo, alongside the generated code. At the beginning it seems fine: you wanna change something, you update the spec and ask the machine to regenerate the code. Easy. Over time, though, you have hundreds if not thousands if spec files in MD. It’s all English prose. There is duplication and subtle inconsistencies. It’s difficult to search for sections of a spec. Do you create a new file for this new requirement or update an existing one? What level of detail is enough here? Should I hint the machine about using the “saga” pattern or just let it know that we are dealing with non atomic transactions distributed across services? Etc. When a colleague opens a PR updating a spec, it’s hard to suggest objective changes (at least with code, you can demonstrate the presence of bugs… not so much with English prose. Sometimes I feel like a lawyer)
All in all, it seems as if maintenance of english prose is way worse than maintenance of actual code in big enough systems. You not only need to review the spec but also review the generated code. It’s painful
I doubt a large percentage of any user base is willing to do all of that
Nowadays is still that but it’s also a way to relax. Even though I don’t have accounts in the main social media networks (instagram, fb, twitter, youtube, etc) I still consume them indirectly on a weekly basis (e.g., i like to watch videoclips in YT, a friend sends me a twitter link, etc). It makes me anxious. I’ve realised that consuming in tiny bits (short videos, ads, stories, tweets, private messages, even going to those stores where everything is under $5) doesn’t suit me well, therefore reading regular books for at least 1-2h per day (plus other activities like working out alone, or going for a walk to a park) is becoming essential for my wellbeing.
Compare that to someone who doesn’t work in IT and needs to master the language to get a decent job. All in all, it’s better to speak English in Germany
And as systems become more complex with time, we will need more people with the title “software engineer”
- ads every now and then
- addictive shorts no one needs
- suggested videos nobody asked for
- geo ban of videos
That summarises pretty well the whole situation. AI is cool and all, but not worth it considering all the disadvantages
Any good resources you would recommend to learn more about this?
From my experience, a typical software engineer needs to understand the business (e.g., knowing who your users are), design a solution (e.g., we probably need an event-driven arch right here) and write the code (e.g., we should use select for update skip locked to avoid over claiming). They all are equally challenging imho
This is why I don’t understand why folks around here (that are employed) feel so enthusiastic about AI. We are going to be working more in a rush to produce stuff that we won’t be feeling as proud of as we did before AI. Unless you were in the profession for the money, the delights of crafting software simply go away and AI is pushing us closer to be just… well, I don’t know, but I don’t like it. Sure thing, if you are a CEO, this new state of things must be wonderful