parpfish
i'll have a specific technical architecture in mind -- API specs, a list of cloud services, a general idea about how code should be broken into modules. i'll write it all out and let the pieces get filled in by AI.
it's not really 'vibe coding' as the term was originally envisioned where you just describe a top-level goal (e.g., "make me a new version of minecraft. no mistakes please."). it's a different level of abstraction where the models are primarily doing implementation and not design.
for me this lets me do the fun parts of designing software BUT i don't have to slog through documentation and learn a bunch of DSLs to get it going.
really? i feel like the overwhelming sentiment in every comment section is staunchly anti-ai. it's far more common to see people lamenting their job prospects or complaining about having to review mountains of slop PRs.
https://disknoice-655ee8.gitlab.io/
it's got the right noises and i believe that they are synced up with real disk usage, but it doesn't quite feel the same because i think disk usage patterns have changed over the last 20-some years.
when mathematicians complaining about losing the part of the job that they love, people think "if you love doing it, why is anybody paying you? you're describing a hobby."
I'd win because I could remove the late-night impulse buys and de-duplicated things added by multiple family members.
They win because it simplifies shipping logistics/packaging and actually encourages more loose/impulse driven buying ("just add it to the cart, we'll review it later").
that's not a crazy amount if you think about the potential ROI of a few of these meetings vs. blowing money on an ad campaign.
there's no way that its this cheap to buy our representatives, which is why im convinced that looking at on-the-books campaign donations is a red herring.
if we're on the former path, you're right. if we're on the later, there comes a point where continued work in automation isn't cost effective and we keep the humans around to handle all the hard 'edge cases' like urban driving to the final warehouse
This either means that a) buying our elected officials is cheap or b) we’re not looking in the right place to see the actual transactions.
A much more likely (and hard to regulate) form of corruption is “back-door lobbying” where there isn’t a clear payment now but a promise of bigger payment in the future. Such as “you helped our industry do X, so once you retire from congress we’ll reward you with a high layer do—nothing consultant’ role”.
those drivers could spend their lives working locally (and sleepin at home), develop deep regional expertise, and be able to handle the hardest part of the job without the fatigue from a cross-country drive.
but there's a strong cultural bias to judge people that wake up at 11am as lazy. and people that stay up to 4am are reckless.
but somebody that slept the same seven hours from 11pm-6am is pragmatic and responsible.
staying up late rocks. its the funnest. why would i give that up? just to pay attention better at work? no thanks.
those people need to know that extraverts are also awkward and shy, but they've practiced their social skills so over time that gets better.
What you actually need to do is have a manager lead assert that it’s happening in a top down way and just run the formatter with the defaults. Let people argue case-by-case on what to change after that.
I think they were against over engineering because they were constantly firefighting bugs and didn’t have time to thoughtfully review.
there’s all the code correctness stuff that we all love. But the biggest benefit is making it so much easier to maintain other parts of the stack.
Following a stack trace into somebody else’s functions and you see that the args are completely untyped or just a bunch of ‘dict[str, Any]’ is the worst. But if you see those inputs as more narrowly typed data classes it makes it so much easier to grok what the function is supposed to do
If a business markets itself with these AIgen posters, you get wildly different responses from different groups.
boomers that spend all their time on Facebook will think “this is such a nice pretty poster” and be oblivious to the fact it is even ai. Even if they knew it was ai they don’t care.
Young people will think it is low class/trashy. Some hate it because it’s ai, others hate it because the poster is ugly/busy/confusing.
you like typing out the code, but i see that as the drudgery that I have to slog through after the fun of drawing architecture diagrams and writing out the api specs.
let a whole ecosystem of music streaming apps take off that cater to different niches of listeners.
each app would be able to differentiation themselves with their UI but also features like recommendations/playlists/etc. And spotify wouldn't see them as competitors because they'd still be getting their cut because they all go through their API.