Amazon Web Services (AWS), is a subsidiary of Amazon.com, which offers a suite of cloud computing services that make up an on-demand computing platform. It costs very little to get started, offers about 1 zillion different products and is the absolute end all of cloud computing.

System design using aws

Stuff about system design.

Sa pro topics

The AWS Solutions Architect Professional Exam blueprint covers the material by topic... so, triaging and thinking about the material got reworked... by topic. Here is is:

SA Pro Topics Posts:

Devops

Back in the day, we just called it configuration management. Or the build system. These days they add in a bit of software defined infrastructure and it is a whole new thing. Not in my book, but whatever. There is not doubt it is useful and important and tools like travis and gulp and the ever present git make it a straightforward affair. And I still love writing scripts that automate the whole thing!

Devops Posts:

Media services

Media Services Posts:


Scrum

Scrum is a management and control process that cuts through complexity to focus on building software that meets business needs. Management and teams are able to get their hands around the requirements and technologies, never let go, and deliver working software, incrementally and empirically. But the tight definition of Scrum Master and Product Owner combined with a good process defintion isn't enough to succeed... I'm a big fan of ScrumBan.

Kanban

For one, Kanban is NOT an Agile tool, framework or methodology—in fact, it’s not even derived from software development practices. Instead, Kanban came out of lean manufacturing techniques made famous by Japanese automakers who used it to manage their workloads. It is so silly simple that it makes me smile. Bottom Line: good stuff... kanban is.

Leanux

I love manifestos. And the any manifesto that goes like this has my love:

  • Early customer validation over releasing products with unknown end-user value
  • Collaborative design over designing on an island
  • Solving user problems over designing the next “cool” feature
  • Measuring KPIs over undefined success metrics
  • Applying appropriate tools over following a rigid plan
  • Nimble design over heavy wireframes, comps or specs