81–90 of 151 posts
They don't seem to have a 'cohesive worldview'; additional context can easily sway them from one conclusion to the opposite conclusion. A large part of coding is about decision-making and prioritization; it's difficult to perform well at either of these tasks unless your worldview is internally consistent.
Vibe Coding is accelerating the death of documentation and architectural clarity. Companies are measuring success by tokens generated and time-to-prototype, ignoring the massive, hidden cost of cleanup/maintenance. The real skill is now cleanup, not generation.
You can start off just with documentation and then in the process check if the code is still in line with the documentation.
You can also generate documentation from the code. Then check yourself, if it fits.
I have been taking on "rescue" projects for a while through my business. Previously, the barely-functioning code was usually being generated via outsourcing agencies but it seems the new source is now going to be LLMs. I imagine it will be the same set of issues really. Just a different way of cost cutting measures. There can be good reasons to take shortcuts but, in my experience, the problems start when you're not…
I was thinking of doing something like that, but how does it work for the company in the end? If they vibe coded their project and now have shitty code full of bugs, you come in, fix the bugs and organize the code better and that's it? How do they continue to maintain it if they didn't have the knowledge to set it up in the first place?
Earlier quoted context omitted.
This. Based on what I have seen so far in my company so very anecdotal. Assuming they know and/or have the capability to do it, between the cost of correcting the issue and push to use AI into everything meaning raising any issue now, politically speaking, is a direct criticism of someone major VP pet projects. I personally simply started to log stuff. The first thing they need to do first is acknowledge there is a p…
There's definitely a lot of politics involved in such projects. So I've learned that a break is necessary between major engagements to decrease the risk of burnout. The environment that creates "rescue" projects is usually not one where long term thinking is prevalent. It would be a pet project of someone who's still there or someone who left but where the ultimate decision maker is still there. Either case, you need…
Other people who have more or a lot of experience with coding, help them and everybody profits in the end.
I understand that it becomes a problem with some businesses but others may profit too.
It's not all bad.
I wonder if vibe coding is a bit like DIY plumbing. You can do it yourself a bit and then later when water starts gushing all over your bathroom you hire an emergency plumber at a high fee. You learn a little more for next time.
FSV = full slop version
A while ago, I was having an intense and heated argument with a good friend in the Finance sector about whether AI would replace jobs. I informed him that AI can only do something repeatable, "already solved problems", or what I call "shit kicking work". His response was something to the effect that I was underestimating how many people's jobs were _entirely_ shit kicking work. To be fair to him, my partner who works…
>My response to both was that I was confident the market would fix this problem itself Based on..? >I cannot imagine that machines will ever replace any work where there is any meaningful threshold for "correct". Autopilot?
(In my opinion: Somewhat, almost and complete.)
I just take some kitchen paper and one of these small thin plastic bags to clean up after my own dog's shit. No need to pay for a service.
Just wanted to apologize for the shallow dismissal and the snark. This is going to generate cash flows so the associated activities are totally legit and not parasitic and a waste of oxygen. My gut reaction was not civilized.