MASSIVE GIVEAWAY!!
A chance to win one of TWO full copies of Rematch: Elite Edition (PS5) OR a gaming mouse are up for grabs!
To qualify:
- Like, retweet, and tag 2 friends in the replies!
- Follow me on Twitch!
- Tune in Juneteenth around 5pm to enter and win!!
The last 9 months have been wild. Eng advisor -> interim head of engineering -> wrapping up first week as the permanent head of eng.
Back in edtech, where I pretty much belong lol.
Now focused on research-validated literacy software for K-8 students. living the dream.
Somehow, I now have two network racks in my office (my closet is height and depth limited, so I can't use a single 42U and call it a day).
plus side, LACP over multiple 10Gbps links is proving very useful for NAS access to multiple clients.
Time for a new blog post?
But *if* you do, or you see that as you grow/mature your product, or using these tools allow you to invest in other areas that help you best meet your business needs, go live in the clouds!
Just because it works for one product/workload, doesn’t mean it works for all.
As with most things, the question on what your software needs (on-demand compute, virtual compute, containerized workloads, dedicated resources, bare metal, etc) is always about *the right tool for the job*.
Some will say, “don’t start out with [insert cloud compute], it’s overkill”. It *can* be overkill. If you don’t have PMF with a global user base, maybe you don’t need the overhead of S3, global CDNs, and edge services.
I also hate the pompous idea that everyone is poor at delivering features just because we are using different programming languages that sometimes enable us to tackle our largest or most problematic customers and workloads a little easier.