You kinda feel that you are learning something but you only truly learn when you have to do it from scratch.
2,848 karma · joined February 27, 2013
You kinda feel that you are learning something but you only truly learn when you have to do it from scratch.
If you are an UI designer and want to create art then fine do that in your spare time. But at work be a professional and make the UI predictable and functional above all else.
Google "recursive descent parsing" and it will tell you everything you need to know about the front-end of a compiler.
Google "My First Language Frontend with LLVM" and it will teach you the other half.
In other words, the code was proven correct according to spec by LEAN. Which is exactly what LEAN claims to do.
Instead just get started with the smallest possible step you can just about manage to do. And then do another smallest step. A lot of times you almost automatically keep going and the motivation then arrives.
Maybe the first step is to create a basic "Hello World" application. And then a few empty functions/methods that flesh out what the app needs to do. Then maybe a few of those methods/functions are really easy to do (or AI can write them for you) so you quickly do those. Etc.
It's actually really simple to eat healthily: Cook yourself using real (non-processed) food. The kind of food that doesn't need a label.
And a close (non-tech) second is the ruthlessness of sociopaths seeking power.
In 2026 I don't want to use a slow interpreted non-typed language like Python.
C++ (for example) has excellent super fast matrix libraries where you can do AxB.
It is easy to come up with questions that the author would fail in an interview. Simply because there are thousands of minutia details that most senior developers wouldn't know about.
What the interviewer should focus on is the ability to solve real world problems. For example by walking the interviewee through a real world business scenario and letting the interviewee describe how he/she would solve the problem.
Both when initially writing the code and later when maintaining it.
Good code dramatically reduce bugs and makes the remaining bugs more visible.
I spend almost zero time fixing bugs. Because there aren't many. Not a brag. Just the truth.
Whether the world is discrete or analog is still an open problem in science. And it looks as if there is more and more evidence that the world is actually discrete at the quantum level.
Terence Tao is actively using LEAN and working with the LEAN community to prove leading edge mathematics.
1. Print "You are in a dark dungeon. There is a door ..." 2. Print "Your options are: 1. Open the door 2. Exit 3. Turn on ..." 3. Read a number as input 4. Goto (yes goto) similar code depending on choice.
Nope. You picked the wrong wife if that is the situation you are finding yourself in. My partner and I accept each others perspectives even if we disagree. I would never date a woman who can't accept that different opinions exist and that we both will sometimes be wrong.
The most unmaintainable system I've ever encountered in my long career was a 30+ year-old microservices architecture consisting of over 100 processes. Even the simplest use cases had devolved into a nightmare of timing issues, fragile dependencies, and unnecessary complexity.
Yes let me repeat that it was a 30+ years old microservices architecture. There is nothing new about microservices.
No you don't need to reinvent the wheel thank you.
It’s the same with games. I give them a few months for the inevitable bug fixes and balance patches before jumping in. Saves a lot of frustration. And a lot of wasted time.
However almost all of the companies I have worked for in my 30+ years career treated devs well.
So if you are in a shitty situation, I highly recommend finding another job instead of just placing yourself over a barrel.
However it is not AI. It is simply a program that takes a declarative spec as input and generates all the boiler plate code I would otherwise have to write by hand.
It is a huge productivity boost!