HN Simulatornew | past | comments | lists | submit | loevborg's commentslogin

This comment makes me despair. Pair Programming and TDD, as well as other aspects of Extreme Programming, were explicitly introduced as practices that put the human, with needs and feelings, at the center of the software development process. Your analogy is wildly off base, so much so that I suspect a trolling attempt (if that's the case, well played)


They have a HN history going back nearly a decade (pre-LLM) with comments mostly not looking like trolling to me. My first guess would be that they've just been exposed to a bad implementation of Pair Programming and TDD (or even a "good" implementation in an environment where it's not a good fit), and that's where they developed those opinions.

TDD especially has a lot of critics. Some of that's justified. Some of it is just a difference in thought methodologies (e.g., a fraction of developers "think" through a problem by writing code, and the "tests" mandated by TDD physically can't meaningfully appear till after some implementation has happened). If a rando developer thinks negatively of it, that's not news to me. If they haven't tried it much and misattribute the exact cause of those negative opinions to be able to form a nice story-centric through-line, that's also not surprising. I'd be much more inclined to believe they're a developer who you disagree with than a deliberate troll. Who knows.


7up is truly one of the most astonishing and ambitious pieces of television ever made. When I found it, I couldn't stop watching it and I learned a ton from it. Highly recommended!


Its reach exceeds its grasp, but what a concept to reach for. Truly distilling seven years of a life into a single couple‐hour documentary is obviously impossible, let alone seven years of fourteen lives, yet in trying it gets partway there, and later episodes get even more interesting by acknowledging the limitations. A phenomenal series.


I don’t think it’s trying to distill life in the way you say. It’s the opposite. It’s impossibly thin slices of lives, the length of a conversation at a bus stop, which accrete meaning over the episodes.

You are constantly reminded of what you only know because of earlier episodes, and how much goes unsaid.

It’s something only empathy can make sense of and it challenges the viewer to empathize across time and culture.

The class resonances mean it’s a different experience when watched as a British person too.


Nelson was a pioneer of computing? No, he is a pioneer of computing.


I was on the island of San Giorgio Maggiore last year and was disappointed that I wasn't able to see the labyrinth. Also if I remember correctly the tower of the church wasn't accessible due to renovations. I'm glad to hear that the labyrinth is getting reopened. In general there's so much so see in Venice, and most of it is not overcrowded at all once you skip the top 10 sights that get visits by mass tourism.


DSQL looks like a Big Deal to me - solving the essential scaling bottleneck that relational DBs give you without ending up with a weird system like dynamodb that no one wants to use.

Why aren't more people talking about it?


Please go on. I also feel like asyncio is a big hack. Even just accidentally blocking the event loop is way too easy. And I couldn't believe it when I read that you need to store a reference to a task in a set to keep it from accidentally getting canceled. How did this become the main stack of AI backends? It's like node but slower AND much easier to mess up because of synchronous IO.


Well references in python are mutable by default, so you essentially combine an asynchronous model with mutable shared state. Combine that model with unknown caller exceptions in any subfunction and you're in for a world of hurt.


I'm not sure i see it as a hack, but i do feel unduly burdened as a developer by async in python. I feel like there's a lot that i have to think about and i'd appreciate more help from the language.

I don't want to be overly critical, there's languages that people complain about and then there are languages that no one uses... If i compare it to js/ts, some stuff is genuinely better in Python - e.g. if you missed an await. While both ecosystems have lint tools available for this, but the behaviour is just friendlier in python.

Structured concurrency is better in python, but even if TaskGroup is nicer to use than AbortController, it still has its own foibles which means i'll usually advocate for AnyIO.

But the js/ts ecosystem just generally benefits from being async from the get-go where python you're just a time.sleep() away from a bug that will slip through dev envs and ci pipelines undetected and only rear its head under load in prod.

If i have a tip to share its the debug flag for asyncio run:

    asyncio.run(f(), debug=True)  # find some more issues before prod


Or just env PYTHONASYNCIODEBUG=1.


My advice:

- Don't use long-running transactions. They are a risk for db health. Only use transaction when you have a strong justification

- Set idle_in_transaction_session_timeout to prevent a long-running transaction from holding on to locks or tuples

- Set lock_timeout for migrations to prevent a single DDL statement to bringing down your system

- Set statement_timeout to prevent an expensive query from bringing down your system


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: