• 0 Posts
  • 73 Comments
Joined 1 year ago
cake
Cake day: August 18th, 2023

help-circle


  • Meh, that’s kind of the point, no? Seems like it would be more jarring to only federate at the community level, as you either a) still have to interact with people from the unwanted instance or b) deal with randomly hidden comments from that instance. If the community dies because it’s on an unpopular instance, well, that’s the way it goes. Can always start up/join a community on another instance that’s federated with yours.





  • I agree that most people won’t care but take issue with calling them “dumb”. Everyone has a limited amount of time on this planet to build skills and chase hobbies. A lot of people on this site have tech-related jobs and hobbies, so of course this matters to us. I might expect someone who buys pre-built gaming PCs to keep this on their radar, but the vast majority of folks who use computers as email and social media machines, including those who only use it for data entry type jobs, have little reason to care about the specifics of their CPU or any other single component of their computer. If their computer breaks, that’s annoying, but that’s life. They’ll spend the same amount on a new laptop as we might spend on a new CPU and get on with their day.

    I don’t know what brand of spark plugs are in my car, and maybe a mechanic or car enthusiast would find that dumb. But hey, I’m too busy caring about my CPU to spend time worrying about my car unless it breaks.








  • I definitely agree, but that’s true of any system. The particulars of the pitfalls may vary, but a good system can’t overpower bad management. We mitigate the stakeholder issue by having BAs that act as the liason between devs and stakeholders, knowing just enough about the dev side to manage expectations while helping to prioritize the things stakeholders want most. Our stakes are also, mercifully, pretty aware that they don’t always know what will be complex and what will be trivial, so they accept the effort we assign to items.


  • Honestly a little confused by the hatred of agile. As anything that is heavily maligned or exalted in tech, it’s a tool that may or may not work for your team and project. Personally I like agile, or at least the version of it that I’ve been exposed to. No days or weeks of design meetings, just “hey we want this feature” and it’s in an item and ready to go. I also find effort points to be one of the more fair ways to gauge dev performance.

    Projects where engineers felt they had the freedom to discuss and address problems were 87 percent more likely to succeed.

    I’m not really sure how this relates to agile. A good team listens to the concerns of its members regardless of what strategy they use.

    A neverending stream of patches indicates that quality might not be what it once was, and code turning up in an unfinished or ill-considered state have all been attributed to Agile practices.

    Again, not sure how shipping with bugs is an agile issue. My understanding of “fail fast” is “try out individual features to quickly see if they work instead of including them in a large update”, not “release features as fast as possible even if they’re poorly tested and full of bugs.” Our team got itself into a “quality crisis” while using agile, but we got back out of it with the same system. It was way more about improving QA practices than the strategy itself.

    The article kinda hand waves the fact that the study was not only commissioned by Engprax, but published by the author of the book “Impact Engineering,” conveniently available on Engprax’s site. Not to say this necessarily invalidates the study, or that agile hasn’t had its fair share of cash grabs, but it makes me doubt the objectivity of the research. Granted, Ali seems like he’s no hack when it comes to engineering.






  • Everyone has a limited time on this earth. Some of us don’t mind or actively enjoy spending that time learning about the technology we use. Others, not so much. I think this comic is really spot on because it’s hard to understand as a tech literate person just how little other people may know. “What browser are you using?” “What’s a browser?”

    The foundational knowledge is not that tough, but when you’re just interested in getting the damn thing to work so you can get on with your life, it’s easy to get frustrated by having to take a crash course on what the hell a BIOS is before you can try to fix it. And when you learn all that just for it to still be broken, patience quickly runs out.

    As long as people have the general understanding that power cycling will solve a good 75% of issues, I’m happy. I hope people give me the same grace when I pay a someone to fix my car or replace my phone screen (I love building computers, but god I hate working on phones).