alxexperience
I find that phrase very helpful, because usually when I write, the first draft is always a giant mess. But you're able to craft it and edit it the best way that you can. So you can push out what you think is good work, and continue to improve as you write more.
I don't write nearly as much as I would like to, but I'm trying to get back into the swing of things. I write about videogames and am hoping to write more tech stuff in the future
I believe this is the story OP mentioned [1].
> Windows 95? No problem. Nice new 32 bit API, but it still ran old 16 bit software perfectly. Microsoft obsessed about this, spending a big chunk of change testing every old program they could find with Windows 95. Jon Ross, who wrote the original version of SimCity for Windows 3.x, told me that he accidentally left a bug in SimCity where he read memory that he had just freed. Yep. It worked fine on Windows 3.x, because the memory never went anywhere. Here’s the amazing part: On beta versions of Windows 95, SimCity wasn’t working in testing. Microsoft tracked down the bug and added specific code to Windows 95 that looks for SimCity. If it finds SimCity running, it runs the memory allocator in a special mode that doesn’t free memory right away. That’s the kind of obsession with backward compatibility that made people willing to upgrade to Windows 95.
[1] https://www.joelonsoftware.com/2000/05/24/strategy-letter-ii...
I have Node.js setup, and I have TypeScript installed as my first npm package, since the scale of my work is made so much more manageable by it.
Locally, I run WebStorm by JetBrains. It has a lot of useful plugins, and it’s build in Debugger is invaluable when debugging large, complex code. I use Docker for MongoDB and Postgresql. PGAdmin is extremely valuable for Postgres.
Git is used all the time to check in code, and most of my code is self-documented/JSDoc, since I’m not really a big fan of writing external documentation unless it is user facing.