Notices by Ryuno-Ki (ryunoki@layer8.space)

@alcinnz @smallcircles @ekis Team XHTML here.

I'm more inclined to client-side things. It's incredible what you can build nowadays. And we don't even scratch the surface!

@ekis I did!

Puma and Iodine weren't on my radar before.

I only get nerdsniped by @smallcircles on WASM before so the references to FFI is also something I should learn.

@ekis As far as I know, @buttondown is written in Python.

So implementations such as https://codeberg.org/helge/bovine/ by @helge could have a higher chance of adoption.

Or BookWyrm's implementation in Django (although I see issues with the license). Finally FunkWhale is another project with ActivityPub.

@ekis I have to admit I learned new things, but you got me really confused.

All good now.

@dev @firefish Pushed an update to the repository and will open a PR after lunch

@dev Thanks to @smallcircles who's always encouraging to join the party and @yarmo who kicked it off!

I'm a contributor from time to time.

@dev Oh, hm. Then I must have misread it.

Sure, we have no time pressure to curate the list. I'll check in from time to time.

@dev Hey there 👋

Today someone pointed out to me that @firefish is no longer.

I couldn't reach it at least.

Can you think of another account I could list at https://delightful.club/delightful-fediverse-apps/ instead?

@dev @firefish We can also add a ghost to it and list it as orphaned if you prefer.

In December you said you would stop contributing but I can see commits by you from last month.

@killyourfm @thunderbird See also https://prism-break.org/en/categories/windows/

@killyourfm See you next year! 👋

🤡

@killyourfm Because delivery services receive bad press and cooking is marketed as something genuinely good.

No spin on IT yet.

(Somehow I feel I missed the point)

@aral I think I know someone working on Safari if you feel like it would help.

Could reach out and point to it to see whether it can affect change (because advocate for accessibility, too IIRC).

@cheeaun @eloquence Have you worked on something like this for Pixelfed clients, @dansup ?

@killyourfm Secondary market ftw!

@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 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 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 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).