Idk, if it quacks it might be an undercover nazi-duck

As somebody who has worked a bit with a few microsoft bound teams : it has to do with the teams and their managers.

Some teams were a treat to work with and are completely open to my comments or questions, and ready to serve the user’s needs.

Other teams are terrible. They dont respond, they do whatever the fuck they want or what their managers tell them and pump out garbage that makes no sense to the users.

Dotnet clr, refit, fluint ui blazor, …
All nice teams.
Fluentui ( webcomponents ), wpf, parts of windows teams, …
Not so much

As a firefox user… This.
Calls work now, but dont you dare share a screen in the call.

… But meetings work fine, even if you share a screen. Thanks microsoft.

Youre forgetting 4chan and south park exposing them

I said the same to a coworker this week. If i were to be part or manage an illegal ring like csam, id make my own protocol/app that just uses encryption. Youre already doing illegal shit, go one further so you dont get caught

Haha, nice one.
I was an ace shot… Eventually. ( at least i didnt stand still and was hard to hit, so its something xD )

It all depends on your needs tbh. I personally think the framework mobo is perfect for a powerful 24/7 server. Smb, router, media center, …

I personally dont need something like that and just have an sbc running pihole and smb 24/7 ( +/- 8w@230v power usage )

Still overkill and uses way to much power. Now, as a server that just happens to also be a retroconsole… :')

I agree. Pi5 apparently uses 5v@5A max, which is outside the usbc-pd specs. Not sure why they didnt go for usbc-9v in and use onboard components to convert the power to something lower for cpu ( which i assume it already does from 5v )

Tbh, i cant make an opinion without technical details :')

They probably just waited for the contracts to end hehe :')

What is the power reason if i may ask?

And very delicious! I love the pasta shape in my mouth haha

Oh god yes! Every time im in germany i will stop at an ice creamshop for this!

Welcher lebenswille? :')

Correct! Hence why i said it all depends on the product, the team, the time, money, project, …
Many factors that decide on how to tackle things and the problems :)

Agreed. Depending in what branch or situation youre in you need handle appropriately and cover your arse but also make it work. If i was to work on a timed project, and the project is set to not make the deadline due to spec changes i will report that ahead of tine to cover the teams arses, but at least we can pivot and deliver something that will be useful and up to spec depending on the feedback :)

Im currently trying to steer a product team to have this kind of process. They are working with an ancient piece of software that is slowly being replaced. However, we need to replace piece by piece while the main app is still being maintained because of law and workflow changes. This is why i want them to set the requirements and designs up front a bit so we can make a good analysis of it before development starts so no technical difficulties or questions arise mid development! However, nothing is set in stone and after each small piece ( aka after each sprint ) we have our review and product owners and stakeholders see what we have made and can chime in, causing us sometimes to pivot what we were making.
Best of both worlds!

Agile has its uses, but like everything you need a bit of both. You need a bit of both waterfall and agile.
Example : you need to have your requirements before development, yes. But how far do you go in your requirements? If i were to make all the requirements for my current project ill still be busy in 3 years and will have to redo bits due to law and workflows changing. however , we need requirements to start development. We need to know what we need to make and what general direction it will be heading to a make correct software/code design.

Agile also teaches you about feedback loops, which even with waterfall, you need to have to know that what youre developing is still up to spec with what the product owner is expecting. So even with waterfall, deliver features in parts or sit together at least once every x weeks to see if youre still good with the code/look/design.

Pure agile is bullshit, but so is pure waterfall. Anything that isnt a mix is bullshit and in the end, it all depends on the project, the team and the time/money constraints.

I have terrible friends haha