Yeah, I grew up in rural area. Not “poor”, but population revenu was below average. Hard work was valued. Why would I have to give money for people who doesn’t work ?! Those lazy bastard just have to find a job. If someone is rich, it’s because he worked very hard and deserves it.
Oh boy what a moron I was…
I’m in my 40s now working for a huge company. The less I work, the more I’m paid…
Hi dude,
Well, “Here is my entirely generated LLM tool” is clearly a red flag. I’m a software engineer for 20 years, I’ll try to explain you why it is a redflag for developpers.
First, how many gallon of water and kg of coal were used to generate it ? Using LLM has a real hidden cost.
3500 lines of code written in 1 week… Professional developers write around 10 to 100 lines a day. Why ? Because understanding a system takes time. Here, there are 3500 lines no one is able to explain. “It works” doesn’t mean “It works”. Building a software is not just about making it work in your own use case.
Github like platforms were created to collaborate. It is not possible to collaborate on a vibe coded application. There are too many code that were written too quickly. And without the whole prompt history, the model used, etc… it is not even possible to do “collaborative vibe coding”. Another agent with another prompt history won’t have the full context of application, and won’t be able to keep consistency.
Now, github, gitlab, codeberg, etc… are flooded by these kind of app, generate by a single person in a few days on which it is not possible to collaborate. OpenSource maintainer are flooded by AI Slope code, and more and more project are forced to become closed source, or to restrict contributions only to some user.
The developer of a software is the worst person ever to test it. There are cognitive bias that make the developer unconsciously avoid scenarios that can break the system. If only one developer built a product, I’m 100% sure I won’t be able to build and run it on my computer without trouble. And again, every vibe-coded application were built by a single person.
If your tool works for you and your friend, cool. But the real value of a source code is not the source itself. It’s the people that worked on it, that built a common understanding, that ran it in several environment, with several use case, and that makes it robust. So don’t be mad if no one want to test your code.
Thanks for spelling 🙂
It’s not that I’m lazy, it’s that I more and more understand how recognition works. I use to be the kind of guys that did everything, doing extra hours to makes everything works smoothly. But the thing is if you do your job well, no one will notice you did anything.
Now I focus on visible things. I always over-evaluate my projects and let some easily fixable issues there and there to show how reactive I am.
Evaluate a 6 month project and deliver everything perfectly working in 7 month, you will just be yelled at for being late.
Evaluate the same project to 9 month. Deliver in 8, get feedback and fix the last issues in last month, everyone will be happy and will notice how reactive you are and how good your support is.
It’s not possible to apply this strategy in all domains, but it works for me. I always have very good appreciation from my management and regularly have bonus.