Would be the best antidote to this sort of thing, but is probably untenable to amend at this point.
3,134 karma · joined April 15, 2011
Would be the best antidote to this sort of thing, but is probably untenable to amend at this point.
That it was trivial to tell which was which is an understatement. There's a floral sweetness to saffron that is absolutely unmistakable to me.
Not sure the percentages of each, but those categories probably about cover it.
Not quite Fortune 500 tier, but certainly not small potatoes.
Also, I've never noticed "black veins" in any peppers I've prepared, including very spicy ones.
(I've worked (and interviewed) as a programmer at VC backed startups and FAANG in SF and NYC over the past 12 years)
Progressives believe that allowing developers to build housing will only create "luxury" housing that is unaffordable to all but the rich, increasing gentrification and displacement. Therefore it's necessary to mandate things like "inclusionary zoning" and tight review of every single development project.
Empirically, the progressive stance results in a lot less housing of any sort getting built, whether "affordable" or otherwise, and consequently higher housing prices for all but the lucky lottery winners who grab the limited number of BMR ("Below Market Rent") units. Some would say that that's actually the goal of progressives (ie, they're using "progressive" window dressing to preserve property values/neighborhood aesthetics of the very rich).
Which of us is right? Maybe both (corporate culture can be pretty heterogeneous). Hard to say, regardless
dot = (sum.) . zipWith (\*)
p = [2, 3, 4]
q = [1, 0, 2]
p `dot` q
Like, the only difference to my eyes is using names for sum/zipWith, and not having the lifts/restructuring happen "magically"1. I'm very uncoordinated, with a noticeable intentional tremor
2. I'm particularly bad at sequencing dependencies for projects/errands/household tasks. I have to write down even fairly simple sequences of subtasks or get lost in yak-shaving loops
3. When flustered, I make very distinctive disfluencies in speech around conjugations (swapping "but"/"and"/"although") and sequencing (ie, placing objects before subjects/verbs) in sentences as well swapping relationships (referring to someone's parent as their child or vice versa, swapping "you" and "I/me", etc)
4. I tend to have a "ground up" approach to writing (building clauses first and then moving them around to construct sentences), which doesn't resemble the approach of other people I've shoulder-surfed.
All of these are fairly mild in terms of life impact, to be clear (or perhaps I'm just able to satisfactorily compensate for them in various ways) but I wonder if they all share some underlying minor cerebellar dysfunction.
(Over ~4 Cruise rides, I’d put them closer to median)
It's also possible for supply of housing to reduce simultaneously. Say if there was a change in rental laws that strongly incentivized landlords to pull units from the market?[0]
[0] https://reason.com/2019/06/17/new-yorks-progressive-backed-r...
There is no universal metric of what makes one accent easier to understand than another.
That's what inflation adjustment is for.
> The poorest people in the US saw faster inflation-adjusted wage growth than any other income bracket: https://www.epi.org/publication/swa-wages-2022/
As a percent of population, number of Americans with multiple jobs is well south of where it was from 1994-2009.
The same C++ or Java or Haskell code run with the same inputs twice, will cause the same result[0]. This repeatability is the magic that enables us to build the towering abstractions that are modern software.
And to a certain mind (eg, mine), that's one of the deepest joys of programming. The fact that you can construct an unimaginably complex system by building up layer by layer these deterministic blocks. Being able to truly understand a system up to abstraction boundaries far sharper than anything in the world of atoms.
LLMs based "programming" threatens to remove this determinism and, sadly for people like me, devalue the skill of being able to understand and construct such systems.
[0]Yes, there are exceptions (issues around concurrency, latency, memory usage), but as a profession we struggle mightily to tame these exceptions back to being deterministic because there's so much value in it.
The incidence question (is the fee "paid" by the buyer or seller) is a semantic one, but if the cartel is able to inflate the total fees, that's something else entirely.
150 - 275 k$ definitely does not encompass 75% of software jobs in the USA
I've worked in Monetization at 3 SaaS cos (admittedly all smaller than Uber, O(100-1000) employees), and at all of them I've seen mistakes of a similar proportion of revenue (~1%) made in both directions (overcharging and undercharging customers) in violation of the letter of our contracts with absolutely zero intent or malice.
Wage law adds several additional layers of complexity beyond that.