I've handled this (in Clojure) either by passing a context map through the entire stack or binding some context atom at the top and using it lower down the stack. The binding is less obvious at first glance, so I prefer to pass the context, but both make testing quite easy and reduce the need for heavy refactoring.
I've worked with designers like this. They don't understand the product as much as they think and generally don't get the technical landscape they're dealing with. I've had to push back (successfully) and have product+design come to the team with more of a problem statement and less of a shiny Figma. The projects with problem statements tend to have less "Jira churn" where we have minor bug reports for styling or UX at the end of a project.
Finding fun in things you do is different for going to work for fun. When I still worked in an office and commuted, I'd very rarely attend any out-of-work activities. I have my own life and getting home at 10pm so I can have some beers with coworkers after work doesn't fit with my lifestyle.
They are coming out against advertising gambling from countries with lax consumer protection laws. If you play slots on a US-based slot machine, you're free to stream. They previously banned posting links to these sites with affiliate codes, but they can't police the streamer's Discord or other channels where these are shared. Since they don't want viewers using affiliate links and codes for these non-US-based gambling sites, they are low on options here.
These are the dumbest type of comments. People are doing real world work in FP, but because it's not the work you do (or you're not comfortable doing the work you do in FP) you're deluded to thinking that no real work gets done in it.
He's a Fullstack JS developer which is even dumber because he uses React which is basically the defacto JS front end framework.
React is trending heavily away from OOP, it's creators heavily buy into FP, and most of the patterns in react are inspired heavily by FP. Functional components are now the way to go.
ReasonML (a pure FP language) is react as intended and is the northstar of React.
I still have TIS-100 under the Languages skill section of my resume as an Easter Egg. I haven't played many of Zach's recent games, but SpaceChem, Opus Magnum, and TIS-100 were some of the best puzzle games ever made to me.
TIS-100 and Shenzen had that fun little bit of hacking using the docs. Or just fiddling with it and finding that one instruction that had enough of a side effect where it could let you shave off two other instructions. Where you could get that really fun rush of removing 1 cycle from something. It is a skill I do not get to use much anymore as most things are fairly cookie cutter.
As as assembly language enthusiast, TIS-100 is easily my #1 Zachtronics game.
The closet contender would be... CoreWar. Seems like their implementations are rarely updated these days.
Robocode is also cool, but you code in Java instead of assembly, anyway.
