3 ms·
Boy, I feel this. I am also a 0.5x programmer. I write dead-simple C; I don't even touch web development, which I consider more complex than C development with
by gavinhoward 3y ago
Boy, I feel this.
I am also a 0.5x programmer. I write dead-simple C; I don't even touch web development, which I consider more complex than C development with Valgrind.
In fact, I've spent nearly 3 years writing a build system. That's how slow I am, and it's made some acquaintances laugh at how long I've worked without result.
But in reality, I'm not just building a build system. I'm also building my own stack, a la [1], including replacing as much of libc as I can and changing the OS API's I use.
I think that soon enough, this stack and this simplicity will become my superpowers and make me a 10x programmer.
Being a stupid programmer means you won't be clever. And if you're not clever, you will be able to debug it, even though it is twice as hard to debug than to write. [2] Good debugging is a superpower in itself.
[1]: https://youtube.com/watch?v=443UNeGrFoM https://youtube.com/watch?v=443UNeGrFoM
[2]: https://www.defprogramming.com/quotes-by/brian-w-kernighan/ https://www.defprogramming.com/quotes-by/brian-w-kernighan/
- whstl 3y agoGreat point about debugging. We're currently trying to simplify a monolith that is too hard to maintain, and the biggest issue for us that debugging is heavily impacted the call-stack size. Sometimes 100 functions before it gets to the point you want. All this due to very complex class and function hierarchies. I'm responsible for a rewrite of some modules and I'm personally gonna stick with simple stuff.