@argiris Sure.

So Agile and Waterfall are two methodologies on how to manage a project.

In waterfall (the older of the two), one phase was only started when the previous was completed. Like water that falls down a cascade.

Requirements engineering => concept => design => development => quality assurance => operation => support (roughly speaking).

Once the product is in phase of the customer, feedback is collected and the cycle repeats.

@argiris Frustration with this led to some folks sit together and come up with the Agile Manifesto (easy to find online).

This methodology worked different. Especially with shorter feedback cycles, inspection and parallelisation.
Teams were able to handle the requirements themselves (led to DevOps).

(N.B. it can be applied to any project, not only building software).

But in reality, companies are reluctant to go all in on this.

@argiris Development doesn't start before design hasn't done requirements engineering with the product manager. Developers are only involved once some design crops were thrown over the wall (like in waterfall).

Quality Assurance only kicks in after a sprint to test for regression (manually, because ain't no time for testing and developers must not write the test suite).

After deployment the whole company frantically clicks through the UI. No test plans or anything.

@argiris So what I observe is a mix of them:

Basically waterfall but with shorter cycles.

When I am interviewing companies (because looking for employment) I'm asking on how they set up their process.

You can be lucky if you find disciplines outside of development and support.

Designers are shared among teams. QA is done by interns or students. Devs are responsible for Ops.

The waterfall aspect here is this:

@argiris I left that company when it grew massively without much change management.

Processes like Scrum of Scrums, SAFe etc feel icky.

So yeah, some frustration in the above from what I've experienced as developer.

Given that Vitaly is doing consulting and Charis is also working in Smashing I can imagine they went through more variants. Wouldn't be surprised if NDAs prevent them from talking about it.

@argiris I can only remember one company that ran Usability tests with people to validate assumptions before too much time was invested.

In that company, different disciplines got a seat on the table when requirements were talked through (to avoid designing things that would be too complicated to implement).
Testers could formulate expectations on how things were tested.

That would be an agile approach (according to Scrum).

@charis I feel like I want to have better tools that don't run risk of getting bought up and closed.

Plus, that there must be closer communication within product teams.

Still too much „agile waterfall“ in the industry.

@changelog
Speaking of juice:

The „changelog“ at the end of these episodes are enough to keep me hooked 🪝

@jerod

@matt
Wait, that wasn't satire?

@darius
An … entertaining subject to say the least:

https://github.com/kdeldycke/awesome-falsehood#dates-and-time

@bekopharm
So it could happen to PyPI (Python), RubyGems (Ruby), Crates (Rust), … too :-(
@Johann150

@mathew
Web3 is going great!

CC @rysiek

@clacke
Exactly that is what was on my mind!
@Gargron @erosdiscordia @rysiek @homegrown

@rysiek
That's why I get really upset once a company enters the stock market.

They stop improving the product for their users, but only look at maximising shareholder value.
@erosdiscordia @homegrown @Gargron

@homegrown
There was a second term next to decentralisation… distributed? Can't recall offhand.

I concluded that I'm looking for services that I can host myself (on premise) and allow for data transition.

This way, I'm free to defer the hosting but always have the option to take matters in my own hands if needed.

Now, that is easier with FLOSS.
But there are so many programming languages!
(I already turned into a polyglot).
@rysiek @erosdiscordia @Gargron

@zkat
A few years ago, some researchers looked at how many contributors were active per project.

Median?

1

@astro
I actually pulled my code off of GitHub (and archived it there) since I got no contribution whatsoever.

Not surprisingly when you consider that the median number of maintainers is 1.

Working across different Gitea instances is an interesting subject.
I was wondering whether WebMention or so could be used for the communication part.

Or we go back to classical mailing lists with all their downsides.
@dimitrisk @rysiek