Twitter being acquired by Musk and rapidly becoming a cesspool of disinformation got me thinking about who controls my content on social media. My stance on on my blog had always been very clear. I was the owner and cross-posted in other places I chose. Social media could not only monetize my content, but I didn’t keep any trace.
I decided to change that. I now post a piece of information I find interesting once per half-day on social media I choose–excluding Twitter, and collect them a newsletter that I publish weekly. I write additional context or my thoughts on each item in the newsletter, a possible incentive over the social media "cross-post."
I delivered issue #1 on October 11th 2023. This issue marks a milestone as it is the 100th edition. I hope there will be many more. And now, enjoy!
- Linux Foundation Announces the Formation of the Developer Relations Foundation
-
Reflecting on data from the 11th Annual State of DevRel Survey, 2024, as well as direct feedback from the global Developer Relations Community, the DRF work over the last 12 months has focused on the following challenges within the profession:
- Connection - DevRel connects product, marketing, support, engineering and sales to align with business goals. However, 50% of survey respondents expressed a struggle with the awareness of the impact of DevRel.
- Misunderstood - The profession faces uphill battles with perception and clarity of purpose
- Alignment - There is a strong need to align with measurable business results. 61% of DevRel professionals in the survey agree they are challenged to prove impact.
I believe it’s amazing and it could have been very useful to me ten years ago. When switching from engineering to Developer Relations, I had to discover a lot by myself. Unfortunately, I’m afraid it’s too late and the ship has sailed: hard-to-measure impact and long-term investment aren’t popular in the current unstable world.
- Ces recruteurs qui agacent les candidats
-
Old, but I still feel the author. I wonder how the tension between recruiters and candidates will evolve in the current state of the world economy.
- The Real Cost of Poor Documentation for Developers
-
I read lots of time that developers don’t like to write documentation. I met a couple of "Clean Code" fanatics who refused to write comments in their code, because they claimed it was self-documenting. Spoiler: it wasn’t.
However, I personally like to write documentation, and I don’t think I’m alone. One can be as proud of one’s documentation as of one’s code.
- What are OKLCH colors?
-
TIL. I only use RGB for my needs.
- Everything I know about good API design
-
- APIs are hard to build because they’re inflexible but must be easy to adopt
- API maintainers’ primary duty is to NOT BREAK USERSPACE. Never make breaking changes to public APIs
- Versioning your API lets you make changes, but imposes significant implementation and adoption barriers
- If your product is valuable enough, it doesn’t really matter how good your API is, people will use it anyway
- If your product is badly-designed enough, it doesn’t matter how carefully you design your API, it will likely suck
- Your API should support simple API keys for authentication, because many of your users will not be professional engineers
- Requests that take action (particularly high-stakes action like payments) should include some kind of idempotency key to make retries safe
- Your API will always be a source of incidents. Make sure you have rate limits and killswitches in place
- Use cursor-based pagination for datasets that might end up being very large
- Make expensive fields optional and off-by-default, but (in my opinion) GraphQL is overkill
- Internal APIs are different in some ways (because your consumers are very different)
I didn’t consider the popular product perspective, but it does make a lot of sense.
I strongly disagree on the internal APIs part, though. Imagine if a team inside a big hyperscaler decides to change an internal API everybody else depends on? That would stir the beast! There’s no dichotomy between internal and external, the factor is in how used is your API.
- How to Name Your Span Attributes
-
I mentioned the previous post in last’s week newsletter. If you liked it, read this one: it’s even better.
- Discover great opportunities to become a Cloud Native contributor
-
Here’s a handy site if you want to start contributing to Open Source in general and to CNCF projects in particular. For example, if you’re a backend Java developer interested in OpenTelemetry, you can run: https://clotributor.dev/search?ts_query_web=java+opentelemetry+-android to get all open issues you can work on. Simple, but useful.
- New Features We Find Exciting in the Kubernetes 1.34 Release
-
- Features Moving to Stable
- Dynamic Resource Allocation with Structured Parameters
- Allowing Only Anonymous Authentication for Configured Endpoints
- Relaxed DNS Search String Validation
- Features Moving to Beta
- PreferSameNode Traffic Distribution
- VolumeSource: OCI Artifact and/or Image
- Features Moving to Alpha
- Allows Setting any FQDN as the Pod’s Hostname
- Features Moving to Stable
- DocumentDB joins the Linux Foundation
-
DocumentDB is a MongoDB compatible open source document database built on PostgreSQL. It offers a native implementation of a document-oriented NoSQL database, enabling seamless CRUD (Create, Read, Update, Delete) operations on BSON(Binary JSON) data types within a PostgreSQL framework. Beyond basic operations, DocumentDB empowers users to execute complex workloads, including full-text searches, geospatial queries, and vector search, delivering robust functionality and flexibility for diverse data management needs.
PostgreSQL for everything!
- The $69 Billion Domino Effect: How VMware’s Debt-Fueled Acquisition Is Killing Open Source, One Repository at a Time
-
Frightening analysis, and I’m afraid pretty on point. I hope the future proves it wrong. Hope for the best, prepare for the worst.
- Pogocache: Open Source Caching Software with Low Latency and Multiple Wire Protocols
-
Seems like a dream come true, but a wise man commented:
While the initial release and performance claims are undeniably exciting, the true test for Pogocache lies ahead. How will these benchmarks hold up under rigorous, independent scrutiny across varied production workloads? How quickly will the developer community embrace and contribute to the project?