← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 200
  1. Making Unicode things fast

    By “Unicode things” I mean programs that process UTF-8.

  2. Allocations are a dependency

    I like to reduce or eliminate allocations in my projects, which use garbage-collected languages (Go and C#).

  3. So, I am working on this rate limiter.

  4. A follow-up to So, you’re splitting strings on the hot path I have enjoyed optimizing my Go library for splitting (tokenizing) words according to the Unicode standard.

  5. Having used rate limiters a few times, I’ve observed that they must be thoughtfully designed.

  6. Motivated by this Twitter post by Craig Kerstiens CDC (change data capture) tends to surprise in terms of expense on the production database.

  7. Can we make it less expensive?

  8. 90% of physics in 900 words

    I had a physics professor who said the most important skill in science was to be able to characterize a system quickly.

  9. Background: I move between Go and C# a lot, and like to compare them

  10. Recently, I’ve implemented a Unicode tokenizer in in Go and in C#, and my career has been ~equally divided between those languages.

  11. I move between Go and C#, and one idiom I like in Go is tests living alongside the things they are testing, right in the same project.

  12. Apple as MVNO for LLMs

    It’s expected that Apple will be improving Siri in the upcoming iOS 18, exploiting the progress that Large Language Models (LLMs) have made over the past year or so.

  13. Generics as builtin typeclasses

    In the spirit of Go’s ‘good enough’ type system, here’s a thought experiment for ‘good enough’ generics…

  14. Saying true things is hard

    I think the replication & open science movement is great.

  15. Stack Overflow Talent aims to connect the right company with the right developer.

  16. I have a theory that the use of TypeScript de facto makes for more performant JavaScript, by making the runtime’s “type prediction” more accurate.

  17. Having the courtesy to be wrong

    One characteristic I see in accountable managers is having the courtesy to be wrong.

  18. This is a follow-on to my introductory post on championship, please give that a read for background.

  19. Championship

    Engineering and product managers often talk about “ownership” of features, when what we want is championship.

  20. On the occasion of reading Nassim Taleb’s latest book, an anecdote about how he influenced a career decision of mine.

  21. The combination of Hugo & Netlify to host my blog has turned out to make easy things easy, and hard things possible.

  22. Stack Overflow tag correlations

    A tool to discover correlations between tags on Stack Exchange sites.

  23. I recently moved my blog from Medium to static generation with Hugo & hosting with Netlify.

  24. Jargon demo

    Jargon is a Go package with tokenizers and lemmatizers.

  25. The makings of a strategy

    A product process is typically something like Strategy → Discovery → Specification → Build → Delivery.

  26. Toward less injection

    Here’s a habit that may help to reduce the complexity of your dependency injection tree.

  27. Alikewise (dating by the book)

    Thank you As of December 2016 we have shut down Alikewise.com.

  28. KPIs are software

    It’s easy to think of key performance indicators as a task to be tacked on to the end of a project.

  29. Time well spent

    Critical to developer and company success is the idea of time well spent.

  30. Lore

    Code has a user experience.

  31. Decker, for a prettier Twitter

    I made a Chrome extension which makes Twitter.com’s UX more tolerable, called decker.

  32. Nulls are a notorious source of bugs in many programming languages.

  33. Versioning is, right now, merely a human label.

  34. Apple’s ad blocking API is good for users and bad for Google, in 3 ways:

  35. It appears that Internet advertising is going through a bit of a shakeout.

  36. I like seeing Google Fiber prompt incumbent dinosaurs into boosting speeds.

  37. Jeff has a thoughtful post about open source, security and incentives.

  38. I got trolled by a facetious article on Go on April 1.

  39. I’ve become adamant about making internal initiatives opt-in for the following reason: it brings more information to bear.

  40. We think of bugs as flaws in code.

  41. I was recently directed to a couple of papers on browser ad-blocking software (here and here).

  42. Here’s a nice little technique I came across in developing gen.

  43. Uncanny valley tech recruiting

    As recruiter pitches show up in my inbox, it’s clear there’s a lot of “fake it til you make it” when it comes to tech terminology.

  44. Fred Wilson makes the argument (here and here) that net neutrality is a conservative idea.

  45. My security and privacy tools

    A quick list of the things I use to improve my web experience:

  46. Prompted by this question I got to thinking about methods in C# and Go.

  47. Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp. — Greenspun

  48. I was directed to a thread about a poor soul who started a project in Go, eventually had to hand it off to the community, and discovered that his original source no longer compiled, due to third-party dependencies having changed.

  49. Here’s a smart and funny bit about culture fit.

  50. Megan McArdle describes the understandable discomfort that some tenants and property owners have about Airbnb’ers coming into their buildings.