← Înapoi la Urmăritori

Cel mai recent articol

Ultima verificare

Urmăritori 0 urmăritori
Articole: 69
  1. Art from AI

    An attempt at making something amusing by reusing snippets of AI-generated text.

  2. What, if anything, has the impact of OKRs been for software teams that have adopted the practice?

  3. What to say

    If you want to do a talk at a software conference, it’s not enough to figure out what you want to talk about.

  4. Playing Turing’s imitation game 24/7 sucks.

  5. Politeness is supposed to be symmetric.

  6. How do we deal with schemaless JSON documents in applications that continually evolve?

  7. How you will leave

    I accidentally discovered a poem about human connection in the middle of all the abstracts submitted to a conference.

  8. I propose a radical new heuristic to be applied before replying to things online: ask yourself if the original poster could already know.

  9. Book clubs are great in theory, but they’re hard to do in practice.

  10. In C#, nullable means something very different for reference types and value types, but the syntax is the same for both.

  11. The typical ASP.NET Core Web API relies heavily on at least two kinds of “magick”: model binding and generation of OpenAPI documents.

  12. Book heuristics

    You can’t read every book.

  13. When someone uses a big word like socio-technical, you would think it would be a starting point for discussing interconnectedness, adaptivity, non-linearity and emergence in those systems.

  14. What's a tomato?

    Sometimes a tomato is just a tomato.

  15. When we connect software systems through APIs, we also connect the people who work on those systems.

  16. The banana test is a simple heuristic to distinguish gimmicks from lasting value.

  17. What’s the opportunity cost of being swept up in hype?

  18. Inspirational math

    A few words about self-help math.

  19. Drift into debt

    The passing of time is the greatest unsolved problem in software.

  20. What is autonomy for a software team?

  21. Code, alas, is dead.

  22. Let’s never discuss if programming is art or science again.

  23. I am coming to terms with being a programmer.

  24. Multiselfing

    On identity and context-switching during the pandemic.

  25. Conway's mob

    How and why intra-team mobs can help fight the rigidity of many software organizations and their code.

  26. Into the tar pit

    A critique of “Out of the Tar Pit”.

  27. JSON data can be represented in many different ways in a .NET application (e.g. explicit JSON model, JSON-friendly DTOs and plain old dictionaries).

  28. We’ve messed up JSON serialization in .NET.

  29. A description of my identity crisis as a programmer, why I’ve rejected craftsmanship and crafting, and what I think we should do instead.

  30. The world of programming contains realms of strange values for things that may happen or may have happened, collections of things, things that may or may not be things, and so forth.

  31. What does adding or multiplying integers, concatenating strings, appending lists and composing functions have in common?

  32. LINQ to Nullable

    What does it take to enable LINQ syntax for Nullable?

  33. An implementation of Peter Henderson’s Functional Geometry in F#, with a step-by-step guide to make an SVG reproduction of Escher’s Square Limit.

  34. Donkey code

    A fable about how code quickly can deteriorate under new requirements if we don’t have a conceptual model with the right abstractions to express both new and old requirements.

  35. The problem with null.

  36. Appeal to pragmatism is a logical fallacy.

  37. A string in a program is never just a string.

  38. Technical debt is a symptom.

  39. Thinging names

    We’ve got it backwards when we say that “naming things is hard”.

  40. Diamond mirrors

    An implementation of the Diamond code kata in F#.

  41. Using extension methods in C# to implement a poor man’s version of aspect-oriented programming.

  42. Rethrow recoil

    Fixing an issue with rethrows in the approach described in the previous blog post.

  43. LINQ to Exceptions

    A way to attach and compose exception handling blocks to Funcs using extension methods.

  44. Read blog post

  45. Read blog post

  46. Read blog post

  47. Read blog post

  48. Read blog post

  49. Read blog post

  50. Read blog post