HNHacker News
TopNewBestAskShowJobs

vp8989

754 karma · joined January 4, 2019

submissionscomments
vp8989··on Apply Unix Principles to Write Testable Microservices
Actual solution: Don't have 500 programmers.
vp8989··on Ford CEO says the company 'overestimated' self-driving cars
Yep. Or they shouldn't even need to "see" the lanes. The roads could be enhanced with signal transmitters so that the car is "on rails", in a digital sense.

Of course that would require centralization and working with the government. The government has no incentive to do this because it would just create another problem for them (mass unemployment).

vp8989··on When to Use TypeScript – A Detailed Guide Through Common Scenarios
Also apparently SQL is #good now. But only because all the people who just spent the last 6 years doing Node said so.
vp8989··on When to Use TypeScript – A Detailed Guide Through Common Scenarios
+1, though this is an unpopular opinion.

IMO appreciation for automated test ROI is a great litmus test for a "good programmer".

vp8989··on SQL databases come up with algorithms you’d never have dreamed of (2017) [video]
You could use views. Although personally I dislike adding this layer of obfuscation. Generally devs are very underskilled in SQL (relative to it's importance) and ORMs hiding the SQL IMO is one of the reasons why.

There is great value in having the entire SQL easily visible in your source code. If there is a performance issue with a specific query my app is running, I can very quickly pull it out and into a database IDE and see what's going on using the more detailed tools available (REPL, execution plan/statistics usage analysis etc).

If the query is composed from a bunch of ORM function calls, I have to step through the program to first generate it.

Reducing friction around debugging allows your devs to become more capable in fixing things or making them work better, and SQL is no exception to that.

vp8989··on Errors – Gotta Catch 'Em All
The blog post is proposing exceptions in the context of an MVC style app where the code that throws the exceptions is part of a request pipeline that also has a global exception handler. This handler would be capable of logging and translating the typed exception to some acceptable output to the consumer.

It seems most people arguing against this clearly didn't read the post or they don't understand the context and are giving their opinions on exceptions in general.

The crux of the post is to leverage the fact that your controller code (in typical modern MVC frameworks) doesn't run in a vacuum, to reduce a lot of boilerplate/repetion around error handling.

vp8989··on Being a middle-aged junior
That isn't really how anyone worth impressing judges work experience.

Those kind of resumes where you have like 18 years of work experience in 9 different language, but you were essentially not much more than a junior dev in any one of them, are very unimpressive.

That is the typical career story and that's why a lot of people struggle to find dev jobs when they get older because they weren't managing their career and were just riding the technology churn with all the other 23 year olds.

You should think of your career progression as every couple of years you are making a jump up to either more responsibility, or a more difficult domain, or working on systems with more load etc ...

If you don't make these forward progressions you will be judged harshly as an older person, because it's very difficult for people to NOT think, "well why didn't this person make any progress in their career? They must suck."

The technologies used is a side detail, it's never the "meat" of your work experience.

vp8989··on On Internal Engineering Practices at Amazon
Looking through the rest of the blog, it looks like the author worked at Amazon between 2014 and 2016.
vp8989··on Yes, Python Is Slow, and I Don’t Care
The idea that a certain programming language could be proven to be more productive than another is laughable. There are so many factors involved in that, I can pretty much guarantee you it will never be studied to an acceptable level of rigor.

The author presents some flimsy "study" about coding string processing algorithms with a straight face, and basically loses all credibility. What about lifetime productivity of a codebase? Speed of refactoring, onboarding, testing etc..

Why don't you just be honest and say you don't care Python is slow because you like using it?

Performance doesn't matter? Of course it does. On the frontend, bad performance has been proven by many eCommerce companies to lead to lost business. On backend data pipelines, bad performance kills your flexibility. The longer it takes you to process N, the less times you can do it. The more times you can do it, the more times you can get it wrong.

Also who says that time-to-market is everything? Tech history has shown that product quality/brand marketing win out in the long term. There are tons of forgotten shitty products that were first. Being first is over-rated.

vp8989··on Ask HN: How to get practical experience in developing scalable apps
It's pretty much "paint by number" on AWS.

The problem with focusing on "scalable" is that wallets and budgets don't scale infinitely and hosting isn't free.

Being able to build stuff that is "scalable" is not enough. You need to be efficient which generally involves "scaling down", ie how much of this data can we be drop because it's useless and no one cares about it?

vp8989··on The Planned Obsolescence of Old Coders
It's not toxic, it's dumb.
vp8989··on Google Moves to Address Wage Equity, and Finds It’s Underpaying Many Men
"The key difference here is that in the MLB it's much harder to quantify skills whereas that's not the case with software engineers. If I was part of a team that released a solid piece of software, even if it's from a non-giant software company, I'm not entirely sure why my experience isn't transferable to Google (outside of a different stack)."

I'm sorry but that is completely the opposite.

In MLB and a lot of other sports now, every single play is tracked. Every player has rate and counting stats to measure efficiency and overall production in every category. Anyone in the world can subscribe to the tape library and watch your entire career on loop and analyze every single moment of your professional career.

No one can do anything like that in closed-source software. Infact, that is the big unsolved problem in tech hiring. No one can tell who the good devs are because your "track record", your resume is just not a reliable indicator of your ability.

vp8989··on Ask HN: What made you change your mind about a programming language/paradigm?
Because there is vastly more state in the world than there is code. And frankly, most state is not that important. Just wait until you work with a sufficiently large immutable system, they are an operational nightmare.

You should opt-in to immutability when the state calculations are very complex and very expensive to get wrong.

I do wish mainstream languages had better tools for safe, opt-in immutability. Something like a "Pure" attribute you assign to a function. It can only call other pure functions and the compiler can verify that it has no state changes in it's own code.

vp8989··on Harder programming questions do a worse job of predicting outcomes
A false dichotomy.

Managing complexity is a valuable skill that should also be screened for at interview. At most top companies you are there for at least 4-5 hours so there should be plenty of time to evaluate that skill.

I think whiteboard questions are good, I want to know that this person is capable of writing difficult code if we need them to.

I also think we probably ask too many of them.

I have been on the hiring side and my experience so far has been that almost always the feedback is close to identical across multiple whiteboard questions. The questions are also so abstract that asking multiple to "prevent bias" seems ineffectual. What bias could there be, you either solve the problem or you don't. Bias is more likely to come in on the behavioral interviews. There should be multiple of those for sure.

Generally someone is either a good enough coder or not and they will display that consistently across all the interviews. You will see the same stuff throughout (good or bad variable naming, good or bad communication etc) thus asking > 1 coding question by default is a waste of everyone's time.

vp8989··on Red Hat Satellite to standardize on PostgreSQL backend
"I suspect it’s a personality thing."

I do too. And also probably a lack of experience dealing with outages and remediation of mistakes.

If it's always someone else's problem to clean up your mistakes then you can't appropriately appreciate how valuable it is that a machine can help you make less of them.

vp8989··on Compounding Knowledge
There is also, practically, a massive gulf between:

1) Being vaguely aware that something exists and knowing you can Google for it.

2) Having such a deep, intuitive understanding of said thing that you can actually use knowledge of that thing to solve complex problems.

vp8989··on Ask HN: What are must-know concepts for back end development?
This is the correct answer but no one wants to hear this in 2019.
vp8989··on From relational DB to a single DynamoDB table
Paying in terms of write units adds so much complexity to what would otherwise be dead simple code.

Normally, you just write to a data store until it's done. The faster the disks the less time it takes.

Now, writes can "fail" so you need to wait/retry or put it back on a queue to reprocess when you have write units available (both of those and the associated logging will cost you $ on AWS).

vp8989··on Software Engineering at Google (2017)
How many 10s?

If you are at an appropriate tier company for your skill level/aptitude then you likely will have to work a lot of extra hours to be (and to be seen as) an 80th percentile performer.

You won't know if that time investment gets you anything until the end of the year. You won't even know what the bonus pool will be or if you'll even have the same manager by the end of the year.

All for an extra 10-30k a year (pre-tax)?

Your time is probably better spent building your reputation in the industry and trying to get a higher paying job.

vp8989··on From relational DB to a single DynamoDB table
https://aws.amazon.com/blogs/database/how-amazon-dynamodb-ad...

They initially implemented capacity units to be spread evenly at the partition level and now they have finally implemented it to work at the table level (which is how they sell it and how they talk about it).

Big whoop, you still have to ask daddy if you want to write at more than 80MB/s per account.

vp8989··on From relational DB to a single DynamoDB table
Why would there be throttling? A WCU is 1KB per second.
← PreviousPage 7 of 7