Good question, I didn’t even consider that I just used the same language that was in the title without thinking.
Good question, I didn’t even consider that I just used the same language that was in the title without thinking.
There could be an advantage for groups that had males do the riskier jobs because the cost of losing a male is much less than a female in terms of maintaining population.
This is pure speculation on my part though, I have no education here and no idea what I’m talking about.
Outlook
Outlook (New)
Outlook (Newer)
Outlook (Newest)
Outlook (Newest final)
Outlook (Newest final V2)
I’m curious about why you think this. I’ve seen complex multi year efforts succeed and continue to evolve with agile principles in mind. What specific part of agile do you think would necessarily cause the issues you mentioned?
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.
I don’t understand what you mean, why would coordinating across a large group be against the agile principles? It sounds like the main issue here is lack of communication and planning which are both important parts of any process including one based on agile.
Planning becomes more important for a larger project but if you hyper focus on sticking to the plan even if things change you can end up delivering something that is not useful for your customers, so I think the principles still make sense there.
Would you rather have working software or a bunch of documentation? If your software is having outages then by definition it is not working. If documentation is the root cause of that then you should fix that by creating enough documentation to allow your software to continue to work per “working software over comprehensive documentation”. Maybe I’m missing something but I don’t see the contradiction here.
Yes, and daily standups are not a requirement of agile in any way. The whole point is people over process and adapting to change rather than following a plan so if standups aren’t working you should stop doing them rather than following a rigid process!
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.
They found a weak spot in our DNA that is present in 95% of people with the disease. It makes it much easier for some immune cells to go haywire and drive excessive inflammation in the bowels. The team have found drugs that already exist seem to reverse the disease in laboratory experiments and are now aiming for human trials.
Hey at least this is one effect from climate change that will disproportionately impact the wealthy.
Don’t Write Logs by Yourself (AKA Don’t Reinvent the Wheel)
Log at the Proper Level
Employ the Proper Log Category
Write Meaningful Log Messages
Write Log Messages in English
Add Context to Your Log Messages
Log in Machine Parseable Format
But Make the Logs Human-Readable as Well
Don’t Log Too Much or Too LittlE
Think of Your Audience
Don’t Log for Troubleshooting Purposes Only
Avoid Vendor Lock-In
Don’t Log Sensitive Information
The article goes into some nice detail on each of these but those are the 13 practices being advocated.
That’s right! It goes in the square hole
You know, tonight, that specific time of day that happens at the same time every day depending on where you are and what season it is there.
Yeah I was also quite annoyed by that.
I don’t know how to React to this.
Write down any NaN advantages of JavaScript
I haven’t used GraphQL personally but I’ve heard interesting things about it. It sounds like you’ve been burned by it so I’d be interested to hear more about your opinion beyond that you think it sucks if you’re willing to share some more details.
Yes I believe they dragged it to the wastebasket
Exactly, they’re passive aggressive af
It’s too late, we can’t contain it