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

help-circle







  • Right off the bat i read

    One standout statistic was that projects with clear requirements documented before development started were 97 percent more likely to succeed. In comparison, one of the four pillars of the Agile Manifesto is “Working Software over Comprehensive Documentation.”

    You need clearly defined requirements to write a good user story. Documentation comes after.

    However, while the Agile Manifesto might have its problems, those stem more from its implementation rather than the principles themselves. “We don’t need a test team because we’re Agile” is a cost-saving abdication of responsibility.

    Precisely, once once have i worked in a company where agile was properly implemented and, yes, user stories were well documented and discussed before being developed. All others are just waterfall in disguise, or Fragile™.

    However, while the Agile Manifesto might have its problems, those stem more from its implementation rather than the principles themselves. “We don’t need a test team because we’re Agile” is a cost-saving abdication of responsibility.









  • Team of one here tends to work on master only for very small stuff.

    There’s a branch for the next release which will get merged once everything’s done. Occasionally there are smaller branches that fork off of the release branch and get merged back.

    Meanwhile master is, most of the time, an old copy of the new release branch so merging goes without issue. Unless there’s a problem in prod, then it gets fixed in master and backported to the feature branch.

    I should use feature toggles more (usually #ifdef, sometimes if (config_Flag)), occasionally a big feature creeps in and i know management will change it at least 3 times and 2-3 new releases will come out in between…


  • Generally speaking, my approach is “on the internet no one knows you’re a dog”. I tend to containerize my activity and keep as much PII away from the internet as possible.

    I have a few accounts on the fediverse because otherwise the conjunction of regional data, interests and languages would easily identify me. Not that i generally do dumb stuff (but i can easily get flagged if i touch… hot topics, you must pander to certain groups otherwise you’re immediately the villain, very free the fediverse), it’s just that the internet hasn’t quite evolved the way i was expecting it 30 years ago and surveillance capitalism is now a thing, among other factors. I provide as little and as fake information as possible when creating accounts.

    As far as the professional sphere goes, all recruiters will ever see is a simple LinkedIn profile. I don’t have much time to do pet projects, unfortunately, and certainly wouldn’t host them on github - forgejo and codeberg ftw.