Readit NewsDead Comment
solididiot commented on Solid.js feels like what I always wanted React to be typeofnan.dev/solid-js-fe... · Posted by u/jamghee
<cynic>Yeah React is already so last year.</cynic>
solididiot commented on Ask HN: Do you find working on large distributed systems exhausting? · Posted by u/wreath
It definitely can be. I'm constantly trying to push our stack away from anti-patterns and towards patterns that work well, are robust, and reduce cognitive load.
It starts by watching Simple Made Easy by Rich Hickey. And then making every member of your team watch it. Seriously, it is the most important talk in software engineering.
https://www.infoq.com/presentations/Simple-Made-Easy/
Exhausting patterns:
- Mutable shared state
- distributed state
- distributed, mutable, shared state ;)
- opaque state
- nebulosity, soft boundaries
- dynamicism
- deep inheritance, big objects, wide interfaces
- objects/functions which mix IO/state with complex logic
- code than needs creds/secrets/config/state/AWS just to run tests
- CI/CD deploy systems that don't actually tell you if they successfully deployed or not. I've had AWS task deploys that time out but actually worked, and ones that seemingly take, but destabilize the system.
---
Things that help me stay sane(r):
- pure functions
- declarative APIs/datatypes
- "hexagonal architecture" - stateful shell, functional core
- type systems, linting, autoformatting, autocomplete, a good IDE
- code does primarily either IO, state management, or logic, but minimal of the other ops
- push for unit tests over integration/system tests wherever possible
- dependency injection
- ability to run as much of the stack locally (in docker-compose) as possible
- infrastructure-as-code (terraform as much as possible)
- observability, telemetry, tracing, metrics, structured logs
- immutable event streams and reducers (vs mutable tables)
- make sure your team takes time periodically to refactor, design deliberately, and pay down tech debt.
Only read the transcript but I'm not getting most of it. I mean it starts with a bunch of aphorisms we all agree with but when it should be getting more concrete it goes on with statements that are kind of vague.
E.g. what exactly does it mean to: >> Don’t use an object to handle information. That’s not what objects were meant for. We need to create generic constructs that manipulate information. You build them once and reuse them. Objects raise complexity in that area.
What kind of generic constructs?
solididiot commented on Can GPT-3 AI write comedy? robmanuelfuckyeah.substac... · Posted by u/rossvor
How do I know whether this thing isn't already here "commending" in this very thread?
solididiot commented on Competitive Programming with AlphaCode deepmind.com/blog/article... · Posted by u/yigitdemirag
Don't worry, there are a lot of much simpler jobs, like drivers or cashiers that will surrender to AI before coder's job does. So UBI will be implemented long before that happens.
I wouldn't be so sure. Programmers (and drivers and cashiers) can "survive" in poverty like millions others already do. This transformation is coming in waves that keep the proverbial frog in the pan.
I think a lot of people just wanted to put in their hours and get home to their families. I love pool but never played with anyone on the table one floor down because it just wasn't a make-friends environment. I think I shot the shit with someone when I got into work a handful of times in the more-than-a-year that I worked there. Huge reason I left.
This isn't even coming from a social person. I prefer WFH. I don't particularly like going out. However, if I'm gonna be forced to be around people I'd at least like it to be pleasant.