- A Byte of Coding
- Posts
- A Byte of Coding Issue 371
Hi-ya,
If you decide to ever publish online, please always include the date you published on the page. It’s frustrating to go on a goose chase to figure out when something was published.
Anyway, here’s the issue.
Made possible through generous sponsorship by:
Published: 19 March 2024
Tags: management
Abi Noda and Tim Cochran explore how to measure developer experience (DX) by surveying developers. Seems like a pretty obvious thing to do, but apparently that’s not the case for many companies.
Some highlights:
quantitative metrics are rarely a good measure for software engineering
two types of qualitative metrics: Attitudinal metrics capture subjective feelings, opinions, or attitudes toward a specific subject; Behavioral metrics capture objective facts or events pertaining to an individuals’ work experiences
free text comments are often most valuable (although probably also the most difficult to process in my opinion)
Published: 19 March 2024
Tags: ai, software development, career
Gergely Orosz discusses the current state of “AI developers” and the unlikeliness that they’ll replace human developer any time soon.
Some highlights:
“AI developers” are mostly a marketing ploy for startups to compete with Microsoft’s copilot
impressive results are yet to be seen
people have been saying developers will be replaced by computers since the 1960s
Published: 15 November 2024
Tags: sponsored, networking, auth, dns
WorkOS’s blog “examines best practices to consider when building in-house as well as a simple alternative” that they provide when it comes to domain verification.
Some highlights:
“Domain verification is a crucial security measure for SaaS providers, ensuring that services are securely delivered to the legitimate owners of a domain”
“Don’t place TXT records on the root domain”
WorkOS offers a simple API you can integrate with to do domain verification
Published: 15 March 2024
Tags: observability, systems
Hazel Weakly presents a new definition of observability and explains why it’s necessary.
Some highlights:
“Observability is the process through which one develops the ability to ask meaningful questions, get useful answers, and act effectively on what you learn”
“Most implementations of “observability” fail because it’s treated as a tooling problem rather than a strategic capability”
observability is meant to make it easier to provider answers to questions that can drive the business forward
Thanks for your Support!
Big thanks to all of the Patreon supports and company sponsors. If you want to support the newsletter you can checkout the Patreon page. It's not necessary, but it lets me know that I'm doing a good job and that you're finding value in the content.