diff options
Diffstat (limited to 'posts/2025-10-27_personal-code.md')
| -rw-r--r-- | posts/2025-10-27_personal-code.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/posts/2025-10-27_personal-code.md b/posts/2025-10-27_personal-code.md index f038814..2c5c92e 100644 --- a/posts/2025-10-27_personal-code.md +++ b/posts/2025-10-27_personal-code.md @@ -25,7 +25,7 @@ Writing code professionally is like working on a textbook. Everything should be spelled out and documented. Newcomers can open a textbook to any section and be able to retrace information to understand. In programming we do this with docs, comments, and logs. -These help a teammember who might have to change a part of the code they haven't touched yet. +These help a team member who might have to change a part of the code they haven't touched yet. While we get explainability and traceability, we also get heft. Textbooks are big and tediously constructed. Big and tedious is the enemy of personal code. @@ -61,7 +61,7 @@ By assuming the only user is me, I don't lose focus and energy on productization "Don't reinvent the wheel" does not apply to personal code. With professional code, we're expected to balance buying from a vendor vs. building ourselves. -Personal code has no such economic considersations. +Personal code has no such economic considerations. I think the current culture is too prone to "yet another" critiques and pointing out how to do something in as few steps as possible. It's powerful to be able to quickly and cheaply tie together off-the-shelf tech into something compelling, but we should still be able to do things the hard way and build what's already been built somewhere else. @@ -94,15 +94,15 @@ Just because I'm writing code, shouldn't mean I have to share it to prove anythi Still, personal code *can* be public without breaking the rules. That's why I said "assume" no one will read it or use it. -Looking at each other's code is fun, especially when the project isn't commerical-grade. +Looking at each other's code is fun, especially when the project isn't commercial-grade. It's one of the reasons I enjoy the folk art section of art museums. -Keeping in the back of my mind somebody might look at it is hard without clouding my judgement when coding, which is why I need the rules. +Keeping in the back of my mind somebody might look at it is hard without clouding my judgment when coding, which is why I need the rules. ### Can personal code become professional code? Plenty of software starts out to solve one person's needs and ends up solving a bunch of people's needs. I don't think we should remotely assume this will be the case for our personal code. If it ends up being so useful, it will probably need to be rewritten with this new goal in mind. -That shouldn't be difficult because personal code is by neccessity bare-bones. +That shouldn't be difficult because personal code is by necessity bare-bones. It's possible a toy project can turn into a company or the next great open source tool, but try not to think about it too much! |