If I’m reading the complaint correctly, the “hack” is what amounts to…prompt injection? Are we seriously considering that a hack these days? Genuine question.
456 karma · joined October 23, 2016
This was a great article overall, though. Well written in addition to the visual aids.
I’m eagerly anticipating the first social media company to take money from every user in order to shut it all down and burn the code.
From the article:
> People commit sunk cost much more easily if someone else is paying, possibly in part because they are trying to still prove themselves right—an understandable and rational choice!
- Start with Flexbox. Flexboxes of flexboxes will solve almost everything that’s common, and be easier to reason through and maintain imo.
- If you’re doing something that appears tabular, use Grid. Flexbox will appear as though it’ll get you there, but the moment you start having cell contents that are highly variable in size your columns will start to get out of sync.
- The above is esp the case if you’re trying to do repeating sets of rows. Eg Row type A, row type B, A, B, etc. That’s a Grid problem.
But of course, the only way to get good mental models is by trying both approaches and seeing what the drawbacks are. Maybe try the Grid games that folks have linked in other comments?
The article linked to one of the author’s other articles which talked about how even if you love it, you start to be fueled by different energy.
> After working at high intensity for more than 90 minutes, we begin to draw on these emergency reserves to keep us going. In the process, we move from parasympathetic to a sympathetic arousal — a physiological state more commonly known as “fight or flight.”
> One consequence of relying on stress hormones for energy is that the prefrontal cortex begins to shut down. We become more reactive and less capable of thinking clearly and reflectively, or seeing the big picture.
I recognize that. Ive also noticed those stress hormones coming more often outside of work and affecting the rest of my life.
Naively, you can implement a component that fetches some data (eg, post) and renders. Some descendants may also need to fetch data and render it. But now you’re blocking the descendants from rendering until the first fetch completes, so you have a waterfall load that takes unnecessarily long.
An alternative has always been to fetch everything at the route/top level. But now it starts to feel a bit strange that your route component needs to know about everything its descendants need.
RSCs promise to allow you implement the former pattern which gives better maintainability without the performance hit of a waterfall since the entire render-fetch-data-render back and forth is done on the backend near your data.
They start out trying to but then time drags on and they “just want it to be done.” At that point the seller is also prioritizing a deal over maximization.
Agents, since they’ve gone through a tonne of these processes, are more immune to the mental load the sale takes on them. I’d bet they’re less likely to try and blow through those final steps.
You can see this kind of thing play out across industries. In SW, a comparison may be the seasoned dev has no problem ripping apart their candidate solution and rewriting it since that process takes them less effort than the junior.
It’s a shame.
I grew up in another country where it was illegal to hold a cellphone while driving and it was actually enforced. I'm just completely dumbfounded at the behaviour here and the lack of enforcement.
(source: crappy guitarist me)
I wonder why there are so many dogs in the street ;-)
There's nowhere where dogs are "natural." They're a species that was bred to the whims and desires of humans, almost always to the detriment of their evolutionary fitness.
I do like the idea that you can use these components as a starting point and drop down to first principles with react-aria hooks if it suits the use case.
But like I said, this is leagues better than the butchery I hear when watching hockey, say. :)
It’s interesting to me because other names like the difficult-to-pronounce Dvořák are kept intact and even attempted quite well by classical fans.
If you’re anything like me, you’ll have this feeling on every new project and new job you start for a while. I’m in my late thirties and am finally starting to realize that “hey, I have this feeling a lot and it’s always wrong.”
Push through it. Write the proposal. I think the proposal-writing process is the very best aspect of GSoC since it forces you into something that you really don’t tend to do in traditional learning like universities. It forces you to think a bit like a product person even and explain benefits and tradeoffs, backing up your beliefs.
There are also still browser quirks etc for some of the newer stuff, and Safari tends to be a laggard, which cuts you off from iOS traffic.
This is the vast majority of homeowners in most countries.
Which also spills into rent costs, of course.
How do you phrase this? What are some successes and failures you've encountered with this approach?
We're a fully-remote SW agency that checks notes builds what's next. I'm a dev, not an HR person so I don't have the full spiel on everything but the main sell to our clients is that we embed with their engineers rather than just building something and throwing it over the wall at them. My team is currently building a React, Next.js, and GraphQL app that lives in our customer's K8s cluster. I've rapidly picked up some knowledge in Kafka and Redis lately as well.
We're trying to fill a couple of roles but we're most urgently trying to pick up some Sr QA folks. We hire quickly and you won't be waiting around forever for an offer. Everest was the fastest from start-to-offer of all the companies I interviewed with a few months ago.
Job Postings: https://apply.workable.com/everestagency/
If you have questions for me before going through the application, I'm at mark@everest.agency