vp8989

8 ms·

31.
by vp8989 5y ago
"And way too many operational issues." I've seen this kind of thing mentioned many times, pretty baffling TBH based on Dynamo's pretty good reputation in industry. Are these mostly to the stateless components of the prod
32.
by vp8989 5y ago
Its shocking to me how people don't get bored of rehashing this same, tired opinion over and over and over again and discussing it with hundreds of comments. There is a blog post like this every other day on the front page of HN and it
33.
by vp8989 5y ago
It's not just the developer experience, in fact that is probably lower on the priority than you would think. The entire business IME struggles to reason about a product, in the details, that is logically 1 product but physically N prod
34.
by vp8989 5y ago
It depends what your career goals are. Repeated execution of non-trivial things in different contexts builds your engineering sense and intuition. Amazon has a quote, "there is no compression algorithm for experience". People who
35.
by vp8989 5y ago
I like this framework. Is this only applicable for debugging projects that are already in motion, but going poorly? I was trying to think if it could also be used to shape the discussion and documentation in the planning/design phase.
36.
by vp8989 5y ago
I have been doing this for about 3 or 4 years too. I wouldn't say it necessarily makes you "productive" unless you work in a very isolated fashion. By whittling it down to the bare essentials you at least know if you are unpr
37.
by vp8989 5y ago
Would this post be considered marketing? A teaser? Whatever it is, I strangely enjoyed it a lot. It's a perfect appetizer to get the juices flowing on thinking about the next generation of application software and how databases can ena
38.
by vp8989 5y ago
Nice post, I think "software engineering" is slowly becoming yet another "bullshit job".
39.
by vp8989 5y ago
I "normalize" my previous titles to whatever pattern/scheme my current company uses. It more clearly demonstrates the career progression on your resume and you typically only get a reference check at your previous employer so
40.
by vp8989 5y ago
"I've got so many other things to handle and deal with that being technical except at a high level seems silly." Like what?
41.
by vp8989 5y ago
You are (conveniently or not) incorrectly assuming that the unit price of provisioned vs on-demand capacity is the same. It's not.
42.
by vp8989 5y ago
The actual observed problem in the article is that the team's SDLC pipeline can't handle the current flow it's being subjected to. Work is getting "blocked" in code review. Devising a coping mechanism for developers
43.
by vp8989 5y ago
"Who here is writing software which runs on Linux, yet needs to be running Windows while they do it?" Backend developers at .NET shops who were issued Windows laptops by their companies.
44.
by vp8989 5y ago
Are you actually likely to have a "high bill" on Lambda but also be "surprised" that all your requests are 30x slower? Presumably anything that can generate a "high bill" also has some reasonable level of on-ca
45.
by vp8989 5y ago
Being replaceable tends to make work less satisfying. All the places I've worked at that followed your advice had the most churn and the least productivity/ROI on engineering $ spent.
46.
by vp8989 5y ago
An "uchi-mata" or "ankle pick" or whatever ... to that person becomes it's own martial art or "game" as people normally think of it. There is incredible breadth to discover once you go 1 level deep into so
47.
by vp8989 5y ago
Follow the volume. Work on things that have lots of users, lots of revenue, lots of transactions etc ... nothing exposes bad engineering more effectively than tens of thousands of requests a second or terabyte size transactional databases.
48.
by vp8989 5y ago
Ye to be clear, I meant even building on top of GKE/EKS it seems like a lot of work configuring things, testing etc ... at least from the outside looking in.
49.
by vp8989 5y ago
"Enter Kubernetes. Now you have a core DevOps/SRE team managing the “platform” (the Kubernetes cluster and various add-ons such as operators) which gives the application developers a high-level interface for operating their applic
50.
by vp8989 5y ago
"Whenever I investigate examples, though, I find the devs have to go through a ton of effort to avoid memory allocations" Yep, also the median dev in a GC'ed language is simply incapable of writing super efficient code in the
51.
Full-stack sum types with TypeScript, Rust and Postgres(vincepergolizzi.com)
4 points by vp8989 5y ago|0 comments
52.
by vp8989 5y ago
It's become very trendy these days to be hyper-pragmatic and dismiss attempts to push forward new big ideas or programming languages as frivolous. "Shut up and give me another 500 lines of PHP, we have (made up) deadlines to meet!
53.
by vp8989 5y ago
Wouldn't you be using 2 threads for at least some of the duration of every instance of that? Seems like it would scale very poorly.
54.
by vp8989 5y ago
Elaborate on what? Rust or the pragmatism stuff?
55.
by vp8989 5y ago
"Turns out that the language is far less important than having really great libraries. I’ll re-evaluate rust when things like resilience4j and micrometer exist for it." I agree. Ecosystem shapes how good a given language is right
56.
by vp8989 5y ago
Agreed. Some new languages actually have the inherent capacity to be much more boring than incumbents, once the requisite work has been done to flesh out their ecosystems and make them familiar to people.
57.
by vp8989 5y ago
I used to think this until I really took the time to dig into Rust. Rust has completely snapped me out of this depressing, "pragmatist" learned helplessness that people seem so keen to try to cram down everyone's throats thes
58.
by vp8989 5y ago
Yeh I should have mentioned MySqlConnector as another example of a high quality .NET library, my apologies. We ripped out the Oracle MySQL library at work and put MySqlConnector in. The high quality documentation made it really easy to unde
59.
by vp8989 5y ago
The Confluent.Kafka one, the AWS .NET SDK (though this is improving), the old MySQL one was really bad. My impression from reading the code and GitHub issues is that they're not maintained by real ".NET people" who are plugge
60.
by vp8989 5y ago
Making JIT 4% (or whatever) faster is cool but it would probably have higher ROI for the .NET ecosystem if Microsoft assigned some of these high caliber people to instead work on improving or simply rewriting some of the atrocious open sour

More ›