![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://programming.dev/pictrs/image/8140dda6-9512-4297-ac17-d303638c90a6.png)
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?
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.
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.
Why did they do it?
Just coz.
Seriously though great news and well done to them.
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.
As an aside, I fucking hate that I can’t uninstall this shit on my work Mac. I use another media player and when it’s open the media keys work fine but if I forget to open and and hit play that cursed thing just looms on the screen to remind me that I can’t get rid of it.
Same here, unless it’s a small PR then I like to nitpick 👍
It’s a meme to say “can’t you just” at my workplace
The best code editor is the one that you enjoy using, because you’re going to be using it a lot.
Up the road from the Biden youth centre
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.
What do you mean? Sounds to me like any other tool, it takes skill to use it well. Same as stack overflow, built in code suggestions or IDE generated code.
Not to detract from the usefulness of it just in terms of the fact that it requires knowledge to use well.
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.
If you aren’t getting seg faults, are you really living?
Let’s do it for real then
Wow, it’s really hard to imagine the deep societal harm done by these five people. And you do have to imagine it because it doesn’t exist.