← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 108
  1. At Ably, we’ve solved production token streaming, so you don’t have to.

  2. Disclosure I work on AI token streaming at Ably.

  3. The ‘cloud-native’ architecture of the last decade is built on a 20-year-old assumption: that state lives in the database, and compute is stateless.

  4. Agents used to be a thing you talked to synchronously.

  5. All your agents are going async

    Agents used to be a thing you talked to synchronously.

  6. You are the bottleneck

    The agent can produce code faster than you can review it.

  7. Apparently writing code is cheap now.

  8. How is is possible that we’ve made incredible gains in the performance of models, but virtually no gains in the infrastructure that supports them?.

  9. We’ve all seen the complaints.

  10. SSE sucks I’m just going to cut to the chase here.

  11. Disclaimer, I work for Ably; so I’m intimately familiar with the tech I mention here.

  12. Realtime features make apps feel modern, collaborative, and up-to-date.

  13. Phone call asymmetry

    You get a phone call, but you’re away from your phone or you can’t answer it right at that moment.

  14. Every programmer should know

    Programmers should know a lot.. apparently.

  15. …and why you really should!

  16. You don’t need CRDTs You don’t need CRDTs for collaborative experiences.

  17. Background I was first attracted to the dumbphones after seeing a series of articles on Hacker News.

  18. There’s a rise in hosted database companies like Supabase, Neon, Turso, etc.

  19. Miro and Figma have a bunch of collaboration features, in this post I’m going to break down two of those features and look at what you’d have to think about when building these into your own apps.

  20. Streaming data aggregation

    Imagine you’re presented with this problem: Design a system that can show the top 10 most popular songs over the last 10 seconds on the homepage of a music streaming service.

  21. Some talk of one way and two way doors, but I prefer the ’egg test’.

  22. Go 1.21 includes structured logging (with levels) as a standard library package.

  23. So, you want to deploy on the edge?

    Application developers often deploy their apps into a single area, generally represented by a handful of AZs in a single region.

  24. Theory of a program

    The building of the program is the same as the building of the theory of it by and in the team of programmers.

  25. Radical and incremental change

    The allure of radical change Radical changes are exciting.

  26. Writing confidently with ChatGPT

    An AI language model As an AI language model designed to mimic human conversation, ChatGPT has encountered its fair share of criticisms.

  27. I work for Attest, we split our engineers largely down the seam of Backend and Frontend.

  28. Aggregates: one piece of code design

    Most tips for code design exist to keep a lid on the exploding complexity of our systems.

  29. Please don't write "point of view"

    There are some hills I am prepared to die on, this is probably not one of them, but it is irritating as hell.

  30. This post is cross-posted from the Attest Product & Technology medium publication.

  31. Addicted to on-call

    Abstract This is an explanation of the systems that lead an organisation to become addicted to on-call.

  32. Tragedy of the codebase commons

    Tragedy of the commons is a situation in which individuals have access to some shared resource.

  33. Consistently executable interviews

    Hiring is important for a business, it’s a high leverage activity that makes other activities easier or faster.

  34. usable java setup vim

    Vim + Java This post covers a usable vim setup for writing java.

  35. docker login error on m1

    After updating my m1 mac, and docker, the docker login to private repo commands started to fail. 1 Error saving credentials: error storing credentials - err: exit status 1, out: Post "http://ipc/registry/credstore-updated": dial unix /Users/user/Library/…

  36. power distance in comms

    Penduluming feedback In my career I’ve received feedback on my comms.

  37. penduluming

    One of the mental models I repeatedly use is the idea of a pendulum.

  38. santander cycles app

    My TfL Santander cycles app stopped accepting my credit card details. symtoms When trying to pay for 24hr cycle access the app navigated to a ‘register card details’ page.

  39. email workflow

    10 years of gmail For 10+ years I was a gmail user.

  40. change the battlefield

    If you don’t like the game, change the battlefield.

  41. One of my wonderful (and very self-reflective) colleagues reached out to me to ask; I tried to explain something in a PR, but I can see from the next question they asked that they hadn’t understood my first explanation.

  42. when to share your mental model

    A mental model is a like an analogy, it’s a shortcut to understanding.

  43. who wrote this shit?

    This post is a response to Philip Heltweg’s “who wrote this shit” post.

  44. The best most useful feedback follows a simple formula.

  45. product ideation is dysfunctional

    Ideation in product management is a broken tool that does not “create ideas”, as it professes to do.

  46. If you can find the right language to explain a concept, you can quickly bridge the gap in you team members’ different perspectives.

  47. positive and negative freedoms

    We want to give our teams freedoms, but taking some things away can also be freedom.

  48. failure demand

    I’ve been looking for a concise way to describe: “teams that ship a feature should be responsible for the long-term success of that feature, including the customer ops caused by stuff missing from the feature”.

  49. Too often your fear of a component that you don’t know influences how you design your system.

  50. vuepress search h4

    Vuepress’ default theme only searches h1 to h3.