1,801 karma · joined January 12, 2014
I posted a long and very moving story the other day about a software developer who was getting blind on an eye in six hours. https://elye-project.medium.com/i-became-blind-within-6-hour...
It made me think about how much time we spend in front of screens these days and that eyesight can't be taken for granted.
This article was a nice contrast describing the possibilities to do work as a blind developer.
Good luck!
As long as an understanding of the domain and problem is required a skilled person is required between the codebase and the LLM.
Even if we get to a point in the future where a programmer can be replaced by an LLM, we'll have businesses where they want someone to use the LLMs to create software.
Some tips: Reach out to recruiters who have contacted you in the past. Sign up for online CV databases. Use your network and contact former colleagues to see if their companies are hiring. Work on a side project that excites you and makes you proud to change your mindset, or take an online course. Try to get excited about the challenge instead of thinking about giving up. I just watched a YCombinator video which, among other things, talks about not giving up too soon: https://youtu.be/al-15mMAS18.
Also, try to get feedback when you're rejected. Are you showing genuine interest in the job? Do you ask insightful questions, and do you submit take-home assignments without bugs?
Moreover, the fact that artists seem to be paid so little makes me increasingly inclined to consider leaving their service for something else, like Tidal, or simply using YouTube Music.
By the way, if anyone is working on a Spotify killer, feel free to reach out. It would be fun to help out.
It has been one of my favorite books about programmers and programming since my childhood.
Steve Jobs has great points again. I love to hear him talk about what really matters for success of great tech companies.
Also, imagine having several agents and having to switch back and forth between them. I'd probably prefer a single GPT with multiple abilities customized to my interests and coding tips.
The day when personalized agents can give you information you didn't know you needed, then we're talking...
”Any fool can write code that a computer can understand. Good programmers write code that humans can understand.” – Martin Fowler
Anyway, I think there has to be a decision/ranking on the importance of having
1. happy programmers & excellent code 2. code that any(?) developer could jump in and maintain
To me it often boils down to not making simple shortcuts due to laziness unless it buys time to market or has some other significant upsides.
Making a system flexible can often be done in a non-complex way so I would challenge then need to make software complex. There is often a trade-off between efficiency and maintainability. If the efficiency route is always preferred there could come a day when the developers quit and others have to maintain what they feel is a mess of code and want to rewrite it. So my vote would be to keep the complexity low (and flexibility high!) unless there's a concrete benefit of allowing the complexity to grow.
You could look into various design patterns to keep code flexible while keeping complexity low.
I thought the article quote was nice too:
> “Of course it is what it is! What else would it be? It would be weird if it wasn’t what it wasn’t,” one user quipped.