-
Practically speaking, I’d count depot_tools from Chromium also as something of a package/depandency-manager. Or at least it can be used as an alternative to one for some projects.
-
Usually, if you read up on the pre-story, the people beeing scolded have likely repeatedly and diliberatly ignored some rather clear and obvious guidelines for linux kernel development. I mean, what are you going to do if someone will insist on not understanding gentle nudging in the right direction? At one point you gotta escalate, …
-
-
That is a quite passive aggressive. I prefer hearing someones opinion, rather than getting the silient treatment.
-
-
-
The valuable thing about scrum is, that it gets everyone involved into a conversation in regular intervals. Other than that, everything else is still about people, … both, for good and for bad.
-
And the scrum guide, linked in TFA, even makes that clear. Unfortunately people who practise scrum do not make that clear, and use the Scrum meetings and artefacts to centralise responsibility and hide behind a process.
It seems that Scrum belongs in a category with Agile, Object-Oriented Programming, BDD and others[*] where the thing as-described is hard and has lots of value once you’ve mastered it, the thing as-practised is easy but has little value, but has the same name so lets you claim to be doing the hard-and-valuable thing. Eventually everybody notices that the easy-but-worthless thing is not helping, so claims that the thing never had any value and reject it.
Scrum-as-described is a baseline process, along with a process improvement framework for a self-organising team to frequently adapt the process to meet their particular needs. Unfortunately, self-organisation and process improvement are difficult skills that are not quickly mastered. Therefore Scrum-as-practised is introduced. Scrum-as-practised is the baseline process forever, with decisions made unilaterally by the product owner, daily status meetings, and fortnightly blame games. Scrum-as-practised is not very useful[**], therefore Scrum is bad.
[*] I would include Free Software, except that Free-Software-as-practised goes by the distinct name Open Source.
[**] Even Scrum-as-practised is useful in many contexts. It provides a safe (pun intended) way for a legacy business to approach an “agile transformation” without completely disrupting middle management and the project office, nor the existing technical functions that have grown a culture expecting those things to exist. When you’ve worked on the “here’s the list of features, see you in 18 months” project, fortnightly releases and a guidebook on how to achieve them really are beneficial.
-
-
Why not try to implement a data structure that might be better suited to the stye of development? Fingertrees maybe? https://github.com/freebroccolo/fingertree.rs
-
Having a transparent http proxy as an option to speed up the installation of multiple machines is a valid use case, and can work wonders if you only have a slow internet connection.
-
Why are large software projects not managed like the Linux Kernel? The Leading Manager should be a coder that accepts or rejects patches, that person would at least have an overview about the state of affairs, …
-
Reading the Headline, I expected this to be about making Mars a habitable planet, … ;-)
-
LibreOffice Draw has quite powerful options for editing PDFs, while maybe not completely in the spirit of this post, I’d definitely add this to the ‘Documents’ section. I only recently noticed this feature of Draw, before I always had to resort to OSX preview for my (simple) PDF editing needs.
-
Also nice, and not mentioned: https://stackapps.com/questions/3610/stackdump-an-offline-browser-for-stackexchange-sites
-
IMHO this paper is rich in words, but poor in actual information about the process. Feels more like a squeeze page for mgt. types, rather than a technical paper.
Most of them were like that since they were presented to such people. Some inventors and early users ended up at Software Engineering Institute doing things like Capability Maturity Model and Personal Software Process. I shared this for the data on what the method achieved mainly targeted at those who read my Cleanroom submissions or were interested in such results.
For learning about it, I put the Stavely site in the text field for a basic summary. The best place to learn it is Stavely’s book, though. It’s well-written. One person here tried to put together a description and examples in Python. Almost all the intro links that aren’t process/management oriented are dead these days. Part of the decaying, Old Web.