• 0 Posts
  • 2 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle

  • All the other comments are great advice. As an ex chemist who does quite a bit of code I’ll add:

    Do you want code that works, or code that works?! It’s reasonably easy to knock out ugly code that only works once, and that can be just what you need. It takes a little more effort however to make it robust. Think about how it can fail and trap the failures. If you’re sharing code with others, this is even more important a people do ‘interesting’ things.

    There’s a lot of temporary code that’s had a very long life in production, this has technical debt… Is it documented? Is it stable? Is it secure? Ideally it should be

    Code examples on the first page of Google tend to work ok, but are not generally secure, e.g doing SQL queries instead of using prepared statements. Doesn’t take much extra effort to do it properly and gives you peace of mind. We create sboms for our code now so we can easily check if a component has gained a vulnerability. Doesn’t mean our code is good, but it helps. You don’t really want to be the person who’s code helped let an attacker in.

    Any code you write, especially stuff you share will give you a support and maintenance task long term. Pirate for it!

    Code sometimes just stops working. - at least I’m my experience. Sacrifice something to the gods and all will be fine.

    Finally, you probably know more than you think. You’ve plenty of experience. Most of the time I can do what I need without e.g. classes, but sometimes I’ll intentionally use a technique in a project just to learn it. I can’t learn stuff if I don’t have a use for it.

    I’m still learning, so if I’ve got any part of the above wrong, please help me out.