←back to thread

1226 points bishopsmother | 1 comments | | HN request time: 0s | source
Show context
yamrzou ◴[] No.35046052[source]
I'm not a user of Fly.io. I can't help but notice how remarkable the effect of open communication on potential end users like me. I remember reading about their reliability problems on HN some time ago. That biased my view of the company. After reading this, the open communication and transparency restored my trust in them, and would make them again a potential candidate for future projects. Because now I know that they acknowledge the problem and that they are trying to improve things.
replies(11): >>35046292 #>>35046484 #>>35046582 #>>35046831 #>>35047508 #>>35047533 #>>35048038 #>>35048182 #>>35049832 #>>35050458 #>>35053770 #
snapetom ◴[] No.35047533[source]
This is probably therapy, but your message and fly.io's post resonates a lot with what I'm going through. I took a product owner role about 6 months ago, my first, with a company that has turned out to be just a mired mess, and a product universally hated both internally and externally.

Long story short, it's completely over-engineered by a bunch of intellectual engineers with no focus, no discipline, and no oversight. It ended up not delivering on any promises it made, and there were a lot of them.

I was warned left and right before presentations and meetings, "this customer hates your product because of ...." I started off every meeting with saying, "we're rearchitecting the product, this is how we're doing it, this is the tech we are using." Immediately there was a sense of relief from customers, followed by questions like, "why can't <current product> deliver <feature> that was promised?" I'm completely honest with bad decisions that were made and how it impacted the feature. Sure, there is skepticism on what we are doing, and I tell them they should absolutely be skeptical based on our track record. The result has been customers who have hated my product now offering to work with us on development.

I've also been completely forthcoming on configuration, security, resources, and setup issues I am finding, many of them are absolutely freakin' insane. I've flat out told customers it's frankly embarrassing and never let us do something like this in the future. The best feedback on this was, "At least you're telling us something. We usually get silence from this team."

God, this is the most depressing job ever.

replies(8): >>35047778 #>>35048040 #>>35048252 #>>35048313 #>>35048395 #>>35050562 #>>35053284 #>>35055179 #
anthlax ◴[] No.35055179[source]
Could you further elaborate on “intellectual engineers”? What mistakes were made? Esoteric languages? Obfuscating design patterns?

Partially so I could learn from mistakes and partially since I’m a sucker for post-mortems :)

replies(1): >>35063131 #
1. snapetom ◴[] No.35063131{3}[source]
There is a part of the app that extracts and parses a database log. There is C, Java, Perl, Go, and bash scripts all over the repo. The bootstrapper is written in Java, but the core work is done in Go. Commandline arguments that are documented in comments may or may not even work. The Go section is one big state machine.

That's just to take a database log, put it into JSON, and zip it up.

That all for just one step in the data pipeline. The others are slightly less hairy, but 75% of this pipeline is literally just moving data around. It goes from JSON to MySQL to Postgres to Parquet. There is no data enrichment at all during these steps. It literally just unpacks from one format, packs to another and repeat.

The whole fucking thing is just one big masturbation circlejerk for a bunch of engineers that have thankfully been RIFed/forced out...