HNHacker News
TopNewBestAskShowJobs

lhorie

9,880 karma · joined September 5, 2008

submissionscomments
lhorie··on Devpod: Remote development environment at Uber
I maintain the web monorepo at Uber, so I think I can give some context.

Monorepos allows us to centralize important dependency upgrades. E.g. fixing log4j vulns is a lot easier when you can patch everything simultaneously. Same for tzdata (2022g gave very little heads up) Auditing for npm supply chain attacks was a lot simpler in monorepo than microrepos. Etc.

Monolithic version control doesn't have to mean monolithic everything.

Our web projects can be deployed independently of each other, and we leverage tool like yarn workspace focus and bazel for granular installs and builds/tests/etc.

It doesn't have to mean monoversions either. We support multiple version of libraries, though we prefer coalescing them as much as possible to facilitate effort centralization. Finding out that your library change will break downstreams before you land the change is a feature.

We had microrepos before and the main problem is that to this day I still get some random team coming to me for help w/ some rediscovered 7 year old repo that doesn't even build anymore cus lockfiles weren't a thing back then.

At a large enough org, you'll inevitably see the full spectrum of team quality, from the really good teams to the one intern/contractor getting thrown into the deep end of some unloved ancient thing. You want a common denominator that lets you do things like patch vulns in unstaffed projects.

I've done fairly large migrations both to and from monorepos. Each has pros and cons. For us and companies like Google, monorepos work well with our organization model. For others it may not.

lhorie··on Mate with only pawns and no promotions
I think you could do it w/ 3 pawns, by having white king on a1, white pawn on a2, then black pawns on a3, b2 and c2.

Two pawns would be possible w/ white king on a1, white pawn on a2, white bishop on b1, and black pawns on b2 and a3.

Unlikely positions in a non-cooperative game though.

lhorie··on When is short tenure a red flag?
I mean, I think "maximizing results" is a bit of a loaded term. The bar at FAANGs and adjacent companies is already very high to begin with; their systems are optimized to prevent bad hires and I'd argue they're quite successful at that. Also worth noting that when you hire at scale, optimizing for finding mythical 10x'ers doesn't scale, almost by definition.

The other thing is that you're assuming a hypothetical candidate w/ only short tenures is someone who is necessarily an ace, vs the original claim that this person is likely a dud. The point I'm making is that in a real concrete scenario w/ lots of numbers to look at, people w/ that sort of resume don't perform well when benchmarked against known high performers. Which then begs the question of whether it is even reasonable to assume that there's any overlap between the extreme job hopper archetype and the "ace" archetype statistically speaking, when comparing to the stats for the cohort of people with "normal" tenures.

I can point to a vast pool of people jumping from one 6 month contract to the next that tend to do abysmally bad in interviews, and I can tell you none of the staff+ or director-type people I know are extreme job hoppers, as anecdotes to support the argument that the overly short tenure strategy doesn't perform as well as average tenures. You'd need to provide a very strong argument for the idea that "short tenures = good heuristic for finding golden needle in a haystack" is a superior strategy for either job seekers or employers, because I just don't see it.

lhorie··on When is short tenure a red flag?
Personally, I'd refrain from throwing around "If I was the manager of the hiring manager" rhetorics when responding to PragmaticPulp; that's someone w/ a lot of hiring experience in big tech.

I'll throw my own two cents as someone who interviewed a couple hundred senior/staff level eng candidates. When a candidate comes around w/ 10+ years of experience, a career filled with one year stints will not pass the bar for L6 level because some of the evaluated requirements (e.g "consistent cross-functional impact") simply cannot be achieved in <12 month stints (and this shows in the interviews)

Something to consider is that tenured big tech interviewers can have hundreds of interviews w/ 10+ YOE candidates under their belts; they've seen high performers and low performers and inflated titles and smooth talkers and everything in between. So when they say someone doesn't pass a bar, it's not just a quick dismissal of a resume (the interviewing process at these companies typically doesn't even allow that); instead there's a lot of interviewing experience behind that statement.

lhorie··on When is short tenure a red flag?
It seems like a pretty common trope for short tenure advocates to talk in terms of me-vs-them. In reality, the world is vast, companies and work arrangements vary a lot and and even if you're shortlisted as having "red flags" by some, others will still take you in.

At least when I see candidates worried about how short stints will look on their resume, this much context suffices to be said.

Where it gets weird is when you see people on r/cscareerquestions or whatever advocating for a series of short tenure stints as a "hack" to get into high pay positions quickly. The problem is that anyone that has success with this strategy is a living example of survivorship bias, and the seemingly "easy-ness" of the strategy gets a lot of mind space among young highly impressionable audiences, when in reality, if you want to be career-growth focused, you typically do need at least some long tenure stints to gain experience w/ longer term responsibilities and relationships. I.e. you don't see director-level people advocating for quick job hopping for a reason.

lhorie··on An Australian startup is “growing” water for California
Isn't that water vapor still going to be in the local environment? Is the argument here that farm plants somehow prevent water from reaching aquifers (at that 100x magnitude) that would otherwise reach them? If so, how?
lhorie··on “Women are wonderful” effect
> Benevolent sexism

I mean, when attending a birthday or christmas party, who buys the presents?

Bias means that judgment about a topic doesn't match reality. But is it really bias (or even more loadedly "sexism") to think that stereotypical women do more likable things if we were to assume that was perhaps actually true?

Imagine, for example, saying that it's "benevonent species-ism" to think that animals are on average more likely to be quadrupedal than humans. That'd be a silly assertion, because we know for a fact that this is true, and because the idea of more legs being better is weird for human standards. This thought exercise then begs the question: if we do think that thinking "women are nicer" is a form of bias, then what is the reality? Is the implication that they are not? That niceness should account for things other than nurturing attributes? According to who?

IMHO, the more interesting aspect of the observation of this effect is what it says about the people talking about it.

lhorie··on Ask HN: Getting tired of complexity in web development
I transitioned from product work to platform/dev productivity work (think frameworks, internal tools) surrounding the web stack, which is a form of extreme specialization. It effectively means I'm not directly dealing w/ useEffect stale closure sort of crap, but instead I work w/ things like supply chain management, CI flakiness and build optimization, which involves developing a skillset that doesn't really fit into the "jack of all trades, master or one" narrative; it's more like developing depth in a wide array of obscure things plus a large dose navigating "working groups" to complement a workforce composed largely of React experts.

Career growth is currently primarily coming from increased internal impact at a large company. In terms of future career growth, most of the recruiter spam I get for Senior/Staff/Principal roles is below my current pay grade, so I expect that further growth will require shifting more and more into director track.

</two-cents>

lhorie··on Staff Engineer Archetypes (2020)
A little meta commentary: I'm seeing a lot of negative takes using the word "they" (so presumably these are from people who either haven't worked in a staff eng capacity, or have, but in dysfunctional organizations).

The intent of this article (as I understand it) was to help people navigate the emerging nebulous role that "staff engineer" was, particularly as it started to become a more mainstream concept a few years ago (whereas prior to it, the dichotomy was largely that senior was "the" terminal IC role and you had to transition to management past that).

Many engineers on the upper side of the senior spectrum have clearly been operating above and beyond what is typically considered senior level, but not in the capacity of a typical manager archetype, so this was meant to help people understand how to identify/categorize these people as well as help people understand what kinds of challenges to look at after you've become a "full-fledged" senior engineer. Resources are useful, whodathunkit.

My advice for those eyeing for a staff+ level would be to avoid making "hot take" categories, everyone can do that and if they're coming from a position of inexperience w/ the subject matter, there's a good chance it's a bad take. Instead, try to derive action items from each of the archetypes, and incorporate those into your work. A good point I heard is that no staff engineer qualifies as a single archetype exclusively; the role is usually a mix of all archetypes, with different people leaning more strongly one way vs another.

It's very easy to make sour comments like "oh staff people just spend all their time in meetings, what good are they for". It's quite another to be that staff engineer and have to balance technical depth acquisition, alignment among disparate groups and the multiplexing required to operate at high levels at both. It's easy to chalk it up to politics, but it's quite another to be able to visualize power structures as tools, and use them as such to accomplish large scale engineering goals. There are classes of engineering challenges that only really arise at the staff+ engineer level, and engaging with them can be rewarding in their own right.

lhorie··on What Makes the Zig Programming Language Unique?
Yes, I meant in your sudoku solver, sorry, I should've been more clear.
lhorie··on What Makes the Zig Programming Language Unique?
Just out of curiosity, in your opinion what's the benefit of using a packed struct and all the generated bit fiddling compared to just a regular struct? Just better memory consumption?
lhorie··on Espresso.js – minimal React alternative – is now a decade old
To play devil's advocate for a bit, what you said applies to jQuery as well. It has an enormous plugin ecosystem. I know, I know, people are going to now start pointing out how X or Y specific thing is "better" in React, but then isn't bundle size, application space code conciseness, etc also W and Z specific things?

At what point is the argument for one toolchain over another simply circular reasoning / backpatting? Trade-off analysis isn't just pointing at X, it's about looking at the balance of X and Y vs W and Z.

lhorie··on Post-pandemic, the battle between Uber and Lyft is looking more one-sided
Basically it's business accounts for doctor offices to arrange transportation for their patients. Many elderly patients have trouble getting to doctor appointments because they don't have smartphones, can't drive, live in areas w/ poor public transit/taxi coverage, etc.
lhorie··on Post-pandemic, the battle between Uber and Lyft is looking more one-sided
Frankly, anybody saying "the only thing Uber has over X is Y" hasn't been paying enough attention.

Uber hasn't been doing scooters for a while. The rentals in the app are through Lime. Stuff like self driving and aviation also got offloaded to Aurora and Joby, respectively.

The third largest vertical for Uber is freight, not scooters. $1.8B in revenue there in Q2.

The rides business now has several arms, from B2B corporate accounts to numerous partnerships with players in adjacent and semi-adjacent industries.

The eats business is branching into general last mile delivery (e.g. cornershop acquisition).

The B2C strategy now is to bundle all the rides/rentals/food/deliveries services into the Uber One membership package, similar to the Amazon Prime/Costco volume-incentivizing model.

Look through the careers site and you see there's an ads arm spinning up.

I'm seeing a very clear change in focus from pie-in-the-sky ideas to more proven business strategies.

lhorie··on Brazilian vote counting (real time)
A few points of interest for those who aren't familiar w/ brazilian politics:

- as the link shows, brazilian political parties are numerous, so general elections typically have multiple candidates. There's no electoral college.

- voting is mandatory in Brazil. In the 2018 presidential elections, there were ~117M voters. By comparison, the last US presidential election saw turnout of 158M voters.

- Brazil has used electronic voting since 1996. General public sentiment towards it has historically always been positive. No instance of fraud has ever been surfaced and the system produces results extremely quickly (as in, within the same day).

- Recently the president has been questioning its security, but for some context on his political platform, he also held a similar stance to Trump on the topic of Covid and has been criticized over his position saying deforestation is good for economy. He's still the favorite candidate. The second most popular candidate (Lula) has a long history of controversy (one of the most high profile being him being implicated in investigations related to the impeachment of the previous president Dilma). As you can imagine, many brazilians are cynical about the country's political system. Take that as you will.

lhorie··on FTC to crack down on companies taking advantage of gig workers
From what I've seen, the majority of arguments against gig work is a combination of information asymmetry (usually that a worker does not know the "true" payout of such work because they haven't accounted for things like depreciation and car maintenance costs) and the idea that you can't "overcharge" for unskilled labor. E.g. one could make the same argument that a general contractor also "does not know the true payout" of their contracts since they also have various difficult-to-calculate cost-of-of-doing-business costs, but the rebuttal is that these costs can be built into the cost of the service.

Something that I think a lot of these discussions fail to account for (and was, incidentally, an underlying theme for California's Prop 22) is that gig companies artificially create a type of market that would otherwise cannibalize itself into a different type of market. If one were to follow the ideals of increasing payouts to [whatever arbitrary point is deemed acceptable], the logical conclusion is that either demand has to increase proportionally to create upward price pressure - and there's no reason to believe the market would simply increase demand just because one wishes for it - or service volume has to decrease (the service becomes less affordable, meaning less demand from price-sensitive customers, which in turn means less drivers on the road, longer wait times, etc).

But once we get into these terms, we run into the classic "I got mine" mentality. Then it's complaints that taxis aren't reliable, or smugness about how one doesn't even use these services in the first place. Well, which is it, does one supposedly "care" or is it really insofar as it doesn't become an inconvenience to themselves? Easier to just blame the companies for everything, right?

The one group that does truly care about the payouts is drivers themselves. From what I see in driver youtube channels, they can in fact become quite savvy about how much they can expect to take home, and come to their own data-based conclusions about whether new features or bonus structures are good or not. Common themes: two [gig companies] are better than one, long term is worse than short term, weekends are better than tuesdays.

And to tie back to supply and demand, gig worker supply base is highly elastic, aggressively more so than any other type of business. Uber's CEO even said inflation helps business because with rising cost of living, more people look to gig work to make a few extra bucks. So, in a way, sure, gig companies promote an environment where more workers can freely come in a take a piece of a pie (which is not infinite). The thing is everyone wants more of it and there's only so much to go around. Is setting up such a system akin to taking advantage of these people? In a way yes because it's playing to their desires to earn more in a world that is largely structured to think payouts should always go up over time, whereas the reality is that they're exposed to these raw supply-and-demand market forces more directly. But also no, because they wouldn't have that opportunity to make extra cash at all otherwise.

lhorie··on When to use Bazel?
> Bazel is much too hard for TypeScript and JavaScript. We don't use Bazel for our frontend. New bundlers like Vite are much faster and have a developer experience that's hard to replicate with Bazel. Aspect.dev is doing some work on this front. One large hurdle is there's not automatic BUILD file dependency updater like Gazelle for Go.

I built this[0] for the Bazel + yarn setup that we use at Uber. We currently manage a 1000+ package monorepo with it.

[0] https://github.com/uber-web/jazelle

lhorie··on When to use Bazel?
I mean, Python (moreso its ecosystem) is notoriously difficult to get working w/ Bazel idiomatically. Bazel is advertised as a language agnostic system (and to be fair, it's better at it than, say, Buck), but in practice it tends to work better w/ stacks that already have some degree of hermeticity (Go, Java), whereas YMMV very much with the more loosey-goosey stacks (Python, JS).

IMHO, Bazel is a classic example of Conway's law[0], and it falls squarely in the "big corp" class of software. You have to be running into issues like 6+ digit CI compute costs or latency SLOs in hundreds-of-teams monorepos before Bazel really starts to make sense as a potential technical solution.

[0] https://en.wikipedia.org/wiki/Conway%27s_law

lhorie··on The Protobuf Language Specification
That sounds great, but what's the governance story? Are the authors of the spec document committing to keeping the document up to date here henceforth? Are the protoc maintainers committing to have these folks involved in project direction decisions?
lhorie··on What makes a senior engineer? Writing software vs. building systems
There are two different career tracks, namely IC (individual contributor) and EM (engineering manager). The latter revolves almost entirely around people management. For the IC track, I've found this writing[0] on staff engineer archetypes useful. The gist is that there are archetypes that involve a lot of people management, but there are also some that are highly technical / coding oriented.

One analogy that comes to mind is wuxia/murim novels (i.e. stories set in ancient times east asia, involving martial arts sects). Among the strongest characters, there's the sect leader type that is involved in politics most of the time, but there's also the recluse master training in the mountains type. Naturally, there's also plenty of characters clinging to titles, overconfident fools, etc.

I think this analogy is interesting because there's a clear parallel between the two worlds in terms of how titles are perceived, the craft that they purport to represent, and their place in the world. Titles can represent both status and mastery, but only loosely at best, the craft can be honed irrespective of both titles and the state of the world, and it's only through increasing a sphere of influence that one can have a sizable impact in the world and its citizens.

[0] https://staffeng.com/guides/staff-archetypes

lhorie··on Ask HN: What happened to vanilla HTML/CSS/JS development?
Disclaimer: I'm the author of one of the frameworks mentioned in this thread.

Yes, HTML/CSS/JS are perfectly fine tools for web development. But just like it's not as efficient to use a hammer as a nail gun, using HTML/CSS/JS alone might not be the best choice if you're trying to build something highly interactive or if you have other concerns (e.g. a very large team that consistently steps on each others' toes on accident).

I'd encourage that you try to actually take HTML/CSS/JS as far as you can take them, if nothing else to experience the pain points of using them at high levels of complexity yourself. This can give you an appreciation for why frameworks do things the way they do. For example, routers are patterns that every framework dealing w/ parameterized pages eventually lands on because it's a pattern that makes it easier to manage page parameterization.

It can be argued that some frameworks land on seemingly strange or overly complicated APIs sometimes, but that's just the realities of engineering. We try to make the best decisions with the known information at the time, and then we have to consider maintenance costs after the fact. Nobody is perfect and sometimes we only see flaws in an approach through hindsight. There's also such a thing as using the wrong tool for the job. Frameworks usually have scope and an idiomatic way of being used. These indicates which use cases the frameworks are strong for, and which aren't.

Most self-respecting frameworks will have some sort of tutorial that you can follow to get a feel for what type of tasks they are trying to optimize for. Try them out to see if that's what you need. If it's not, that's ok, there are plenty of other tools that could fit the bill better. My recommendation would be to try different "categories" of frameworks. For example, React/Vue/Svelte are very similar in scope, so trying one should give you an idea of what all three are more or less all about. You could try htmx, or GWT or even jQuery to experience completely different flavors of "framework-ness", maybe one of those will "click" better. Maybe you'll find that vanilla HTML/CSS/JS is all you need after all, and that's ok too.

lhorie··on Don't ignore the janitor
> I have no illusion that I am not trading my time

I think that's kinda the point of the article. The people that ignore janitors surely are under no illusion that their time is better spent elsewhere than talking to cleaning staff. Rich parents in Dubai surely are under no illusion that it is better to hire full time nannies than to waste their time raising their own kids. The people in Wall-E surely are under no illusion that their time is better spent entertaining themselves than, well, anything.

But as the increasingly absurd examples hopefully illustrate, not everyone thinks the same way. For example, my wife firmly believes that food that is paid for is intrinsically inferior, because, all else being equal, it's not made with the same level of care as if it was made by family (and this in fact can be a particularly noticeable observation if you come from a culture that takes pride in elaborate cuisine)

We all have things that we believe implicitly are a waste of our time, perhaps because of our upbringing or some other reason, but I think the overarching message of the article is that there are some things in life that we should not be compromising on, even if we did have all the money in the world.

lhorie··on Don't ignore the janitor
It's not all that different than going home and doing the cooking or the laundry. Surely you don't leave housework to your partner "because your time would be better spent elsewhere", right?

We don't think of brushing our teeth as "wading into the weeds", it's just an integral part of life for us. Cooking and laundry is (hopefully) just as much an integral part of life. Similarly, the Japanese famously don't have public trash bins everywhere and yet their streets are spotless because they consider public space cleanliness an integral part of life.

And one would hope that saying hi to people is an integral part of life too.

lhorie··on Don't ignore the janitor
In Japanese schools, the kids are the ones doing the cleaning. Not just taking out the trash, but cleaning the blackboards, mopping the floor, tidying up the desks, cleaning the bathrooms, etc.

The reasoning isn't to save money, however. It is precisely to teach them there's no such thing as work that is beneath them.

lhorie··on Making iron from sand [video]
Not quite as pre-historic, but along similar lines, I quite enjoyed Honzuki no Gekokujou (Ancendance of a bookworm), a series about a book-loving girl reborn as a sickly poor commoner child in a fantasy world and her attempts to create books (and other modern products) from scratch.
lhorie··on JavaScript hydration is a workaround, not a solution
One story that comes to mind was when I was still relatively early in my career and the COO of the company came to me asking for some help getting some jquery ui tab widget thingie to work.

And as if the words "COO" and "jquery ui" in the same sentence weren't enough to raise eyebrows, what came next was probably one of the most mind bending software engineering episodes I'd ever witness. It turned out he was trying to put together a web UI for displaying a number of reports from some computationally intensive data warehouse query crunching. We're talking visualization of tables and tables full of data. Conventional wisdom would dictate that implementing this the traditional way would involve query optimizations, various layers of caching, separation of concerns, a framework to manage all the complexity, etc, etc, etc. His approach? Just do the naive queries (slow as they were), print directly to HTML old school PHP style, then save the HTML file to disk.

He was a bubbly happy type of guy and you could see the child-like joy on his face when he showed me how lightning fast the thing would load from navigating from one page to another because it was effectively looking at a static website once the pages had been generated once. I distinctly recall feeling a mix of confused feelings at seeing the guy break every rule in the "programming best practices" book and the undeniably good performance results from the sheer dumb simplicity of the solution.

lhorie··on Want quick answers? Ask questions well
> Another theory: that for some people, hitting a problem is an excuse to stop working entirely

What I do in these cases is link back to the docs in question format, e.g. "have you tried [link to relevant docs page]". Puts the ball back on their court and kinda puts them on the spot for not doing due diligence without coming off too passive aggressive.

On occasion, I had to also explicitly spell out "please include error messages, expected and actual behaviors, repro steps, what have you tried, etc" as a response to a question in slack chat. Some people just lack self-awareness.

lhorie··on Pakistan's floods have created 100km-wide inland lake, satellite images
I was trying to figure out a relatable comparison on a map. Looking from one side of the flood lake to the other would be like trying to spot Niagara Falls from Toronto, or San Jose from San Francisco - never mind that the distance is large enough for Earth's curvature to get in the way. And that's just thinking of it as a cross-sectional view of the lake, which doesn't say much about area.

The way I ended up explaining it to my kids was that 33M people were affected. San Francisco population is ~800k, so around 40 SFs worth of people are impacted.

lhorie··on 'Too many employees, but few work': Pichai, Zuckerberg sound the alarm
People will always make up reasons if the tone of the conversation feels adversarial, but just spend a week in r/cscareerquestions to see the unfiltered sentiment: lots of people literally bragging about working 30 or even 20 hours per week as a full time employee, or who explicitly call out "slacking off" as a reason for preferring WFH. "Rest and vest". Etc.
lhorie··on To speak meaningfully about art
But that sentence isn't arguing for the notion of some "absolute good art". If I had to criticize it, it would be to say it doesn't go far enough by still accepting the concept of good vs bad art, whereas I think interesting discussions are multidimensional.

For example, why do you defend archeological architecture? Are the pyramids "good" because they are opulent? That sounds like a sensible stance at a glance, but then what of the Burj Khalifa?

Is Calvin and Hobbes not acclaimed? Is it not art? What of obscure manga about gender identity?

Why is Turning Red controversial? Who is it relatable to, and does that matter?

Suddenly equating one's opinion w/ "good vs bad" seems superficial. There's historical context, there's political commentary, and commentary on the commentary, and how that shapes the rest of the contemporary works.

← PreviousPage 3 of 34Next →