HNHacker News
TopNewBestAskShowJobs

vp8989

754 karma · joined January 4, 2019

submissionscomments
vp8989··on Ask HN: Is Google still a cool place to work?
"A good number of these teams also consist of engineers who have hit a certain level of growth equilibrium which prevents other junior and newer engineers from growing beyond a certain level."

Unsure what you mean here. Do you mean because teams can only have so many heads at certain levels, the people who are holding those seats block others from getting promoted?

vp8989··on Edge Computing
For #2, how would you deal with the user moving to a different region?
vp8989··on How to create a 1M record table with a single query
This is how I do it. You can cross join the derived table to itself if you need more rows.

Much more performant and naturally relational way of generating data than looping recursively.

vp8989··on A new moralism is gripping the literary world
How is it done then?
vp8989··on How to deal with difficult people on software projects
Hah, that is definitely a category. The person who always creates a "follow up ticket" but never, ever does any of them.
vp8989··on Ask HN: When should the dev team get involved in the hiring process?
This sounds interesting. It feels like you would have to have a super smooth on ramp to productivity, otherwise you are getting terrible signal from the try outs.

Ie. you don't want to hire dev A because it took them just 2 weeks to figure out how to deploy a change to Prod instead of 4.

vp8989··on Ask HN: I'm a non-technical CEO of 20M startup that wants to learn
"That problem is better solved by eliminating the silos and aligning incentives rather than gaining technical knowledge, in my opinion."

How do you actually do that though?

Employees typically have incentive to perform their own function to the best of their abilities. This manifests as things like compliance theatre, excessive/impractical IT policies, over-engineering the software, features/products built for the sake of it.

vp8989··on Best practices can slow your application down
Fair enough, thanks for the correction. I guess the tone of the post doesn't convey that they know what they are doing to some people, although it should be obvious that they didn't just sleepwalk into having one of the highest "power to weight" ratio web apps on the Internet.
vp8989··on Best practices can slow your application down
I think the industry should re-evaluate whether unit testing ought to still be the dominant testing paradigm. With Docker and things like WireMock I can fake/mock anything downstream of me in a fast, isolated and deterministic way. Both locally and in CI.

There is so much accidental complexity cruft and ceremony involved with the writing of unit tests and making things unit testable. In a lot of cases, the "coverage" is an illusion and the tests add more friction than there really ought to be.

vp8989··on Best practices can slow your application down
It's candy for beginner/intermediates who want to sound like they know what they are talking about.
vp8989··on Best practices can slow your application down
It's hilarious that you are skeptical of the competence of the SO core devs. You should do a little further reading, there is lots of content available online from the core devs who actually "do the work" there (ie, not the people who wrote this fluffy blog post).
vp8989··on The Two Classes of Software Engineer
Systems Software vs. Application Development is a more appropriate categorization.

There's a tier that sits in the middle who write "platform" software on top of "systems" but for "applications", but you could argue that those people are much closer to app devs than system software devs so they may as well be lumped in with them.

There is simply less supply of systems jobs and they have a higher talent requirement, so it's pretty rational for people to be content to stay at the application dev layer.

Where is the evidence that systems devs get paid more? My impression is that lots of systems development historically has been unpaid or paid via open source foundations. And the route to getting paid doing that kind of work seems a lot more bumpy and less straight forward, almost like a "starving artist" kind of life story.

Whereas app dev is pretty simple. You go to college, you crank on LeetCode for a couple of weeks and then you get a 6 figure salary working on JIRA tickets. It's a brainless, hard to get wrong life script.

vp8989··on We Expect 300k Fewer Births Than Usual This Year in the US
"where it just sat there doing a whole bunch of nothing to consumer prices and wages."

Your primary residence should be thought of as a consumption item, whether you rent or own. If homes cost more to buy or rent since the QE (and they do) then we absolutely have had consumer price inflation.

vp8989··on Speed Is the Killer Feature
Maybe it's because I am not in "the Valley", but this line of thinking makes absolutely no sense to me. You are speaking in generalities, so you are essentially implying that most people are working on software that has not achieved product market fit?

How could the majority of people collect a salary working on software that has no users? That makes no sense.

vp8989··on Google admits Kubernetes container tech is too complex
Yeh this list is not surprising and none of these things you mentioned exclusively require Kubernetes or running containers in Prod. Like I mentioned in another comment, it feels like the purpose of Kubernetes is that it's "brand" provides political cover to introduce these practices to the engineering org.
vp8989··on Google admits Kubernetes container tech is too complex
Maybe. I don't buy that just because people are on Kubernetes they won't still kludge it up with custom in-house scripts or "extensions". Give it time.
vp8989··on Google admits Kubernetes container tech is too complex
"I have some colleagues that are delaying our rollout unintentionally so they can play around with developing more tooling for deployments which is really frustrating."

My impression is that the primary purpose of Kubernetes is to give SRE teams political air cover to rewrite a lot of their existing processes. Whether Kubernetes is actually required for that, or even net superior seems questionable. This unsexy work becomes justifiable because it's coupled to a mainstream accepted tech modernization.

You see this same phenomenon with database migrations. Where what the team really needed to do is just rewrite an app to use the existing database properly. But no one is going to approve that work. So what happens is people convince themselves that the existing tech sucks and use that to rationalize doing the rewrite. The result ends up not always being net superior, because sure you did the rewrite but you are also eating the operational cost of integrating a new technology into the org.

vp8989··on Google admits Kubernetes container tech is too complex
"Kubernetes is the biggest quality-of-life improvement I've experienced in my career."

Can you elaborate? What exactly about Kubernetes improved the developers life?

vp8989··on Tesla has made $1B profit on its Bitcoin investment
"but he could easily put together a plan for selling his share over the next few years, especially now he is no longer CEO"

That doesn't sound very liquid to me.

vp8989··on Choose Boring Technology (2015)
"The very best developers are capable, and avoid complexity. The next best developers are capable, and love complexity. The worst developers are not capable."

It's not always in one's control to avoid complexity. The simplest solution to a problem in a lot of cases may be 2-3x the lift (simplicity tends to require more work, complexity is easy) and thus blocked by the business. A holistically simpler solution may be blocked politically because a certain team doesn't want to own some functionality etc ...

I would say the best developers can see complexity coming and have a healthy fear of it, the medium devs don't mind complexity and the worst devs can't get anything done without increasing complexity.

vp8989··on 12 requests per second: A realistic look at Python web frameworks
"Focus on making a product people wanna actually use first. If you're lucky enough to get to scale you can work about optimizing it then."

This seems like a false dichotomy. Avoiding obvious performance mistakes such as the ones you mentioned does not require additional focus that would detract from general building. It just requires that you know what you are doing.

If you are the type of person who makes said mistakes, its unlikely you would ever go back and fix them by "focusing" on performance because the issue is simply that you don't know what you don't know. Likely someone else will come along in future and point out your mistakes to you.

Optimization that actually hinders you from building and requires focus is at the very margins and almost no one is going to those levels in typical "application" code.

vp8989··on “Location-Based Pay” – Who are we to complain?
I said US tech workers are overpaid, not US workers in general. UK tech salaries are a lot closer to other types of office work.
vp8989··on “Location-Based Pay” – Who are we to complain?
The article we are commenting on is written from the context of a high COL based tech worker.
vp8989··on Why SELECT * is bad for SQL performance (2020)
"someone went around applying every micro-optimisation in the book regardless of how nessasary or appropriate it might be"

This feels like a strawman. I have yet to see an instance of this in my 10 years. The much, much, much more common case is people justifying half-assed shoddy work with YAGNI.

vp8989··on Why SELECT * is bad for SQL performance (2020)
"The amount of "bad" is very low to barely measurable in most real-life scenarios (#2)."

When you constantly apply this "only things bigger than X matter" reasoning you still end up with slow, shitty software but you just died by a thousand cuts instead of 1.

vp8989··on “Location-Based Pay” – Who are we to complain?
US tech workers are massively over-payed so it's tough to feel sorry for ourselves. I moved here from Europe and the salaries are completely absurd, especially at the junior level. People are being brought in from college, they can barely tie their shoe laces without someone there to help them and they are given 6 figures. Meanwhile I know people in the UK who are seasoned lead engineers who work hard and literally put entire companies on their backs and they make half the money.
vp8989··on Tesla buys $1.5B in Bitcoin, may accept it as payment in the future
"Yet, historically, when forced to make the choice, governments have almost always chosen continuation of fiscal policy over the gold standard. Many times (e.g., the early 1930s), governments chose the gold standard only for things to get even worse and instead opt for fiscal policy. In the long run, every country has ultimately abandoned the gold standard."

This. There's a lot of very very smart people who are totally lost among the trees on the technicalities of Bitcoin who don't get this 1 simple aspect. It's never happening.

vp8989··on Product Manager vs. Product Marketing Manager vs. Product Owner
It tells you what is happening that is easy enough to track and measure. Most empiricism in the business world is poser empiricism, people want to say they are "data-driven" because that is virtuous in our current culture but when push comes to shove no one wants to invest the time to do it properly.
vp8989··on A recent poll of employees who are working remotely
Ye I totally get what you mean and I have observed this a lot too.

I think for some people though, this might be an acceptable trade off (even temporarily) where they favor being able to WFH and not need to be tethered to train lines / highways for commuting over being "close to the action".

If companies offered this trade off across the board it would be a good way to retain employees over the long term as your life situation changes (kids etc ...) you can kind still find a place at the same company that can accomodate the lifestyle you desire at that point in time.

vp8989··on A recent poll of employees who are working remotely
I think all or nothing is not realistic for most companies unless the CEOs are very progressive and just deeply believe in it.

A decent workaround is to have entirely remote teams and entirely in-office teams. That way people can be on teams where they feel like being remote is not a detriment to their careers (because ALL discussion takes place online) and people who prefer working in-person don't have to force everything onto Slack just to have the remote people feel included.

← PreviousPage 4 of 7Next →