Earlier quoted context omitted.
Every programmer really is just mediocre. There is no perfect software yet. Hence people who built it are mediocre.
Like any skillset, programming skills likely form a distribution pattern. There are exceptional programmers out there, I've worked with a few. "Every programmer really is just mediocre" merely indicates you have only worked with mediocre colleagues and are one yourself. > There is no perfect software yet. "Software" you refer to is actually 'software product', not merely 'code'. So the reality is that even with excep…
Ask HN: Go deep into AI/LLMs or just use them as tools?
111–120 of 140 posts
Re: Ask HN: Go deep into AI/LLMs or just use them as tools?
#112Andriy Burkov has written excellent trilogy books series on AI/LLMs namely "The Hundred-Page Machine Learning Book" and "Machine Learning Engineering" and the latest "The Hundred-Page Language Models Book" [2],[3],[4].
Having said that, the capability of providing useful AI/LLMs solutions for intuitive and interactive learning environment, training portal, standards documentation exploration, business and industry rules and regulations checking, etc based on the open-source local-first data repository with AI/LLMs are probably the killer application that're truly useful for end users, for examples here [5],[6].
[1] Automatic differentiation:
https://en.wikipedia.org/wiki/Automatic_differentiation
[2] The Hundred-Page Machine Learning Book:
[3] Machine Learning Engineering:
https://www.mlebook.com/wiki/doku.php
[4] The Hundred-page Language Models Book
[5] Local-first software: You own your data, in spite of the cloud:
https://www.inkandswitch.com/essay/local-first/
[6] AI-driven chat system designed to support students in the Introduction to Computing course (ECE 120) at UIUC, offering assistance with course content, homework, or troubleshooting common problems. It serves as an educational aid integrated into the course’s learning environment:
Re: Ask HN: Go deep into AI/LLMs or just use them as tools?
#113My 2 centes: 1. Learn basic NNs at a simple level, build from scratch (no frameworks) a feed forward neural network with back propagation to train against MNIST or something as simple. Understand every part of it. Just use your favorite programming language. 2. Learn (without having to implement with the code, or to understand the finer parts of the implementations) how the NN architectures work and why they work. Wh…
(That's not to say that you shouldn't bother with learning more -- more knowledge is always good -- or that the OP specifically only knows that. It's more a sensible minimum.)
My own "curriculum" for that has been Jeremy Howard's Fast AI course and Sebastian Raschka's book "build an LLM from scratch". Still working through it, but once I'm done I think I'll be solid on your point 2 above. My guess is that I'll want to learn more, but that's out of interest more than because I think its necessary.
Re: Ask HN: Go deep into AI/LLMs or just use them as tools?
#114Depends on what you want to do. But my 2 cents are that like all new technology, LLMs will become a commodity. Which means that everybody uses them but few people are able to develop them from scratch. It's not different from other things like databases, GPU drivers, 3D engines for games, etc. That all involves a lot of hardcore computer science and math. But lots of people use these things without being hindered by…
>It's not different from other things like databases, GPU drivers, 3D engines for games, etc. Not quite the same. E.g. databases are a part of the system itself. It's actually pretty helpful for a SWE to understand them reasonably deeply, especially when they're so leaky as an abstraction (arguably, even the more nuanced characteristics of your database of choice will influence the design of your whole application).…
Granted this is a pretty simple task and a low stakes scenario, but I don't think we should limit ourselves to assuming AI will always only be dev tooling.
Re: Ask HN: Go deep into AI/LLMs or just use them as tools?
#115Depends on what you want to do. But my 2 cents are that like all new technology, LLMs will become a commodity. Which means that everybody uses them but few people are able to develop them from scratch. It's not different from other things like databases, GPU drivers, 3D engines for games, etc. That all involves a lot of hardcore computer science and math. But lots of people use these things without being hindered by…
That means, if you learn more about the internals of LLMs, your market angle is going to be artisanal customised models. Fashion is commoditised, but people still pay for a custom tailored suit. In the same way companies will continue to pay for finetunes optimised for their business usecase.
If you decide to focus more on the application of LLMs, you should really invest into high-level architectural skills. Good “code completion” models can already do what an outsourced 10 bucks per hour developer used to do. Your job in the future is going to be to decide the structure of which fuse and against the towel and or which type of state is being stored and managed. But the actual coding of the UI forms and the glue code to synchronise from an SQL query to the client state, that part is probably going to be fully outsourced to LLMs.
Re: Ask HN: Go deep into AI/LLMs or just use them as tools?
#116It's your choice, but it's definitely not ,,just another tool''. Most of my LLMs made lots of mistakes, but Codex with $200 subscription changed my workflow totally, and now I'm having 40 pull requests/day merged. Treat LLMs as interns, increase your test coverage with them to the point that they can't ruin your codebase and get really good at reviewing code and splitting tasks up to smaller digestible ones, and prom…
In an 8 hour workday you are merging one new PR every 12 minutes?
I'm very sceptical that anyone can review a significant chunk of code that fast, unless these are all one and two liners that pass review on the first go.
In this best case scenario, where no review results in reworking the PR, and you can review and merge every 12 minutes, without any breaks of any sort, why is your review even required?
Re: Ask HN: Go deep into AI/LLMs or just use them as tools?
#117Re: Ask HN: Go deep into AI/LLMs or just use them as tools?
#118My 2 centes: 1. Learn basic NNs at a simple level, build from scratch (no frameworks) a feed forward neural network with back propagation to train against MNIST or something as simple. Understand every part of it. Just use your favorite programming language. 2. Learn (without having to implement with the code, or to understand the finer parts of the implementations) how the NN architectures work and why they work. Wh…
As someone who I both respect a lot and know is really knowledgeable about the latest with AI and LLMs: can you clarify one thing for me? Are all these points based on preparing for a future where LLMs are even better? Or do you think they're good enough now that they will transform the way software is built and software engineers work, with just better tooling? I've tried to keep up with them somewhat, and dabble wi…
Re: Ask HN: Go deep into AI/LLMs or just use them as tools?
#119My 2 centes: 1. Learn basic NNs at a simple level, build from scratch (no frameworks) a feed forward neural network with back propagation to train against MNIST or something as simple. Understand every part of it. Just use your favorite programming language. 2. Learn (without having to implement with the code, or to understand the finer parts of the implementations) how the NN architectures work and why they work. Wh…
> Learn how to use AI effectively for coding. This is absolutely non-trivial, and a lot of good programmers are terrible LLMs users (and end believing LLMs are not useful for coding). I've been asking this on every AI coding thread. Are there good youtube videos of ppl using AI on complex codebases. I see tons of build tic-tac-to in 5 minutes type videos but not on bigger established codebases.
Re: Ask HN: Go deep into AI/LLMs or just use them as tools?
#120However, this question is better answered by asking yourself what you're interested in. Do you _want_ a deeper understanding of AI/ML? If so, jump in. If you're not genuinely interested it'll be an interminable slog, and you'll revert to doing whatever you actually want to do eventually.
Nothing wrong with continuing to develop web/full stack apps while leveraging the new tools; that's also quite interesting.