Not actually a minifesto

Devs,

Here's another interesting article that I just read.
http://minifesto.org/

Not sure I would agree with everything especially with calling this a "mini"festo, but I get this author's point. I also would use better terms instead of "killing the baby". Anyhow, just something to read and think about. In essence, fail fast, work fast, better is good (thanks President Obama), and keep your eyes on the win.

Discovering Datasets with Google

Devs,

If you haven't already been keeping abreast of all the data science hype, then I would suggest that you get with it. Although I haven't been able to keep up with the "hype" (and I call it "hype" because everything with computers has been on processing 'data'), this doesn't mean you have to wait for me. I'll catch up eventually. I have just have other priorities right now in this season of my life (aka two toddlers).

Here's an article I enjoyed reading. Cheers!

https://www.blog.google/products/search/making-it-easier-discover-datasets/

True "Agile Development"

Devs,

I'm not going to say much since some developers have the tendency to talk in circles on certain topics like "what is Agile". Instead, I am posting an article that I just read and totally agree with (who is actually one of the founders of the Agile Manifesto). I actually took part in this "experimental" phase when it came out with my first corporate job in Minnesota. From there, I've been on teams in Boston and in DC. There has only been one other team which was a Boston, small business that worked close to the principles of Agile. This is perhaps because the CTO was co-founder of the business.

Therefore, I'm realizing that for an organization to truly be Agile, one of the co-founders must be extremely technical if not a co-founder/CTO.

https://martinfowler.com/articles/agile-aus-2018.html

1. Get rid of the Agile Industrial Complex and the idea of imposing stuff on teams. Let teams work out the way they should work themselves.
2. Raise the importance of technical excellence, and never forget that when writing software, the technology side is really vital, and
3. organize around products.

One area I wish Martin would have highlighted is the importance of "smart users". That is, users are who are aware of how to develop their product to make life easier. I don't mean easier like "make a better car" but visionary like "make a self-driving car". That kind of vision (which requires an imagination - thanks GE) is the kind of easier I'm referring to. Somehow, I thought with more people using all of these gadgets that people would become more creative. I'm still waiting to witness, hahaha.

Enjoy the ride!