I tried making this joke to the author when the book was released ("I purchased the book, but the link just took me to an empty page") and, unfortunately, they didn't get it and tried to give me customer support
I guess I'm not quite understanding why you need six staging servers provisioned at $500 a pop? And if you need that because you have a large team...what percentage of your engineering spend is $3000 vs $100k+/yr salaries?
Especially when I got look at the site in question (idealist.org) and it seems to be a pretty boring job board product.
RE "neutered inspector": you can inspect the element and click ".cls" to toggle off classes: https://i.imgur.com/ig2SQw3.png
RE "you can't chain selectors": you can stack modifiers like `dark:hover`. The example of having the same styles for hover, active, and focus actually seems Not Great as those are different states that you 99% of the time want to look visually different (Tailwind examples include things like hover:bg-blue-600 active:bg-blue-700 which just seems like a better guardrail)
I got really into daily fantasy at the height of the boom: you make a fantasy football lineup and enter it into paid contests. For big leagues like the NFL you can potentially win millions of dollars (but there are tons and tons of players and lots of 'pros' that do it full-time).
But for the past several years, I have been only playing niche sports: specifically Canadian football (CFL). It's way smaller stakes but the competition is much easier and I've written my own analytics tools so I have a nice edge compared to NFL where there is tons and tons of high quality content and analysis. I've profited over $20k during the past three seasons.
I used OR-Tools via the Python bindings a few years ago. It was nice to work with once I got setup but it was a pain to get it installed (both locally and when deploying to a cloud server).
I would have liked some kind of API that I could call out to instead but nothing existed at the time: you pass in the inputs to construct the linear equations and then you get back the results.
I think the article would be better if you were to include even a basic template instead of just adding the <strong> tag. Right now, my first impression would be "why not just wrap the content in <strong> in JS instead of making a network request on every keystroke?"
The benefit of being able to reuse the server template logic isn't being demonstrate because of the simplicity of the example.
It is great to see more options for non-accredited investors. There are plenty of software-type folks in low-cost of living states that don't meet the net-worth / salary bar but are well off financially and understand the risks.
This is neat. You might consider making a twitter / instagram bot version. I like the Word of the Daily and would be nice to mix that into my twitter feed vs getting an email or viewing the page.
And getting FDA approval is not the finish line. It's just the start of the roll-out. Now employ teams of reps to get the drug covered by every commercial insurance company and all Medicare/Medicaid parties so that patients have access to this life-saving treatment, get policies and authorization forms and billing codes created and implemented. Do outreach to make sure doctors and patients even know that a drug has been approved and how it compares to existing options.
I really hated SmartTVs and would actively avoid them, but I recently got one of the Roku branded TVs and it's actually quite good. Roku has always been great for me in terms of software updates, availability of streaming services, and good-enough UI that everyone in the family can use it.
They are both JS frameworks, but they are fundamentally different approaches.
React (and React-rails) moves rendering / state / logic clientside. You can use tools like react-rails to more easily pass data from your Rails controller to your react components (basically conveniences to create props from instance variables).
Stimulus doesn't handle rendering at all. It's intended to be used for small little "sprinkles" of JavaScript (think things like: showing / hiding content, toggling classes, basic event handlers). If you used to write jQuery snippets to wire up a click event to run ~5-10 lines of JS, then you might look at Stimulus as a more modern implementation (es6, mutationobserver, etc). Stimulus plays nicely with Turbolinks since it needs existing HTML (servered rendered from normal Rails views) to attach to.
You're basically looking at two diverging paths: do you go down a JS-driven SPA application with React (or some kind of hybrid where you have React do parts of the page) or do you opt for Basecamp's "I cant belive its not a SPA" approach with Turbolinks, server-rendered HTML, and Stimulus for small interactivity.
I've had great success with the Turbolinks + Stimulus approach. There are a couple of common patterns that you'll reach for, namely, lazy loading content (basically a <div> with a URL attribute that you have Stimulus load via AJAX) and really leaning into Rails remote-link / server javascript responses for modals and little page updates.
It's so great to still be super productive and be able to crank out several pages of an app in a few hours vs most of the React / SPA codebases where you might send the whole day on one little component.
