1,181 karma · joined October 3, 2017
meet.hn/city/br-Rio-de-Janeiro
I speak for both you and your employer.
technical@theideaofcoffee.com
Though I think it will be difficult to switch the narrative of better-performance-at-all-costs mindset toward something like this. For almost every application, you'd probably be better off worrying about integrity than raw speed.
Also lots of providers just string up cable on poles, which are routinely snagged by trucks, shot by ammunition, run into by cars, etc etc, so even more vulnerable than shallow burial. Some of these cables are major links so damage can cause wide-reaching problems. No match for an out of control sedan, let along a nuclear strike. [4] [5]
[0] https://www.techrepublic.com/article/google-fiber-is-using-a...
[1] https://wpln.org/post/google-fiber-disruptions-have-some-say...
[2] https://www.nashvillescene.com/news/pithinthewind/google-tre...
[3] https://arstechnica.com/information-technology/2019/02/googl...
[4] https://www.wmur.com/article/crash-manchester-comcast-servic...
[5] https://www.cbsnews.com/sacramento/news/crash-vandalism-comc...
and etc
It’ll probably turn out that this update was pushed out against the strident, loud warnings of some small dev group within the company, and overruled by the all-knowing managerial class to keep up an OKR. They’ll have been warned six ways to Sunday but...
I’d definitely be not be the one pushing the big red button.
>> 4 There’s a continual disconnect where people with experience can see problems then construct easy and rapid to implement solutions, but people with less experience think every little bug fix is a “we don’t have time to stop the world for 6 months so we can never fix anything!” problem. We get excited to fix problems because we see fixing problems is tractable and we can implement these fixes in days instead of months as opposed to others don’t understand how everything works. It’s amazing how the simple practice of just doing the work solves many problems sooner than many people think is possible.
I didn't expect a mind reading today. It's kind of cathartic to read about someone experiencing similar problems and know that it's just a people thing after all, the tech really doesn't exist, just the individuals doing it.
I wish I thought of it on my last trans-atlantic!
Then I dropped it, because, hey, the glitterati of hacker news and all of the others must be right, huh? I let it wither, while working on other things, working for other people, making them wealthier, while all in the back of my mind I keep thinking: "maybe I should keep working on it."
Services doing the same exact thing started popping up. They get traction. Users are mostly happy with what they were doing, but they didn't have half of the features that I had already implemented in the code that hadn't seen any use outside of my testing environment. Some take off so well they have a now-publicly traded company doing the same thing. Ten years after I started my little project.
Fuck.
Lesson learned. The naivete of youth is a harsh teacher. Work on it. Put more effort into it. Ship it. Go with your gut--you probably have a better sense than you think you do of what will work and what won't. Ignore the hivemind. Don't leave room for the regret you will inevitably feel when you're scooped.
A lot of these companies also seem to be reaching beyond their grasp as well. I don't think a lot of them necessarily have the vision, nor the wisdom on their staff to recognize a well-rounded background, especially if there isn't the blaring siren of a FAANG on someone's resume. They're simply not equipped to dig in. It's probably also a matter of raw number of years, they're afraid that if you join, you'll get bored then they'll be back to square one (been there).
This is a reasonable step to take if you're working in a reasonable company with reasonable "management". If you're unlucky enough to be working under a manager that refuses to recognize there is a problem, even with compelling data, prepare for pain. In that case nothing is allowed to be done because "well, that's how we've always done it and doing something about it might upset someone". It's really time to quit and find something new at that point because there is generally no hope of turning that around.
> If you can’t easily explain why something is difficult, then it’s incidental complexity, which is probably worth addressing
See above. "That's how we've always done it, and someone is used to that work flow, so we can't change it." Sometimes this will lead to a legitimate Chesterton's Fence situation, in which case you'd want to regroup and rethink it. Otherwise, the batshit insane is the default. Target the latter.
> Try to solve bugs one layer deeper
"There is no time to do that! We have so many other projects!" While being blind to the fact (or better yet, burying their head in the sand and trying to ignore) that it's all self-induced.
> Don’t underestimate the value of digging into history to investigate some bugs
"We can't change that because one of our people close to management made that decision and it might drive them away." Good, get them out, that's the only way to really fix it. Ideally if the management that hired them is pushed out too.
> When working on a team, you should usually ask the question
"Who are you to question our wisdom? Who are you to suggest something else, it's working in production."
These are great things to start conversations, but you have to start them in an organization that is willing to change and be willing to take your advice to heart. Don't waste your precious life trying to change what can't be change, no matter how much you want to see it change.
Then that's implemented with no warning to be able to migrate important info out into a wiki or other documentation. So in the end, no better than IRC really, but I get it, not a Slack problem, but allowing that whiplash at a click of a button doesn't help. Slack seems to help paper over deep cultural problems in a way that makes it all colorful and squishy.
But as other seem to agree, it's pretty bad at keeping anything organized like you want to be as an info repo, there are tools that are geared toward that specifically. Don't crowbar one into the other.
It’s by far Apple’s worst built-in app on the iphone, by far. I wish they’d give it some love, moreso after having bought out Dark Sky.
It all comes down to the people. The right people can make all the difference in something like that, the wrong people make it miserable for the rest.
Playing the innovation hero in that kind of org is dangerous, and I have the battle scars, the burn-out and resentment to prove it. Others have pointed out that the point of the power structures is to self-perpetuate and any threat to that is swiftly dealt with.
It's just so sad to see, all because people fear change. I don't know how to change that other than replacing those lifers and swapping out management.
Now I know what to look for and am willing to bounce at the first sign of it.
I love to see these projects keeping the legacy of these old, great machines alive, if not running some fraction of unicos, at least aesthetically.
Then we’d know this set of language features you’re familiar enough with to hold that cert. It might cut down on the waste and proliferation of useless tech that seems to be strangling the industry because people just want it on their resume.
It would do enough to dissuade companies from hiring non-licensed engineers (hey you could actually call yourself and engineer and not feel like an imposter), and would put a hard liability on things that definitely need it: financial and health data, which seems to be ripe for exploit and disclosure.
One way or another the insanity of the current system needs to stop.
I'd love to see a post, maybe there is, about maintenance of all of this, perhaps a story or two about an issue that maybe had some existential threat to the station and how it was overcome. I look at the majority of the infrastructure there and just keep in the back of my mind how fragile it all seems. And yes, obviously there are redundancies, but even with redundancy, things can still fail, they exist in the physical world after all.
What demonstrates obedience more than having to solve a problem against the expectations of someone holding something of value over your head? "If you don't do as we say in the way we tell you to say it, you don't get this <thing>." No matter you may have a different perspective on solving the problem, even going so far as to dismiss it outright, it's all about the rubric. No subtlety, no interpretation allowed. Make it easier for your interviewer masters.
Personally, I think the main post hits it right on.