868 karma · joined July 27, 2023
Interests: computer history, guitar, cycling, running, film and darkroom photography
The annoyances of the Leaf are overstated, and the benefits are way better than people give credit for.
If people do what’s popular, they have to accept a popularity tax for the “keeping up with the Joneses” lifestyle
- Proficiency in xyz language is extremely important. I think this is misunderstood to mean that becoming a Python/Typescript/whatever expert is what differentiates the pros from the bros. I would actually recommend studying the theory of programming languages from first principles, instead - Dan Grossman's "Programming Languages" class on Coursera is great for this. It lays the foundation for understanding how any programming language works, from a theoretical and mechanics basis. I was able to pick up new languages and understand concepts in existing languages way, way faster after building this foundation. The "10 hours to Python mastery" types of courses are a waste of time and focus on the wrong things in my opinion - invest the time in foundational knowledge instead.
- YouTube videos and blog posts are sufficient to become a proficient programmer. This is a bit of a con in my opinion. Both formats are like a sugar-heavy diet - you'll feel high and satisfied quickly, but in the long-term, the lack of information in these formats will starve you of high-quality information. Get into a habit of returning to first principles - figure out what the canonical textbooks are for the subject matter you are trying to learn about, acquire them, and read chapters out of them when you are stuck on a problem. This will deepen your understanding and give you a basis for exploring related subjects. Also, read the man page. Read the man page. Read the man page.
Also check out OSSU (https://github.com/ossu), which has a bunch of great recommendations for free/nearly-free courses that will complete a full CS curriculum. I lack a CS degree, so I periodically reference this curriculum when looking for a new subject to study in my downtime.
Happy to talk more if you're interested, we need more smart and capable individuals like yourself in this field.
0 - Try to write the code myself, using LSP hints as needed
1 - Read the primary source (man page, documentation, textbook) to find an answer. Upside is that I learn something about related topics along the way by skimming the table of contents
2 - Consult stack overflow/google. This has become less and less useful, as both of those resources have become flooded with garbage info and misleading blog posts in the last several years.
3 - Pull out the AI copilot and ask it for help, while sharing what I already know and what I think the shape of the solution will be.
4 - Actively seek help - talk to colleagues, post a question on a relevant forum, etc...
Is this perfect? No, I've wasted hours in the worst case with an answer that the copilot thought was correct, but was not. But on balance, I'd say that it has saved me many days worth of time in the last year, usually in the form of research and knowledge discovery. It's much faster to test out a bunch of potential solutions when the copilot is writing most of the code and I just tweak a few relevant parameters.
I've been using all the time I've saved on mundane programming by studying computer science from first principles. As someone without a CS degree, I am acutely aware of my gaps in knowledge about theoretical computer science. I consider myself a halfway-decent programmer at this point, so I don't find that filling my head with more and more syntax and esoteric rules about frameworks to be helpful. I'd rather learn what the basis is for all those rules, and reconstruct them myself as needed.
I also have a lot more confidence to branch out from my moneytree (web dev) and try my hand at other areas of programming, like embedded development, messaging, and language theory. This field is endlessly fascinating, and I selfishly want to learn and try it all. So far in my career, I've spent most of it in web dev, but have also been able to test the waters of embedded development for a year, and interesting "back-end" services for another year or so. I even had the confidence to start my own company with a friend, realizing that I could actually shoulder most of the development burden early on if I strategically rely on AI to prompt me through implementation details which I'm not quite an expert in.
This is my strategy for ensuring longevity in this career. I'll admit I'm only on year 8 of programming professionally, but I hope this is the correct attitude to have.
If you want a speedy government and speedy paperwork, it might be worth asking if we could increase headcount to handle tasks, preferably in parallel if possible.
A comment like this is kind of bewildering on a tech news site full of software entrepreneurs. Instead of handling more paperwork with more people, why don't we find ways to automate the paperwork processing using computers? Every other competitive industry streamlined their processes decades ago (and continues to do so) - why is the government exempt from this kind of solution as well? Do we have to accept that millions of people must do useless tasks for the US government? For example, if you require your house to get inspected for code, you may want to increase the size of your planning department so that code inspection can occur within the day. Can the environmental assessment be done in parallel to other necessary paperwork?
It's funny you use this as an analogy, because home inspections are notoriously pointless. They tell you stupid things, such as that the step to the house is 11" from ground, while code is 8" - meanwhile totally missing issues in the crawl space because "it is unsafe for us to go in there". I paid $500 to be lulled into complacency, and no amount of money for more inspectors to do the job "faster" would have convinced someone to find the important issues with the house I was about to buy. I'm not interested in paying even more money for more useless information. That's the point - scrub out these useless checks and parades of stupidity, which there is plenty of in both the home-buying process as well as in government.https://daedtech.com/how-developers-stop-learning-rise-of-th...
Happy to chat further if you’d like some advice or just want to hear how I recognized the situation and got out. It probably took 2 years longer than it needed to, for me to fix the situation
I am also excited by the fact that the text editor configuration is programmable in a Turing-complete language, as opposed to pure JSON configurations that VS Code offers (correct me if I'm wrong, but settings are just a JSON file right?). It means that anything is possible.
In VSCode, my biggest complaint was that, for the Vim extension, the status bar was not configurable - I wanted to make the whole page change color when in "Normal" mode, versus "Insert" mode. Not possible in VSCode, but it's only a handful of lines of Lua in Vim.
Is that a huge productivity boost? No, but it makes me happy. Just as much as I want to be productive, I also want to be happy while programming
I really hope you’re wrong about that. I don’t want to be ruled by another Microsoft product
I like working from a desk. I feel locked in, and when I get up, it really is to take a break from the work
The cost savings are certainly worth it. I also grew up with desktop computing until college, and even then the laptop rarely left my dorm room. So maybe I’m just used to working this way
I recently spec’d out some comparable machines from Apple - $999 gets you a 32GB Mac Mini M4. A comparably setup Macbook Air (24GB, M3) costs $1299, and the current gen Macbook Pro is $1999. That’s a lot more money for a small screen and small keyboard
The key observation here is that the mind is very, very flexible and adaptable to assimilating new information and working with abstractions. So when you feel like you're at the edge of your working memory when solving a problem, then maybe it's time to take a step back and find ways to simplify or abstract those pieces into a larger concept that can fit more easily into one "slot". Instead of remembering 6 pieces of information, it might be easier to learn a particular pattern, load that into "Slot 1", and use "Slot 2" to keep track of the particular ways the code you're looking at deviates from the standard pattern.
It's also interesting to note that these "slots" aren't really fixed in size, nor are they even comparable between people. Some people have way better abilities to cram a huge amount of mathematical information per slot, while others are very good at people interactions and assimilating all their observations. Finally, all of this can be trained - just because you're bad at one skill, doesn't mean you will always remain bad (yes, even outside the "critical learning period")
Care less about what people think about you at work, and more about your health. We’re all adults, and you’re allowed to do that. others are more forgiving when you show grace while admitting faults
Take a month off and go somewhere. Or don’t, staycation. Or work on a side project. Or replay Final Fantasy 7. You’re allowed to do all these things, and you should
keybr.com - Retrained myself to type on an ortholinear ergo keyboard after 20+ years of bad habits and pecking at membrane keyboards. Went from frequent wrist pains and breaks needed, to being able to type for hours on end. I still take breaks, but not because of hand pain anymore. I used keybr.com to help retrain my typing skills in a few weeks
Rectangle - even though the latest macOS has window snapping, it did not for many, many years. I like how configurable this window snapper is, with hotkeys and customizable window sizes. Easily worth the $4 one-time charge
——
Also - to each their own, but if you’re paying to meditate, you’re doing it wrong
2) lynx https://www.w3.org/History/1945/vbush/vbush.shtml
3) Accept cookies with a glass of warm milk and enjoy :)