HNHacker News
TopNewBestAskShowJobs

vp8989

754 karma · joined January 4, 2019

submissionscomments
vp8989··on Attention Is My Most Valuable Asset for Productivity as a Software Developer
IME it's very easy to get into a constant state of CNS burnout with deadlifts. It takes a lot of discipline to go into a gym and only deadlift upto like 70-75% of your max. The deadlift frankly is easy and fun, it's really only a challenging lift in the high 90s of intensity. So people who deadlift, probably do it too often and at too high intensities such that it takes away from other stuff.

I think one caveat he doesn't mention, is all the pro athletes choosing cleans over deadlifts also have coaches there who are making sure their form is good.

In that case then yeh, it's a more technical lift and provided you're getting good coaching you're less likely to burn out your CNS on a clean than on a deadlift.

vp8989··on Microservices – architecture nihilism in minimalism's clothes
That seems like a conveniently contrived example.

Why, in this example, would only 1 instance of the monolith go down but all instances of the crucial microservice go down?

vp8989··on How Satya Nadella turned Microsoft around
FB is big ad. To say that MSFT is not big tech is absurd.

They have a widely used desktop operating system, a top-3 public cloud, they make their own laptops and other hardware, they make multiple widely used programming languages, they have one of the most widely used databases, they have a well regarded research division ... the list goes on

The scope of tech that MSFT works on is as big as anyone, and is what they primarily make their money from ... so why wouldn't anyone think it's "big tech"?

vp8989··on My platonic ideal for how engineering hiring should work
"C# programmers that hadn't heard of virtual"

No offense, but that is a very silly thing to consider "foundational" in 2020. The heavy, all encompassing use of inheritance patterns these days is much less prevalent than 10 years ago, even in the C# community.

vp8989··on A Review of the Clover SPAC
This was pretty much my takeaway after having worked in healthcare tech for ~2 years. The real purpose of the business was to make sure doctors got every $ they were "owed" in as efficient a way as possible, but basically every employee would claim that they were "fixing healthcare".
vp8989··on We deleted the production database by accident
"for most people a web server and csv will serve the first thousand customers"

I hear this kind of thought-terminating cliche a lot on here and it makes absolutely no sense.

If # of users is a rough approximate of a company's success and more successful companies tend to hire more engineers ... then actually the majority of engineers would not have the luxury of not needing to think about scalability.

With engineering salaries being what they are, why would you think that "most people" are employed working on systems that only have 1000 users?

vp8989··on Why Everyone Builds Internal Kubernetes Platforms
People who don't write code should not dictate what the dev experience in a company should be. Kludging up some YAML that you run directly in Prod from your laptop is not writing code, Im sorry to say. The problem is that SREs are tasked with solving these problems and they have horrible taste and sensibilities around dev experience because they are not devs.

All these remote dev Kubernetes solutions sound good in theory, but suck royally in practice. Remote debugging just isn't as good and the idea that I have to be online to get any work done is such a step back that it's baffling that anyone could even propose this.

vp8989··on Google pub/sub released an ordering feature
Agreed, also "processing in order" != "consuming from the sink in order". If everything upstream and downstream of the sink doesn't also happen in order then using an ordered sink is pointless.
vp8989··on Google pub/sub released an ordering feature
One way it can be a foot gun is:

To ensure ordering, systems like these have to block consumption on any given partition until it gets an ACK. If publishers of the data don't understand that, they can publish with too coarse a partition key which greatly decreases the amount of concurrent consumption you can have.

Not knocking how these systems work, it's more that people generally don't "read the fine print", especially these days with cloud services.

vp8989··on Red flags I saw while doing technical interviews
Welcome to the Internet.

Hot takes about interviewing are a dime a dozen because it's an easy thing to have an opinion about, and as long as you punch up then your takes will generally be accepted.

What's always missing from these articles is any empathy for the people on the other side.

vp8989··on Ask HN: Should I quit the field of software development?
Why do you think system design knowledge would not be used on the job? New systems are built all the time. Existing systems are extended/refactored all the time.

System design interviews IME are very applicable/productive actually. Especially ones that put you in a non-greenfield scenario.

Getting good at those requires studying topics that actually are relevant to the day to day job. The Kleppmann book referenced above is one of the bibles IMO. A software book that's actually worth the paper it's printed on.

vp8989··on .NET Transactional Document DB and Event Store on PostgreSQL
There is a growing number of ".NET shops" nowadays that are using non-MS open-source infrastructure. You don't hear much about it because the .NET community has always been culturally less exhibitionist than others. So much so that there are still tons of people out there who don't know that .NET runs on Linux, and has done for quite a number of years now.
vp8989··on I thought I would have accomplished a lot more today and also before I was 35
The malaise of the over-educated median person who has not yet come to terms with what they really are.
vp8989··on I Quit My Job. Here’s How I Planned the Start as an Entrepreneur
Welcome to the Internet.
vp8989··on That coworker who never stops refactoring
This article is based on a very commonly used but flawed premise that all product-driven work actually delivers value to the business and that tech-driven work doesn't.

This is only really true in the real world for a subset of brand new startups, where none of the low hanging fruit product ideas have been built yet but the "idea" for the business is very good. Tech-driven work doesn't pay off here because of scale. It's not worth working on perf when your total server bills is in the hundreds or thousands of $. It's not worth working on dev exp when you have < 10 developers. You don't need to refactor yet as it's greenfield code anyway and it's easy enough to glob stuff on to support business ideas ... for now.

If you are working on a sufficiently mature product, there is a fairly high chance that the product-driven feature you are about to spend months on will fail to gain any traction and be totally scrapped. Anyone who has 5+ years experience has probably experienced this multiple times, this happens all the time even at "good companies".

This is because all the obvious low-hanging fruit ideas were already built years ago (which is why the business even has any money to employ YOU as a software engineer).

In more established companies you are less likely to deliver value to users but more likely to deliver value to the business by executing on "tech-driven" initiatives. This is because of scale:

- If you work on perf, cutting 10% of server costs is a big deal when you run thousands of them vs. tens of them - If you work on developer efficiency, improving that for hundreds or thousands of developers is a big deal - If you refactor to support future changes, preventing forced "big bang" rewrites of large established systems you will save the business millions of $ in salary

vp8989··on Docker Releases Plugin for Simplified Deployments into AWS
Microservices is just a pragmatic, reasonable solution to the changing "economics" of software:

- There is a lot more software being built nowadays - There are a lot more engineers working - The average age keeps decreasing to offset rising labor costs - The average skill level keeps decreasing because of increased abstraction and managed solutions (despite more information / history to learn from) - There is more B2C software running in Prod now that is "on the hook" for millions of $ of revenue

So you have more, less skilled people working on things with higher economic value. The "microservices" solution is to limit the mess and destruction they can cause by giving them their own little sandbox to build in.

Provided the "plumbing" is well enough engineered, it nets out to a better outcome than letting hundreds of 23 year old junior engineers loose on a monolith.

vp8989··on I made a simple geolocation service
"using provisioned concurrency"

What's the point of using Lambda if you have to provision capacity for it?

You pay a premium on the compute because it's able to scale down to zero (so in theory, it works out cheaper anyway), but in reality it only works well when you do everything in your power to have it not scale down to zero.

vp8989··on Post-Commit Reviews
This is basically git flow except peer review happens before cutting a release instead of before integrating changes.

Even if I worked with a hall of fame team of developers, I don't want to integrate your crappy first draft that hasn't been peer reviewed or tested into my work. Generally, if you wouldn't deploy it to Prod as-is, I don't want to build on top of it.

When you allow merging of half-done work, it places additional cognitive overhead on each developer they now all have to keep up and be aware of the timeline of each other's changes and are potentially blocked from releasing until all the merged work that isn't yet released is done.

There is also the thinking that "developer velocity" = how fast you can merge stuff into a shared integration branch. This is dated, low-ownership thinking that I wouldn't want any team I am on to take part in.

The developer is not "done" until it's running in Prod. So you want process that makes that as frictionless as possible, while still having all the peer-review goodness.

The best flow I have experienced is dead simple and it's:

feature branch -> create PR -> peer-review/manual testing/business sign off -> merge to mainline -> CI/CD runs tests and deploys to Prod (from mainline)

vp8989··on When your coworker does great work, tell their manager
Positive feedback can be a good way to reinforce behaviors in your team mates that you want to see more of. For example, you wish that people on the team tested their changes thoroughly before opening a PR.

If you mention that, you will be seen as whiny and a complainer. But if you praise someone who does it, well now you're being positive. Both things have the same effect, in that they communicate that you want people to do more of a certain behavior ... but they are perceived differently by others in the group.

It has the same effect the other way. If you generally provide positive feedback for good work and someone does mediocre work. Your lack of feedback is noticed, without you actually sticking your neck out and saying anything negative.

vp8989··on Deep Work and the 30-Hour Method for Learning a New Skill (2018)
The sad thing is that the way the software industry is structured, it creates environments where juniors are doing the deep work and people with more experience are doing shallow logistical work.

We have it totally backwards.

vp8989··on Pulsar vs. Kafka
I don't think the platform or the pricing model were well architected for a 1 producer, many (and growing) consumer use case which is IMO the most compelling use case for a streaming system.

All the "success cases", sample architectures and real in the wild systems I've seen built on top of Kinesis have 1-3 consumers max.

They added the enhanced fan-out to try to get around this but it seems like you have to (over)pay for a ton of provisioned capacity to ensure you get decent latency on a > 5 consumer use case. So much like Lambda, it's only "serverless" or non-provisioned for people who have super low expectations of what system software ought to be capable of. For everyone else, it's just a mediocre expensive provisioned solution.

vp8989··on Pulsar vs. Kafka
AWS should fork Pulsar and put out a v2 streaming product. Kinesis is kind of crappy (IMO) and doesn't seem to be improving much. If you look at the Pulsar architecture and feature set you can tell that it was designed very much with this in mind (something that large scale cloud providers can integrate with their infinitely scalable storage and compute systems).

It's not all hype either, according to this post https://jack-vanlightly.com/blog/2018/10/21/how-to-not-lose-... it seems like a solid piece of tech.

vp8989··on Linus Torvalds: 'I Do No Coding Any More'
All the "code quality" people write shitty systems. You are too zoomed in if you think code quality is really important. It's kind of important, but your system likely has much more important things wrong with it than the "code quality". Things you could actually get fired for, or seriously reprimanded if the winds don't blow in your favor.

Almost all "code quality" discussion in PRs is lightweight value judgements with no rigor or consistency. Just what random bikeshedding objection that person happened to think of, maybe they had a bad night's sleep? Who knows...

Remnants of an era where most software was low stakes and had low number of users. We now have many more "-ilities" we are judged on, that are measurable and that actually matter, so ignore the code quality trolls stuck in 2005.

vp8989··on Go is boring, and that’s fantastic
Can you elaborate, RE: the Go code review?
vp8989··on Ask HN: What are you learning?
>Honestly, you think I don't know about docker? You think I don't know about the cloud? "Infrastructure as code" oooh buzzwords, you're just using a shittier domain specific language to write something that you can also do with Regular code (such as python, no buzzwords needed).

https://en.wikipedia.org/wiki/Dunning%E2%80%93Kruger_effect

vp8989··on PostgreSQL's Imperfections
Each flavor (and version) of Aurora is compatible with a corresponding version of the open source software. For example Aurora MySQL 1.* is compatible with MySQL 5.6

At my current gig we use it in Prod, but we are also able to run our software during development pointing to locally installed open-source versions of MySQL just fine. I imagine it's the same for Postgres.

vp8989··on PostgreSQL's Imperfections
They are 2 distinct skillsets:

#1 - The administration of a database system #2 - Being able to write code that uses said system effectively

If you don't have skillset #2, you are going to design and build bad systems and eventually a DBA will need to bail you out. The trend is that companies are reducing the number of DBAs on the payroll because of things like AWS Aurora, so you had better get skillset #2.

And why wouldn't you want it? It's like knife skills for a chef. You should know your tools inside out.

vp8989··on PostgreSQL's Imperfections
I don't think anyone would bother to port code from C# to Java in 2020, but I agree with your point. Not using a technology to it's fullest in favor of portability is not smart.

I think most things we build on top are sufficiently complex now that even with these self-imposed limits, porting everything over from X to Y is a major undertaking.

vp8989··on Developers don't need ping-pong tables
Because when you don't, at least ~50% will complain that the ticket isn't well specced enough.

For every person who wants autonomy there is another who would rather be on auto-pilot, mindlessly coding up arbitrary ticket JIRA-1234 with a Twitch window open on their 2nd screen.

vp8989··on Why I Switched from Visual Studio Code to JetBrains WebStorm
The world is jam-packed to the brim with posers, in every walk of life.
← PreviousPage 6 of 7Next →