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

help-circle

  • 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.






  • I still credit him with really sparking my interest in science, but he’s taken a the lighthearted question of “could this work in the real world?” to extremely pedantic and unpleasant extremes. Who the fuck cares if “uhm actually the stars didn’t look like that when the Titanic went down”?

    I don’t think he’s a bad person, just a jerk and not someone I’d want to be stuck in an elevator with. Nowadays you have people like Randall Muroe, Adam Savage, Steve Mould, etc. who still dive into speculative physics while keeping it fun and fostering curiosity.




  • I base my opinion here on my experience with the Python discord, which is probably one of my favorite haunts these days. It excels at helping newbies, of which there are many each day, because their questions are quick to answer and can be handled almost instantly by any decently experienced active user. It’s the more specific or advanced questions that languish there, because it’s less likely that someone experienced with that particular domain will happen to be online. It doesn’t need to concern itself with archival quality because no one expects answers to be referenced later.

    So I think both types of communities can play to their strengths without diminishing their quality. The chat rooms can answer the simple, open ended questions that don’t bring value to SO’s database of knowledge, and the more complex and advanced questions can have a better chance of being seen and answered with valuable insight on SO.


  • I think the issue is that, as a new dev, you also have no idea where to go for the type of help you need, and SO is always at the top of the search results. I’ve found that discord servers are better for helping newbies because it allows more experienced users to interactively teach them how to ask questions and how to read documentation. Handing someone a URL and saying “look it up” is pretty helpful for a newbie, but that’s discouraged on SO since answers are much more permanent and links degrade over time.

    Maybe SO needs some way to direct those who “don’t get the site” to a more chat-room like community where they can get their very common questions answered quickly rather than posting a duplicate question that no one wants to take the time to fully explain in a single answer.



  • I don’t think the length of program matters so much, especially with type hints making it easier to maintain larger projects.

    That being said, it’s pretty well known in the community that distributing any kind of end user software is a nightmare with python (though there’s a small group of people who insist that it’s not that hard to get people to install python to run their program. Those people are nuts).

    The biggest reason I use python for as many projects as is practical, though, is because it has an incredible community that I love to interact with. Unless I truly need something to be scalable, python is always going to be my hammer of choice.


  • I’ve learned to be very judicious about using libraries only if they’re well established (unless I’m working on a personal project and don’t mind taking a chance with a smaller library). I do think one should think very carefully before adding a dependency, especially in webdev where you have a million bloated frameworks that have a handful of things you actually need. That being said, a trusted dependency is better than trying to reinvent (and maintain) the wheel.