send a tag suggestion

which tags should be associated with each other?

why should these tags be associated?

Use the form below to provide more context.

#cloud

kb0
@kb0

headline? who needs em

> yo!
good evening cohost crew! it's ya boy 
> kano
coming in for the long haul!
spent a bunch of time at various big techs, but prefer working on what I love most.
my deep technical background is in all things web, data engineering, cloud/platform & computer architectures, and progLs -- and driving teams to be their healthiest + bestest doing it.
on the side, I produce music (since 2018)! I focus on "essence", which tl;dr is layered melodic sound design that flutters up high and booms down low. 
> highlights:
- too many to list tbh, did X projects and have saved stacks $Ym + Z time
- next.js ftw
- edge AI/CV src -> Rust ingest via k8s
  -> data lake -> semantic layer
  -> website (you!)
- Δ ???
otherwise: I play games (variety!), fly virtual jets, watch anime, support my idols, ball out with friends, and live my best life!

I hoped to post about various tech topics and random things I learned while solving super simple or super complex quests on my grand campaign to learn and grow, because
1) curiosity is best captured in stories, and
2) it may help the odd fellow traveler of these distant, unexplored lands. probably. maybe.

but it's okay that I didn't! I was so busy with life and projects to generate material for this, that it became too late... at least for this site >:D (see if you can find me somewhere!)

that code block looks like a top 😌
Stegosaur
@Stegosaur

Simplicity

I'm working on several long-form posts about various Cloudy things, but with Amazon now swinging the axe in its AWS division, there's something I want to emphasize for all the engineering folks out there, summed up nicely by Steve Jobs:

Simple can be harder than complex: You have to work hard to get your thinking clean to make it simple. But it’s worth it in the end because once you get there, you can move mountains.

I spent the first stage of my career cleaning up technical debt at various clients and organizations, which in turn gave me an understanding for just how short-sighted most organizations operate. Companies spend gobs of cash on IT while complaining it's one of their single biggest expenses (occasionally alternating with labor costs for the top spot), but rarely invest the capital to reduce those costs through simplification. In an effort to have the most marketing buzzwords tied to their products - NFTs, AI, microservices, blockchain, (public) cloud, etc - they chase fads and saddle their engineering teams with tech after tech and no clear support model or timeline in sight.

All of this is to say that as debts are being called in and this manufactured recession begins in earnest, simplicity is a virtue to be elevated up and worked towards. Simplicity saves the organization money on every conceivable metric:

  • Systems require fewer engineers to maintain and support
  • Lower need for technical support, as users are more likely to grasp and utilize resources independently
  • Substantially less capital investment, as extraneous features or supplemental products have been removed
  • Lower TCO, as workloads are placed in cost-appropriate areas and asset lifecycles are extended to reflect the slowed pace of improvement

Simplicity ain't glamorous, but it's kept me busy and relatively employed thus far, at least so long as organizations had buy-in for it. As the era of explosive growth ends and value-driven operations begins for the tech sector, simplicity will be a far more valuable skill than expertise on the latest technology fad.