chazu

6 ms·

1.
by chazu 9mo ago
Legally prescribed pharmaceuticals, caffeine, lately nicotine. I also have to start working immediately when I sit down - and continue working until the day is over. Any prolonged break risks taking me out of my resource state. It's gr
2.
by chazu 3y ago
Absolutely - anyone who focuses this much on personal life during an interview is almost assuredly clueless as to how to manage people.
3.
by chazu 3y ago
I've got one of each and they are unquestionably the best things I've made, done or invested in.
4.
by chazu 4y ago
I'm consistently shocked by the number of people who have never heard of this principle. Introducing arbitrary numerical limits (emphasis on _arbitrary_, as performance limitations or other actual requirements obviously trump this rule
5.
by chazu 4y ago
Examples of issues Ive seen in the wild because people violate this rule include payroll systems with an arbitrary maximum number of pay codes and review app systems with a static number of review apps. Just like every other heuristic in so
6.
by chazu 4y ago
Cue is one of the most exciting developments that's impacted me professionally in recent years. I can't advocate for it enough.
7.
by chazu 4y ago
Not sure what you mean. Sometimes the word API is used in one sense, sometimes in another. It's a useful distinction insofar as it allows you to talk about APIs as things used by programmers. I find many developers have a hard time und
8.
by chazu 4y ago
I want the author of htmx to get together with the guy from pandastrike and rant about the misuse of REST for an hour a week. It would be my new favorite podcast.
9.
by chazu 4y ago
An API is also the interface used by humans to create programs. When you use a library, you're using its API. This sense of the term API is often lost.
10.
by chazu 4y ago
Very cool - thank you for sharing. I like the idea of task-based benchmarking for UI toolkits, and I'm also happy to see more tview code for me to study.
11.
by chazu 4y ago
90% of SREs and SRE managers haven't read the SRE book(s). 99.9% of folks hiring SREs or starting SRE teams haven't read the SRE book. The SRE book (and its sequels) say quite plainly what SRE is and isn't. They also say that
12.
by chazu 4y ago
> From the productivity standpoint, it is not acceptable that a Machine Learning engineer or a Full Stack Developer are expected to know Kubernetes. Or that they need to interact with a Kubernetes person/team. I agree - these things
13.
by chazu 4y ago
> one could argue that the role of sys admins just got more specialized Read the introduction to the SRE book, available free online [1] - and you'll see that SRE is defined _in contrast to_ systems administration. Its specifically
14.
by chazu 4y ago
That story was truly a horrific vision of the future.
15.
by chazu 4y ago
Has this been translated into English? Cursory googling returns nothing.
16.
by chazu 5y ago
Agreed - this idea is often cited by fans of the book 'Team Topologies'. Its important here to distinguish between the idea of _an_ internal platform team and a _platform engineering_ team. A platform team is any team which provid
17.
by chazu 5y ago
This looks great and I hope to deploy it and kick the tires soon, thanks for sharing. Currently I've been using movienight[1] for this, but it sounds like your app is much more feature rich. [1] https://github.com/zorch
18.
by chazu 5y ago
ECR borked for us in east-1
19.
by chazu 5y ago
Newer solutions which use abstraction layers like postgREST will hopefully result in easier migration down the road - but I doubt most products/projects use such a thing.
20.
by chazu 5y ago
This. I went down this road for some time before I reached a point with Pharo where I feel comfortable doing things their way.
21.
by chazu 5y ago
You don't need any boilerplate to write an operator - you can write an operator in any language. I've written several in python and they all clock in under 300 sLoC
22.
by chazu 5y ago
Thanks for the leads on this - very excited to look further into it.
23.
by chazu 5y ago
These projects are a source of fascination to me, however a persistent question for me is how do these more symbolic approaches to cognitive modelling figure in today's world of ML and data-driven AI? I'm very curious to know wher
24.
by chazu 5y ago
This person gets it. Which is rare - do you want a job? :) But seriously, you hit upon something which is important, but very hard to communicate/admit - a big part of making the "DevOps Transformation" happen - which is a ch
25.
by chazu 5y ago
This is why I like the 'platform engineering' meme - much better way to frame the value proposition. See: Thoughtworks' blogs and podcasts on platform-engineering-centric topics.
26.
by chazu 5y ago
This is absolutely wrong - DevOps is not a job title. At least it shouldn't be, as anyone in the sector will tell you. The conflation of DevOps responsibilities and specializations with SysAdmin work is the reason why the vast majority
27.
by chazu 5y ago
GitOps is a deployment methodology. Sure its a buzzword, but product devs have plenty of those as well. I _do_ agree that DevSecOps is a pointless concept - as is FinOps and other xOps crap - its become a way to throw work over the wall, wh
28.
by chazu 5y ago
You hit on the most important thing about DevOps: DevOps is not a job title - as any DevOps person will tell you. Obviously it _is_ a job title, but what they mean is that it isn't supposed to be one. Its supposed to be a way of lookin
29.
by chazu 5y ago
Talk about myopic.
30.
by chazu 5y ago
I suggest Accelerate, Balancing Agility and Discipline, The Phoenix Project and the OG Continuous Delivery book by Jez Humble and David Farley.

More ›