591–600 of 800 posts
Earlier quoted context omitted.
But this learning is also value. Without playing around with it, you wouldn't know when to use an LLM and when not.
But the models change every 3-6 months. What's the use of learning what they can and can't do when what they can and can't do changes so frequently?
This is an industry that requires continuous learning.
Earlier quoted context omitted.
I didn't realize maximizing money is the way to achieve moral excellence. It's interesting how Puritanical the EA folks are
There is no moral excellence but which you invent for yourself. But given the first principle or goal of 'having the most impact', maximizing money is often quite useful.
It's a horrifying feeling facing the possibility that the career I spent so much time and money to get into is fading away. Sure, LLMs are not there yet, and they might not ever quite get there. But will companies start hiring again? If productivity has gone up, and it seems like it has, then no. So, a decade of hanging by a thread, getting by and doubling down on CS, hoping that the job market sees an uptick? Or try…
There is infinite amount of software to be made. Desires and wants never get satisfied. There will simply be more software, more features, more supported platforms, more bug checks, more tests, more CI/CD, more docs, more websites, more services, more more more. Once we solve something, we have a million new desires that we want to solve. There will be plenty of work in software, up until the time when really all kno…
Earlier quoted context omitted.
If you have to put in this much effort, why not just write it yourself?
When you write a library the first step is always designing it. LLMs dont get rid of that step, they get rid of the next step where you implement your design.
Earlier quoted context omitted.
> Feels like a false equivalency. It's clearly a textbook example of survivorship bias. In the 90s the same argument was directed at this new thing called the internet, and those who placed a bet on it being a fad ended up being forgotten by history. It's rather obvious that this AI thing is a transformative event in world history, perhaps more critical than the advent of the internet. Take a look at traffic to estab…
> In the 90s the same argument was directed at this new thing called the internet, and those who placed a bet on it being a fad ended up being forgotten by history. Allow me to introduce you to the dot-com boom, where everyone who bet on the internet went broke.
Earlier quoted context omitted.
How does a phased rollout improve LLM error rates exactly?
Error rate here is the rate of shipping bugs to customers.
Earlier quoted context omitted.
The discussion is centered around the idea that "adopting early" provides some future proofing in a rapidly evolving (and largely non-standard) terrain. I share the FA's position that it does not. > The web is special in this sense, it's intentionally long-lived warts and all. So the fundamentals pay outsized dividends. Fundamentals pay dividends, but what makes you think that what you learn as an early adopter are f…
Good points and thoughtful reply. You're right, fundamentals are distilled, so to think they are free just by getting in early is likely backwards. And earning one's professional chops doesn't stop or start based on when you enter. Web dev definitely is nostalgic. I miss the early days but I also conveniently erased ie6, binding data to HTML, the need for backbone and jQuery to do anything. hmmm yeah doesn't matter w…
Also known as PTSD-induced amnesia, haha. We all tried to forget.
Earlier quoted context omitted.
No, this thread and sub-discussion is about specifically early web fundamentals. The web is special in this sense, it's intentionally long-lived warts and all. So the fundamentals pay outsized dividends. The rube goldberg machine that is modern JS dev still spits out an index.html result. Being a good professional developer means getting the primitives and the data model not horribly pointed in the wrong direction. S…
The discussion is centered around the idea that "adopting early" provides some future proofing in a rapidly evolving (and largely non-standard) terrain. I share the FA's position that it does not. > The web is special in this sense, it's intentionally long-lived warts and all. So the fundamentals pay outsized dividends. Fundamentals pay dividends, but what makes you think that what you learn as an early adopter are f…
Picking up the web early didn't help with the latter. I spent most of my early time memorizing tips and tricks that only applied to old browsers. I didn't pick up the fundamentals till I went back to school for CS and took a networking class.
Earlier quoted context omitted.
“You're holding it wrong.” is the most common response I get, when I talk about problems I had with LLM-assisted coding.
You aren't holding it wrong, the truth is AI is a mixed bag, leaning towards a liability. If people really counted all the time they spend coddling the AI, trying again, then trying again and again and again to get a useful output, then having to clean up that output, they would see that the supposed efficiency gains are near zero if not negative. The only people it really helps are people who were not good at coding…
Exactly. I counted and reported my results in a previous thread [0].
Earlier quoted context omitted.
> Suddenly the job ads were "Android Dev. Must have 3 years experience". So just read up on it and say you do. They don't really need 3 years experience, so you don't really need to have it.
Employers check your work history. You'd better be able to back up having the amount of experience they require with paid, value-delivering work at past employers, or they'll pass.