Completed the table of contents of the RTOS presentation, so that if you plan to look at it, you know what you will face during your journey 🙂 The presentation should be completed by end of December.
https://t.co/Ih8kHN3X8r
@Sncfconnect Mon épouse et moi-même passons commande chacun avec notre PC, en même temps, d'une carte Avantage SNCF. Résultat : la page web https://t.co/io8PADSNo9 indique à mon épouse : "Vous avez été bloqué(e)." Comment se sort-elle de cette situation ?
Just added a second exercise to the "RTOS for Machine Learning" presentation. This new presentation will be a more detailed version of a previous one, which I'm adapting to a new target, the EFR32xG24 Dev Kit.
https://t.co/VMkHqjT8bt
I've just discovered how easy it is to display my route on the GR34 long-distance hiking trail on GeoPortail. Well done to the development team!
https://t.co/FGppeVhzHu
Route recorded with GPS Logger. Well done too!
https://t.co/wtYf6Bpqwu
Our new Compiler Services team has already been busy during their first few months. Check out our contributions to the recently released GCC 14.
#gcc#compilers#opensource#openmp#openacc#offloading
https://t.co/L9CYUsExIG
Linux 6.6 was released on October 29th. Here is a summary of BayLibre's contributions per SoC family: https://t.co/xc6TrU5YfK #linux#linuxkernel#upstream
Scrum is a cancer.
I've been writing software for 25 years, and nothing renders a software team useless like Scrum does.
Some anecdotes:
1. They tried to convince me that Poker is a planning tool, not a game.
2. If you want to be more efficient, you must add process, not remove it. They had us attending the "ceremonies," a fancy name for a buttload of meetings: stand-ups, groomings, planning, retrospectives, and Scrum of Scrums. We spent more time talking than doing.
3. We prohibited laptops in meetings. We had to stand. We passed a ball around to keep everyone paying attention.
4. We spent more time estimating story points than writing software. Story points measure complexity, not time, but we had to decide how many story points fit in a sprint.
5. I had to use t-shirt sizes to estimate software.
6. We measured how much it cost to deliver one story point and then wrote contracts where clients paid for a package of "500 story points."
7. Management lost it when they found that 500 story points in one project weren't the same as 500 story points on another project. We had many meetings to fix this.
8. Imagine having a manager, a scrum master, a product owner, and a tech lead. You had to answer to all of them and none simultaneously.
9. We paid people who told us whether we were "burning down points" fast enough. Weren't story points about complexity instead of time? Never mind.
I believe in Agile, but this ain't agile.
We brought professional Scrum trainers. We paid people from our team to get certified. We tried Scrum this way and that other way. We spent years doing it.
The result was always the same: It didn't work.
Scrum is a cancer that will eat your development team. Scrum is not for developers; it's another tool for managers to feel they are in control.
But the best about Scrum are those who look you in the eye and tell you: "If it doesn't work for you, you are doing it wrong. Scrum is anything that works for your team."
Sure it is.
We are excited about the great talks planned for Embedded Recipes on September 28th and 29th in Paris: https://t.co/wyyl3Scarc Tickets are still available: https://t.co/OuGp9pWzoe #er2023