Back in 2005, I remember working on startups running on Scrum principles. It worked well at the time, we where able to ship, grow the team, and move forward with a nice few-features-per-week cadence, working remotely, on a small team; less than 10. Tt always worked fine, but very centralized and slow, as all-things-dev were at the time.
I worked with ActiveColab in 2007, Skype 2007, Yammer 2009, Trello 2011, Pivotal Tracker 2013, Trello 2016, Confluence 2022, Slack 2013, Google Meet, and sometimes I think, scrum became _less-relevant_ over the years as more advanced product management tools became the norm and the product manager role matured by leveraging them.
These days, it's not rare to see lead developers manage kanban-like boards very effectively, releasing on time, with grace, without the need of a scrum master to coordinate efforts.
I do like asynchronous scrum daily standups using http://geekbot.com on slack, when on-site or/and distributed and doing sprints. I seen this work well on startups going from pre-seed to series B.
Personally, I am fascinated with team dynamics and how they've changed over the years. We are definitely living the best of times as a developer and I still see sparkles of well-applied scrum every now and then that works nicely.
For me, one of the coolest thing about the Robocop movie series is that, each Robocop movie is about the next Robocop. Robocop 1 is about Murphy being the first Robocop, Robocop 2 is about Cain becoming the second Robocop, and Robocop 3 is about the asian looking Robocops -- the third generation.
AI doesn't scale well. Problems get worst as you make your model bigger and more generalized. To make things worst, data, model architecture, precision, hardware, affect your model performance in ways that are hard or impossible to anticipate.
If you watch Tesla's AI presentation, https://www.youtube.com/watch?v=HUP6Z5voiS8, you will notice that they have multiple AI's stacked on each other, which IMO is a step back from truly e2e multimodal AI system. So even with their custom fancy hardware, multimodal is too hard.
I wonder, wouldn't it be better to use geo fencing (using H3), and have the car download the model depending on the zone where it is driving? And optimize multiple models based on "driver engagements"? This could fix the problem of zones where there are particularities in the driving, road, or human activities, and allow for model optimization to happen on a smaller vector space than the whole world. For example, why not have a model for US highways, LA, New Deli, UK, so on.
Tesla also knows where the cars are, and control their expansion plans worldwide, which could inform model prioritization roadmap.
In my mind, it will be easier to test, debug, label, optimize, and guarantee quality to users, that at the end of the day, without knowing exact statistics, I am dare to say spend more than 70% of the time driving around the same county/city/area/town?
One of the most brilliant engineers out there. A true madman with an old hacker mentality that is nowhere to be seen these days, except for maybe George Hotz...
Old days where different, today, it's about leetcode and being overly happy on zoom calls, and playing along investors playbooks... Capitalist only left the hoodies, and that's because another 100m funded startup from their portfolio are selling them.
While garbage in, garbage out may seem like a bad policy to the user, to the AI system, it means that it can have a closed feedback loop, where the final code (the solution) can be linked to the initial input, regardless if the input was garbage or not.
I would say that anything that can be stated as a large-scale supervised reinforced learning problem is a gold mine -- if the output of course, has value and supervision is free.
Tesla self-driving and Comma.ai, from an eagle's eye view, exploit the same concept.
I worked with ActiveColab in 2007, Skype 2007, Yammer 2009, Trello 2011, Pivotal Tracker 2013, Trello 2016, Confluence 2022, Slack 2013, Google Meet, and sometimes I think, scrum became _less-relevant_ over the years as more advanced product management tools became the norm and the product manager role matured by leveraging them.
These days, it's not rare to see lead developers manage kanban-like boards very effectively, releasing on time, with grace, without the need of a scrum master to coordinate efforts.
I do like asynchronous scrum daily standups using http://geekbot.com on slack, when on-site or/and distributed and doing sprints. I seen this work well on startups going from pre-seed to series B.
Personally, I am fascinated with team dynamics and how they've changed over the years. We are definitely living the best of times as a developer and I still see sparkles of well-applied scrum every now and then that works nicely.