221–230 of 323 posts
Earlier quoted context omitted.
There is nothing wrong with first year junior code that does the job.
Does not. Do you know my requirements? This is actually in a time critical path.
If you hadn't told me that I would also not have bothered optimizing syscalls.
Did you tell the AI the profiler results and ask for ways to make it faster?
Earlier quoted context omitted.
I think some of the suspicion is that it's really not 10x in practice.
Like AI could write code perfectly as soon as I thought of it, and that would not improve my productivity 10x. Coding was never the slow part. Everything that goes around coding (like determining that the extra load here is not going to overload things, getting PMs to actually make their mind up what the feature is going to do, etc.), means that there's simply not that much time to be saved on coding activities.
Btw, AI doesn't just code, there are AIs for debugging, monitoring etc too.
This is extremely fascinating and finally something that feels extremely tangible as opposed to vibes based ideas around how AI will "take everyone's jobs" while failing to fill in the gaps between. This feels extremely gap filling. I find it quite interesting how we can do a very large chunk of the work up front in design, in order to automate the rest of the work. Its almost as if waterfall was the better pattern a…
Waterfall has always been the best model as long as specs are frozen, which is never the case.
Earlier quoted context omitted.
My current favourite LLM wankery example is this beauty: https://blog.fahadusman.com/proxmox-replacing-failed-drive-i... Note how it has invented the faster parameter for the zpool command. It is possible that the blog writer hallucinated a faster parameter themselves without needing a LLM - who knows. I think all developers should add a faster parameter to all commands to make them run faster. Perhaps a LLM could cr…
How can this article be written by LLM? Its date is November 2021. Not judging the article as a whole but the command you pointed out seems to be correct. Faster is the name of the pool.
Earlier quoted context omitted.
Does not. Do you know my requirements? This is actually in a time critical path.
Well, that wasn't in your comment. :P If you hadn't told me that I would also not have bothered optimizing syscalls. Did you tell the AI the profiler results and ask for ways to make it faster?
Acting like a LLM now :P
> Did you tell the AI the profiler results and ask for ways to make it faster?
Looking for ways to turn a 10 minute job into a couple days?
The premise might possibly be true, but as an actually seasoned Python developer, I've taken a look at one file: https://github.com/dx-tooling/platform-problem-monitoring-co... All of it smells of a (lousy) junior software engineer: from configuring root logger at the top, module level (which relies on module import caching not to be reapplied), over not using a stdlib config file parser and building one themselves,…
> However, my broad understanding of software architecture, engineering best practices, system operations, and what makes for excellent software projects made this development process remarkably smooth.
If the seniors are going to write this sort of Python code and then talk about how knowledge and experience made it smooth or whatever, might as well hire a junior and let them learn through trials and tribulations.
Earlier quoted context omitted.
Waterfall has always been the best model as long as specs are frozen, which is never the case.
sure, but if you're generating the code in a very small amount of time from the specs then suddenly its no longer the code that is the source, its the specs. That's what waterfall always wanted to be and it failed because writing the code usually took a lot longer than writing the specs, but now perhaps, that is no longer the case.
Earlier quoted context omitted.
But you said "I can now whip up a serious contender to any SaaS business in a week". Any SaaS business. In a week. And to be a "serious contender", you have to have feature parity. Yet now you're shifting the goalposts. What's stopping you? There are 38 weeks left in 2025. Please build "serious contenders" for each of the top 38 most popular SaaS products before the end of the year. Surely you will be the most succes…
The rest of the business is the issue. I can whitelabel a Spotify clone but licensing rights and all that business stuff is outside my wheelhouse. An app that serves mp3s and has a bunch of other buttons? yeah, done. "shifting goalposts?" no, we're having a conversation, I'm not being deposed under a subpoena. My claim is that in a week you could build a thing that people want to use, as long as you can sell it, that…
Spotify is not the audio player widget in some user interface. It started off as a Torrent-like P2P system for file distribution on top of a very large search index and file storage. That's the minimum you'd build for a "whitelabel [...] Spotify clone". Since then they've added massive, sophisticated systems for user monitoring and prediction, ad distribution, abuse and fraud detection, and so on.
Use that code generation platform to build a product off any combination of two of the larger subsystems at Spotify and you're set for retirement if you only grab a reasonable salesperson and an accountant off the street. Robust file distribution with robust abuse detection or robust ad distribution or robust user prediction would be that valuable in many business sectors.
If building and maintaining actually is that effortless for you, show some evidence.