I would argue sequencing is part of the hard part of idempotency, your business context would decide “when” to apply sequencing is good enough (recall monopoly “bank error collect $$$”).

Set and setting is also relevant, most places don’t deal with money or disastrous concurrency scenarios.

Now if you want to argue for a paradigm shift for why we shouldn’t be here to begin with and offer a way to get back to scalable centralized db system we’re all hears.

I fell in love the abstraction patterns that Hex architecture and DDD provide, especially when upgrading a framework that only affected one layer (REST), or when any outside contract changes you only need to change the adapter or port interface layer since everything depends on Core but core depends on nothing.

I love the payoff and risk mitigation of using strong static typed languages for enterprise code and architecture but I recently took over a large Python Flask app. We need to start abstracting layers to replace a 3rd party service with a new one. For hex architecture to work I need to use dependency injection which looks like the main Flask app.py seems the place to wire those up but I don't think it can be enforced without strong PR controls and standards.

Comments URL: https://news.ycombinator.com/item?id=42936854

Points: 2

# Comments: 2

Comments URL: https://news.ycombinator.com/item?id=41936747

Points: 2

# Comments: 2

Comments URL: https://news.ycombinator.com/item?id=39466851

Points: 129

# Comments: 68

Learned that different learning styles was bunk (visual vs auditory). Also, experts are the worst teachers, they are far removed from being in your shoes and do not provide the empathy or the correct scaffolding to start newcomers down the path of understanding a topic.

The biggest success for pedagogy impact is study groups, and tutoring while or immediately after learning something (the accountability of needing to teach someone bumps.your motivation to understand the nuances, plus the act of teaching helps you remember)

https://youtrack.jetbrains.com/issue/DBE-10653?replyTo=27-86...

Comments URL: https://news.ycombinator.com/item?id=38700388

Points: 1

# Comments: 1

We then hired a front end architect who replaced all widgets with react components, changed our checkout to full CSR React, our latency raised for all users, we lost 5% conversion on checkouts that never recovered, then the next step was to build a React service to help render the React, and moved CSR React to SSR React service.

We now have 2 teams to support this. I get there are a list of other tradeoffs but I really miss JSPs.