HNHacker News
TopNewBestAskShowJobs

dimino

382 karma · joined May 14, 2015

Software Engineer

diminoten@gmail.com

submissionscomments
dimino··on Turning PostgreSQL into a queue serving 10k jobs per second (2013)
It only adds the burden to DevOps who can't figure out how to monitor/maintain a system, which is not rocket science, and if you're a DevOps person who doesn't know how to handle such a mainstream technology as, say, ZeroMQ or RabbitMQ or even Redis, then maybe you shouldn't be in the position you're in.

The only argument that doesn't hold up is "use one tool for everything". This ideology is for lazy people who want to anchor themselves in a period of time, and refuse to learn new things.

dimino··on A Pragmatic Approach to Thorny People Problems
> If one person’s presence is derailing the conversation for some reason, don’t automatically decide they must be the bad guy. The absolute worst thing you can do is to tell that person to shut up and leave the discussion while allowing other people to keep attacking them in some way. This includes everyone rebutting their comments that they are no longer allowed to defend because they were asked to stop posting.

> It is healthier to allow them to vigorously defend their point of view if they wish. If they are the only person representing a particular point of view or experience, do not act like “they are posting too much” if they reply to everyone talking with them about it.

Really wish dang would read this. HN takes the exact opposite approach to this and dang prefers to enforce this to avoid confrontation rather than create a space for conversation.

Edit: this is a great example. I can't reply to anyone here, because I'm rate limited, so people can say how many ways I'm wrong and I have no real ability to defend my argument. This is what dang wants, and it's incredibly toxic. The downvotes pour in and I'm helpless.

dimino··on Turning PostgreSQL into a queue serving 10k jobs per second (2013)
Sorry, but what you call a "toy", I call a highly reliable technology that's used in production widely across the majority of Fortune 500 companies. No one here is suggesting anything remotely like what you're strawmanning, but it's clear the straw man is the only argument you can take down.

The reason you are completely wrong and a toxic member of your team is that your logic can be used to justify all kinds of terrible, short term wins that sacrifice any kind of long term/sustainable design. You'd rather make a bad technology play so your boss gets off your back, than think through your decision and make a long term investment into a sustainable, maintainable, improvable, and agile technology that's actually suited to solve the real problem you have.

OF COURSE you're there to accomplish the tasks your business needs to succeed. That's a given. What's not a given is that you need to slap together the shittiest piece of software that'll do that job right then and there.

Your attitude is what keeps companies from solving problems, and forces them to pay dollar after dollar to fix the same issue over and over again. You're selfish, you're greedy, and you cost your company insane amounts of money.

You should not be employed in this industry if what you wrote here is how you think, period.

dimino··on Turning PostgreSQL into a queue serving 10k jobs per second (2013)
I'm not missing the point, I'm discounting the point, because the point that adding technology is additional complexity, and complexity is bad is a nonsense argument that actually stems from a fear of new things.

This has nothing to do with getting shit done, and everything to do with people who don't want to learn new things because they're afraid of not being smart enough to make the new thing work.

dimino··on Turning PostgreSQL into a queue serving 10k jobs per second (2013)
No, I'm assuming you haven't otherwise you'd know that redis AND postgres are inferior message brokers, both of them, and the fact that you haven't corrected me means you're not well versed at all in this problem domain.
dimino··on Turning PostgreSQL into a queue serving 10k jobs per second (2013)
It is very much a bad technology sourcing strategy, and you will kill your business if you attempt it. Period.

It comes from a place of ignorance, and you're promoting ignorance. Learn why technologies exist and make an informed decision about tradeoffs, instead of being lazy and incompetent by blindly choosing technology based on what's a very locally maxima for you personally. It's selfish and damaging.

Edit since I'm rate limited: The folks landing on Postgres are not landing there after due consideration, they're landing on a technology they're familiar with because they don't know how to learn.

It is lazy, ignorant and selfish, and while of course people don't like having truth spoken to them, that's what it is; truth.

Edit 2: Making these poor technology choices will kill your business because you won't have the agility that using a specific message broker technology gives you. You won't have built-in solutions to common queueing problems, you won't have dedicated specific logging/metrics to monitor, you won't have the libraries in your preferred language to directly tackle your problem, you won't have the support community available to you (it will be much smaller), you won't be able to pivot onto related patterns as your needs change, your scaling will always be more complicated because fewer people are doing it and the tool you use isn't tailored for your use case; the list goes on. Your competitors will swallow you because they move faster than you do, and your business will die.

This is annoying to me because I've been in situations where I've had to maintain and write features against technology that was a poor fit for its use, but people like those in this comment sections bitched and moaned about a "new thing" existing in our stack. The reality was they didn't want to learn anything, and were fine pushing the hard work off onto the developers, so they could safely continue to do as little as they possibly could get away with.

Do your job, learn technology that actually fits your use case, and stop trying to push work off onto other people.

dimino··on Turning PostgreSQL into a queue serving 10k jobs per second (2013)
Sorry, but this isn't one of those cases. A RDBMS is objectively inferior for queueing compared to dedicated message broker technologies. This is blatantly obvious if you've ever used both for queueing.

You're applying generic heuristics against a problem where folks have specific domain knowledge that contradicts those heuristics.

I cannot stress this enough; you are flat wrong if you think Postgres is appropriate to use for queueing.

dimino··on In Its First Funding in 14 Years, 1Password Raises $200M Series A
I trust 1Password 100x more than I trust any individual to keep password information safe.
dimino··on Turning PostgreSQL into a queue serving 10k jobs per second (2013)
I find this argument to be pretty weak, and seems to be a stand-in for, "I don't want to use a new technology because it'd require me to learn something, so I'm going to shoehorn something I feel more comfortable with, even though it's not the best tool for the job."

Edit: I'm rate limited so to elaborate a bit.

Queueing technologies are not "new interesting bit of technology", they're tailored solutions to solve a specific problem.

Using a RDBMS for queueing is not what it was built to do, and you will run into issues doing so (I have).

By trying to use one tool for everything, you lose out on all kinds of optimizations, features, and performance enhancements that are specific to the problem you're trying to solve.

It's bad engineering to try and force Postgres into the role of queue when vastly superior technologies exist. You're actively hurting the engineers you work with, and the company you work for, if you force the same tech into use cases it isn't optimal for.

I cannot stress this enough; fear of learning is anathema to software, and trying to hide it behind a veneer of caution is not only disingenuous but potentially malicious as well, maximizing exclusively for the benefit of the individual against the interests of the group.

dimino··on Turning PostgreSQL into a queue serving 10k jobs per second (2013)
rq is pretty good, have you checked it out?
dimino··on Brave launches 1.0
And I suppose adding, "...while keeping you informed about what's happening in the world" or "...while entertaining you" wouldn't matter to you, would it?
dimino··on America’s largest milk producer files for bankruptcy
What's trolly is to derail a conversation, repeatedly trying to get on your soapbox to parrot word association rants about a company that you agree did nothing wrong in this specific situation.
dimino··on America’s largest milk producer files for bankruptcy
That's because you're ignoring the actual article and the discussion around the article and going on a tangential rant.

You're basically "feeling comfortable" derailing a conversation to talk about what you want to talk about instead of the actual topic.

Classy.

dimino··on America’s largest milk producer files for bankruptcy
Again, you went wide. Specifically, Walmart is not responsible for Dean's bankruptcy, which was all we were discussing.
dimino··on America’s largest milk producer files for bankruptcy
Yes, those are the facts, but why is that a problem? Why is Dean the responsibility of Walmart?
dimino··on Telling users why their content was removed reduces future issues [pdf]
How does the power you have over people who are otherwise identical to you play into it?
dimino··on Brave launches 1.0
So you also want the media industry to die as well? Too bad, but most of us don't.
dimino··on John Carmack: I’m going to work on artificial general intelligence
Sometimes, but mostly not.
dimino··on America’s largest milk producer files for bankruptcy
Yes, but try to stay specific to this situation. How is Walmart obligated to buy milk from one specific supplier forever?

You seem to want to go wide with this, but the question isn't a generic one; it's very particular to Walmart, milk, and the claim that Walmart is somehow supposed to buy from Dean Foods, or else they're acting immorally.

dimino··on Telling users why their content was removed reduces future issues [pdf]
Informative? Seems like you want to mitigate my theoretical dissent, to be honest...
dimino··on America’s largest milk producer files for bankruptcy
Wait why is Walmart a bad guy here? Walmart isn't obligated to keep these folks in business, relying on one customer is risky.
dimino··on America’s largest milk producer files for bankruptcy
Walmart wasn't the first company to do this, many of the big grocers are in housing milk production, or so I heard from someone who works at Walmart HQ.
dimino··on Telling users why their content was removed reduces future issues [pdf]
People will flag a comment they don't like, hop on multiple accounts to spam downvotes, will downvote everything a person writes (via their comment history), all kinds of malicious behavior on HN if someone posts something they disagree with.

It doesn't take many of those people to ruin the experience for others, and dang doesn't lift a finger A) because he's of the opinion that disagreement amongst users is bad for HN and B) the software running HN is old and not sophisticated enough to detect bad actors.

I had to abandon my other account recently because I'd get hit with 10-15 downvotes in the span of 3-5 minutes, multiple times a day as I was using the site. Many hours of minimal activity and then boom, minus 15 karma, all at once, corresponding precisely with the number of comments I had that were votable (less than a day old).

Not sure how to describe a nuanced point of view though, it's a point of view that loses critical fidelity when generalized. If the generalization falls into the "dissent" bucket, it's then given the above treatment by bad actors on HN, which has the effect of only allowing a single specific viewpoint to exist on HN, because "flagged" messages aren't displayed at all, and downvoted comments are literally hard to read via fading.

dimino··on A new way to read and print double-sided paper (2016)
I promise I did look! Thanks, though.
dimino··on A new way to read and print double-sided paper (2016)
When you bind the pages this doesn't work anymore, since you can't reorder the read page to the back.

Did I miss the author addressing this, or is it one of the disadvantages not listed?

dimino··on Telling users why their content was removed reduces future issues [pdf]
Could not disagree more; the community is an echo chamber because of how poorly dang treats dissent, and more importantly how easy it is to silence alternative viewpoints here.

As a result, growth doesn't happen here, only self validation. Try taking a nuanced view on privacy if you disagree.

dimino··on Telling users why their content was removed reduces future issues [pdf]
You shouldn't be in that position. You are a user, Reddit shouldn't out you in a position to have to do their job for them.

At the very least, you should get a cut of the ad revenue your sub brings in. No technical reason they couldn't do that, and it would incentivize you to behave, as well.

dimino··on Seeking Developers for Paid Contract Improving Pip
This is great news, very excited to see the fruits of this labor.

Skip to here for a bit more info: https://github.com/pypa/pip/issues/988#issuecomment-55267449...

An explanation of the problem and the solution's approach: https://docs.google.com/document/d/1x_VrNtXCup75qA3glDd2fQOB...

dimino··on Russia Hysteria Infects WashPost: False Story About Hacking U.S. Electric Grid
The onus is on me to figure out what you would need to believe this was Russia?
dimino··on Russia Hysteria Infects WashPost: False Story About Hacking U.S. Electric Grid
The point is the article cherry-picks a single point of data and claims it's the only point of data, when in reality the whole sum of the IOC is what identifies Russia, not any specific piece of malware.
← PreviousPage 2 of 26Next →