You're wrong
1,288 karma · joined April 12, 2018
You're wrong
That people ARE making, surely not machines. Like Terence Tao or Knuts did using the tool to their advantage, for example it would have been impossible for me to prove the same thing Tao did with an LLM. Same reason I believe programmers won't go away
That’s just a gigantic bs you wouldn’t be able to stir an ai without code writing knowledge this approach in the long term we will make all of you shilling people go back to hand code crucial parts of the business logic
Have you ever asked yourself maybe you’re not that good and you can still learn and improve and be relevant?
We must live in two different worlds, it must be like that
Maybe you have fun saying if it converts better or not! I'm fan of a/b testing
If you do let me know ;)
Most of these things are just true as of today.
> You protect your job by learning how to use new tools as the technology advances.
Sure and the more you learn the more you see how hyped they were and reality untangle
> Engineers don't ask a tool to write code.
And what they ask? They create loops or graphs? These tools ultimately vomit code anyways
> one-shot secure, performant code.
I call it reverse skill issue; it feels secure and performant because you can't verify properly, it feels right but it's actually broken in many nuanced ways. You can measure performance and produce a broken measurement as well. It's not as simple as you make it
Tangential uses of the dom, the core app is on the canvas
> I don't use Google Chrome.
Who cares? They have an almost monopoly and they dictate what to implement on the web, it's already happening that many sites don't work on firefox because they've been only optimized for Chrome. And btw Firefox will implement manifest v3 as well. If you're not using Firefox or Safari you're still using chromium. We don't even have the capability anymore of developing alternative browser engines, the spec is a monster and the various attempts are still very far away.
> No one has decided this, it just happened because web browsers were in the right place at the right time
Exactly and since this is the current reality I don't see why we couldn't have better browser tooling for rendering near native stuff like we do on desktop frameworks. Developer tooling for the desktop already exists since ages but web folks have injected desktop apps as well with bloated stuff like electron
> My web browser is my agent
It's very likely not anymore, otherwise Chrome wouldn't have pushed for manifest v3
> I wish Figma and Google Docs were just offline-usable desktop applications.
I wish this too, but since we have decided app distribution to be web based, we need serious tools for making serious apps
A total nightmare and imo every dev should push back using this stuff. You'd otherwise have management brag about you not being a good communicator with the ai agent, the same management that have no idea how to steer these tools.
I really like Zed the editor, I'm not sure I like the path they getting into
I dunno sometimes I think I should have sticked with a simpler solution coded by hand with more tradeoffs, than trying doing more and spend days back and forth in an endless feedback loop. Or fighting back the Agent that is more than happy to over produce.
IMO the problem is not the single developer using more agentic tooling, it's the whole work chain, who reviews your changes use agentic tooling assistance and over produce a lot of feedback and you're back with the clanker making many decisions that just drains you at the end of the day. I miss the times where we released many more simple things sith many more tradeoffs and business decisions