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

help-circle


  • Fair enough, at my job the code working consistently is absolutely the number one priority at all times but I can imagine that there are some places where this is not true. If working software isn’t imporant then I agree agile is probably not the right choice

    It’s worth pointing out though that having insufficient documentation is not a feature of agile. Sounds more like laziness or misplaced priorities to me as documentation is called out as being useful in the agile principles, just not as important as working software.





  • Note that this is failure to deliver on time, not failure to deliver full stop.

    I also think a lot of places claim to be agile, but don’t follow or understand the principles at all. Another commenter here is the perfect example of that where they say the opposite of what’s in the agile manifesto and claim that it’s a representation of what it says.

    Maybe that’s a fundamental problem with agile. It’s just a set of loose principles rather than a concrete methodology being pushed for by a company and it has therefore been bastardised by consulting companies and scrum masters claiming to teach the checklist of practices that will make your company agile. Such a checklist does not exist, it’s just a set of ideas to keep in mind while you work out the detailed processes or lack thereof that work for you.

    For anyone that wants to refresh their memory on the agile manifesto:

    Individuals and interactions over processes and tools

    Working software over comprehensive documentation

    Customer collaboration over contract negotiation

    Responding to change over following a plan

    That is, while there is value in the items on the right, we value the items on the left more.


    1. Don’t Write Logs by Yourself (AKA Don’t Reinvent the Wheel)

    2. Log at the Proper Level

    3. Employ the Proper Log Category

    4. Write Meaningful Log Messages

    5. Write Log Messages in English

    6. Add Context to Your Log Messages

    7. Log in Machine Parseable Format

    8. But Make the Logs Human-Readable as Well

    9. Don’t Log Too Much or Too LittlE

    10. Think of Your Audience

    11. Don’t Log for Troubleshooting Purposes Only

    12. Avoid Vendor Lock-In

    13. Don’t Log Sensitive Information

    The article goes into some nice detail on each of these but those are the 13 practices being advocated.









  • If you want to play a star game I recommend Starsector. I’ve been getting back into it recently and it’s great. More a mount and blade in space than a Starfield though. Updates are slow but significant and there’s plenty of game to enjoy already.

    One really cool mechanic is story points which you get alongside levelling up (and you keep earning after the level cap) which you can spend in certain parts of the game to do special stuff or break the normal rules which is really cool. Many interesting things tie into it but yeah, lot’s of interesting mechanics.



  • Sounds like you have some programming experience already but whether this is a reasonable learner project I think depends a bit in what kind of things you’re trying to learn but it sounds pretty good to me.

    If you’re going to be using a familiar language and you already know how to call web APIs pretty comfortably I think that’s a pretty reasonable pet project assuming musicbrainz has a public API (I’m not familiar with it unfortunately).

    If you’re wanting to learn some more basic stuff around calling APIs and maybe a language you’re not familiar with I would start by making something super dumb that calls an unauthenticated public API like a weather service or something.

    Ultimately I think your project idea sounds good though, just making a suggestion for something even simpler you could try as a stepping stone if you need to.

    Either way congrats on your retirement! Have fun with all the interesting projects you decide to pursue.