5,885 karma · joined February 24, 2012
Checkout my book! https://www.manning.com/books/data-oriented-programming-in-java
chriskiehl.com
Haskell != Category Theory. You don't have to know what an Endofunctor is in order to write useful programs. Haskell is just another programming language. It's totally possible to do cool stuff in it without knowing any of the theories that back a lot of the "why" behind its common abstractions.
Pick up any book and just start building toy programs! Don't over think it. Start very small. Make a CLI tool. Scrape some data off the internet. Even simple haskell programs will cause you to bump into all kinds of concepts at the time you need to learn them.
Just working through a book can make Haskell seem painfully esoteric. Monad transformers broke my brain when I tried to learn them simply because I reached the monad transformer chapter. However, I finally "got" them once I was actually building something, because their existence is something you naturally start to bump into the more you program. There's a friction that comes from no having them, but noticing that "friction" and letting it guide you can only happen over time as you use the language.
Google didn't reject the candidate, the interview loop he got rejected him for any of the myriad of knee-jerk split-second decisions made on the candidate's character in an unnatural and stressful environment.
I've been in hundreds of interview loops at $Megacorp. You can stack the deck with preparation, but sometimes you just hit a loop that doesn't click with you.
There's some stuff that felt dated even for its time. For instance, GUI programming with AWT / Swing. It's super disappointing to spin up a GUI and have it look... well, like Java GUIs do. As a student, it can be a bit demoralizing to spend a bunch of time and effort only to end up with something that looks so stupid and unfinished.
On the whole, though. Great book.
What does that look like in your mind?
Fighting with the AI's wrongness out of spike is an unexpectedly good motivator.
The amount of rope it gave to hang yourself. Hooks were the harbinger of the sad state that what was to come.
The OG React was a breath of fresh air because it introduced the world to immutable data flow. The component model was dead simple. You had a fat (for better or worse) class that served as a management point for your side-effects and IO, then a bunch of stateless transformation functions / components.
The old class + lifecycle methods imposed a much needed friction on the development process. Their clunkiness was a feature (imo). It raised the cost of creating stateful components / performing side-effects wherever you wanted.
Then hooks showed up. In a lot of ways, it feels like React is now rediscovering the bad parts of OOP: uncontrolled mutation and side-effects. "Immutable data flow" means very little when everything is launching side-effects, updating some global store, modifying 12 layers of caches, writing to local storage, etc. etc. etc. etc.
It became a complete nightmare to reason about what an application was actually doing. Most of my experience with React (at least as of a year ago) was debugging performance issues, or UI quirks from component A clobbering updates from component B, because some special GraphQL caching magic modifies some global cache somewhere in some provider, which is 37 layers removed from the code you're actually looking at.
I've also seen the northern lights with my own eyes. Way up in the arctic circle in Sweden. Their color changes along with activity. Grey looking sometimes? Sure. But also colors that are so vivid that it feels like it envelopes your body.
This is why I think design docs need to be lightweight and reviewed early. Design docs shouldn't be a masterpiece perfected in isolation over the course of days or weeks. That guarantees the author has calcified their opinions. When I was on review panels at Amazon, 99% of them were an exercise in futility -- the author had already poured concrete. It is very, very, very hard to avoid the mental trap of "Hrmph! I've thought about this more deeply than anyone else" that comes from living down in the isolated world of "doing design."
The earlier you get other eyes involved, the more likely people will actually listen to feedback and consider alternatives. You still, of course, need that heads down time to put in all the details, but the overall shape of the design shouldn't be a big reveal when you hit the design review.
You're making OP's main point. He's arguing that (to use his numbers) 90-95% of startups don't actually need to worry about that. Hell, I would argue that a lot of services at established companies don't actually need to worry about it (and the ones that do, need to worry about it a lot). Tons of stuff inside of $megacorps is running on crummy "non-scalable" architectures because somebody sat down and did the "engineering" part of "software engineering" and went "y'know, I think all we're really ever need is..."
>Cloud is still better for early stage startups
My preference is cloud these days (especially if I'm just quick and dirty clicking buttons in console rather than CDK-ing things together). However, there are still lots of cases where sinning up a $10 droplet and running `docker compose` completely satisfies "the architecture" part of the business.
For the most part, once you've got your kart dialed it. It is still "pick your character and go". It's one of my goto games for "I want to do something for a few minutes to unwind" (which usually ends up with me more frustrated and on edge than unwound haha).
Nobody likes a poo-pooer, but, holy moly, I thought it was unbelievable trash. Are her other books better? This one was "noble savages: the book". The Creechies can't even conceive of inter-species murder until Big Bad Comic Book Evil Guy (who just loves being evil) introduces it. The creechies don't know evil. They settle their disputes as all superior noble people would: through art.
I probably just got in my own way while reading. There was a lot of "wait.. they're sending _wood_ through interstellar space?". They have an ecology that can support a supply chain that produces food in excess to perform 40+ year round trips through space, but... they can't grow a tree? A tomato plant? Sure. A tree? Nah.
It might be a good kids book, if not for all the... raping.
I'm fine with "screen says X and drink is Y". That's sort've the most I'm after when I go to get a coffee.
For some humans, they don't have to be "made" to do it. They love squabbling over style issues and rearranging deck chairs. I will never, ever understand caring about style issues, so auto-formatters are a gift from the heavens. Now the guy that used to waste time in code review can waste time tweaking the formatter rules, and everyone else can move on with their life.
Anything other than open propaganda seems to be offensive to the government. I've got no clue what they're saying on TikTok about him, but kids understanding that there's some nuance and understandable motivation behind a guy like bin Laden seems like... not something to be terribly alarmed about? Of course, goes without saying, bad dude. However, there's a big difference between cartoon character who "hates freedom" and "guy who is pissed off about (among other things) the effect of US foreign policy on his country." One breeds "turn 'em to glass" sentiments, another breeds "what IS our foreign policy?"
I sat through a two day (all day) "retreat" (conference room in our regular office) where people tripped over themselves to present their teams innovative AI ideas to leadership.
"It's a chat bot that..." "It's a chat bot that..." "It's a chat bot that..."
How are statements about reality fat shaming?
The things you linked are completely irrelevant. First link: The calorie counts of food are wrong? Sure. Absolutely. No shock there. Treat them as rough estimates.
Second link: different people are different? Whoa. Wow. Oh man, mind blown.
What you naively describe as "not true", the universe itself would describe as bedrock reality.
Despite the bad scientism (i.e. coping) everyone hides behind, nothing changes the fact that if you burn more calories than you consume, you'll loose weight.
If you aren't loosing weight AND counting all of your calories, guess what: you've counted wrong. Dial them back more. Keep dialing back until results are achieved. The gym bros have truly found This One Weird Trick that works 100% of the time.
The big pay off in formal methods is learning to think abstractly (imho). Even if you don't make a full blown model, sketching out the problem in something like TLA+ can be extremely valuable just by forcing you to think about the modeling independently of code. Even in the world of general software engineering, being able to reframe requirements as temporal invariants has felt something like a super power.
What are your thoughts on Rick and Morty?