2 ms·
You're either one of the best developers in the world, or you think you are. If the former, then your system works well. If the latter, well, I'm glad it's be
by jedberg 4y ago
You're either one of the best developers in the world, or you think you are. If the former, then your system works well. If the latter, well, I'm glad it's been working for you so far, but I suspect you'll have trouble down the road.
And if you don't, it sounds like you'll never get your flywheel going so that you can stop working or work on something else.
I'm mostly saying, to people reading this, it would probably be unwise to follow this advice.
- forgotmypw17 4y agoI agree with jedberg. Please do not treat my post as advice. Nowhere did I state that it is intended as such.
- nailer 4y ago> You're either one of the best developers in the world I'd say this is the approach used by anyone in the top 5% (give or take). Which is probably most of HN. You don't need to be Linus or Fabrice or DJB to know most programmers are bad at programming and realise you can do a better job. Does that mean he writes his own kernel and C compiler? No, OP writes: > I avoid using third-party libraries for anything I can write myself. Which shows awareness of his current limits, another trait of good programmers.
- deterministic 4y agoI disagree. The more dependencies I remove, the less of a maintenance burden the code I maintain is. I am maintaining very large scale C++ code used in production every day by large multi-national companies. And have almost zero maintenance work.