The original[1][2] articles are a better read IMO. The link is just a summary of the two with added spelling and grammatical errors that materially impact the meaning.
Seems to happen with all our blog posts that appear on here (I work at Uber) - I don't get why the originals don't get upvoted but these rehashes do - are our titles just not as good?
Yes, that’s definitely the main reason. It’s called “burying the lede”.
Saving $6M is key information that makes this story interesting. It’s buried all the way at the bottom of the first blog and is completely missing from the second blog which focuses specifically on the migration
I'm usually guilty of this. The hands-on person involved in a highly technical project gets excited and bogged down in the details of the project that they end up not being the most compelling storyteller about it.
Personally, yes, the rehash's title is stronger. It tells a story whose ending piques your curiosity to read more.
"Uber Migrates" (beginning: company that I'm interested in does something) "1T records" (middle: that's a lot of records; I wonder what happened) "from DynamoDB to LedgerStore" (hmm, how do they compare?) "to Save $6M Annually" (end: that's a good chunk of change for me, but was it worth it to Uber? Why did it save that amount? Let me read more)
It's a simple and engaging "there and back again" story that paves the way for a sequel.
Versus:
"How LedgerStore Supports Trillions of Indexes at Uber" (ah, okay, a technology supports trillions of indexes. Moving on to the next article in my feed)
"Migrating a Trillion Entries of Uber’s Ledger Data from DynamoDB to LedgerStore" (ah, a big migration. I'm not sure who did it or whether anything interesting came of it, or even whether it happened or is just theoretical because of the gerund, and moving one trillion of something is cool but not something I probably need to read about right now, so let's move on)
YMMV. Some probably prefer the more abstract/less narrative titles, but the first one is more of an attention grabber for me.
Other than the comments about titles, the entire blogpost doesn't show for me with ublock. So I'll open it, see a picture of some birds, scroll around for a bit then give up.
Nothing custom, so it must be on a list somewhere.
edit - it doesn't have to really be blocking the actual post here even, if their loading code breaks when some other tracking code doesn't run, that could explain it.
My point is that a random dev running a pretty plain adblock (aren't we all?) simply cannot view their post. This is down to uber, their practices, an external developer and how uber create their blog (they don't just have the content in the page). If I'm not a special case with extremely weird luck, a bunch of devs seeing links to their posts will open them and not see any actual content. They will then, I assume, be less likely to upvote them.
Given that they are seeing problems with posts being upvoted this seems somewhat relevant.
I have no issues reading their blog with uBlock Origin.
You are running software that is blocking content you want to read. That is my point.
If I put on blinders and then complain I can't see your stuff, that's my fault not yours - regardless if your stuff is good or the worst annoying spam ever. If I want to see it for some reason, maybe I should take off the blinders
> You are running software that is blocking content you want to read. That is my point.
Yes. It's my point too. I am running very standard software for a dev and it is stopping their dev blog posts being visible.
> If I put on blinders and then complain
I'm not complaining. I'm explaining, given the evidence I have, why they may be seeing poor results on HN. If I'm not alone (and since I have no custom setup designed to keep our their blog posts that would be a surprise) then there are other developers who cannot see their posts.
Ad Blocking is recommended by USA government agency for security reasons, not running an ad blocker is a dangerous and suggest lack of information/education about IT stuff.
>but if legit content gets blocked you only have yourself to blame.
If the bug is on the devs then the devs are to blame, for maybe expecting teh ads are loaded, or the tracking third party code.
The project I am working on works with ad blocker on. Also we had issues with users that had a spellchecking extension active, it would create a ton of hidden markup on a contenteditable element, and we made code to handle the issue instead of having many tickets to our support complaining and we telling them that is their fault for using a popular extension.
And if someone with a js heavy blog asked why it wasn't getting traction on a lynx centered forum they'd probably be told that their content wasn't readable for a portion of the users.
Just put all your articles into a customGPT with the examples from the rehashes for each one and then ask the GPT to rewrite your title to the a “rehash” like title for the new posts ;)
Lol I was not being on topic or constructive - just repeating the meme that rust is synonymous with "blazing fast", because of endless statements to the effect of "rust is blazing fast," or "if you want blazing fast code, use rust," or the endless blazing fast rust libraries:
Can weigh in here, we use pgtyped heavily at work and it’s really good. There are some constraints with the type inference on complex queries, but it’s a decent trade off IMO.
Do you have a bit more information regarding said limitation?
I'm guessing that dynamic queries would of course not be suitable but any other edge cases you have encountered?
I have, and I would recommend it, if it generated a Postgre schema from a GraphQL schema and not the other way around.
The advantages of GraphQL are its integration of backend and frontend workflows, and that won’t happen with PostGraphile: a frontend needing a schema change needs to go through the backend instead of the backend extending to meet the frontend in the middle.
Mate, if you haven’t already, go talk with a therapist. I’ve struggled with avoidance my entire adult life – avoiding awkwardness, pain, risk, “bad”emotions, difficult conversations, conflict – and talking with a professional has really helped me.
Much like making new friends past university, therapists are a crapshoot. Some simply aren't a good fit or have poor sofa-side manner or fail to develop a sense of trust.
If the therapy is part of an employer funded benefit, you also only get a limited number of sessions, and only with the employer-approved provider.
Interesting. Though I've got very little interest in Lacan's work itself, I could see this being a pretty good filter for finding smart/disciplined therapists who are able to address more... abstract concerns (then again, maybe it's better for some of us to be forced out of abstract territory for therapy).
Also, your employer funded therapist will likely have a specific mandate to basically help you get back to work, meaning no longterm solutions or help, only bandaids.
Maybe I'm lucky, I work for $LARGE_CORP_WITH_GOOD_BENEFITS and Aetna covers a non-tiny number of independent mental health practices with a small copay per session. Are there many companies with therapists on the payroll? I can't imagine feeling comfortable in that setting.
Any tips on what type of therapist (psychologist, therapist, counsellor, etc.) and/or treatment you found effective? Sounds like talk therapy -- but did you go through other stuff as well?
Talk to a licensed therapist with a PhD or PsyD that specializes in cognitive behavioral therapy (CBT). There are masters level therapist, however most of them don't have as much training as people with PhD's or PsyD's (it can be hit or miss with masters level clinicians). But really it's about finding someone that you can connect with.
CBT focuses on challenging behavior that goes against your goals and building an arsenal of cognitive tools to maintain behavior that helps you achieve your goals.
It's what most people with these kinds of problems need.
Yes, quite a lot I would imagine. I use it extensively at work and similarly sql heavy software companies in the past. That being said, I’ve also worked at places where they’ve avoided it like the plague – largely because few people were competent at it – and were moving away from relational DBs due to scale.
