I'm glad that others are voicing the same issues I'm experiencing. Sometimes I wonder if I'm taking crazy pills.
My solution has been to place an Apple bluetooth keyboard -on top- of my 15" MBP keyboard and that seems to work pretty well, but wow, it shouldn't have come to this...
And yet even in this story, there are multiple comments a la "Yawn. I can't believe this is an issue. Apple shouldn't be paying attention to niche complainers."
Because the level of vitriol is not commensurate with the problem? They'll replace the keyboards, most people don't have issues. (I know I don't, 2+ years in).
Nerd entitlement rage is monotonous. The latest models 4th gen keyboards are pretty much fine.
"they'll replace it with the same faulty keyboard"
We know they've gone through several revisions that have purportedly reduced the incidents of problems, and they'll likely go through more improvements. When you get your keyboard replaced they will use the better variant.
Thankfully I get to make my own hardware decisions, so I've made a point of ordering a new MBP every time a new revision is released, and promptly returning it to Apple the next day when I realize the keyboard is still absolute rubbish.
I would like to think that maybe if some person at Apple runs a report for returns and see that "keyboard" accounts for a huge majority of returns, they may actually act with some semblance of haste.
>My solution has been to place an Apple bluetooth keyboard -on top- of my 15" MBP keyboard and that seems to work pretty well, but wow, it shouldn't have come to this...
I did that with my 2008 unibody Macbook Pro (yes, Macbook keyboards also sometimes broke pre-2016), which also suffered from EM209 [1] (second time, beyond Apple's free-fix period). I used heavy-duty rubber bands to both hold the screen together along the non-visible borders, and affix the wireless keyboard over the computer's. Certainly something to never ever show anyone else, but completely functional with the exception of the inability to close up the computer. Only after failing to start one day did I replace it with the 2012 non-Retina I am typing on; come to think of it, it's now exactly as old as the 2008 when it completely died, albeit in full working order. (It did need a keyboard repair. I am hard on keyboards.)
Can't believe I haven't thought of this! I've been using an Apple BT keyboard with my MBP but never thought to stack it right on top of the butterfly keyboard. I can confirm that it fits the 13" MPB, just like your 15"!
Update: my Apple BT keyboard (which is many years old -- it takes 3 AA batteries, not 2) slightly covers the top of the trackpad on my 13" MBP. This means that the palm rejection algorithm does not work as well. I may be able to get it to work for me by just adjusting how I hold my hands when typing, but it's not a clear home-run with my smaller laptop and possibly larger keyboard. I would seriously consider getting a smaller BT keyboard to make this work, though.
Haven't tried that, but it really sounds it would be terrible to the wrists after prolonged use (in which case "prolonged" would mean longer than 10-15 minutes).
It appears that the SLA guaranteed uptime for Azure SQL Database is 99.9% or 99.99%, depending on tier. That equates to the following allowable downtime per month (which I think is what they base SLA fulfillment on):
99.9: 43m 49.7s
99.99: 4m 23.0s
Sounds like they need to cough up some money for their four 9s customers...
When is such an awesome company like GitLab going to get serious about compensation and actually fix their calculator for regions outside of SF? I know firsthand that this is preventing many experienced people from even bothering to pursue opportunities there.
I'm not sure if you're replying to me or the company. I have nothing to do with the company, I'm just some random developer wiseguy. I don't see any mention of needing experience with the latest LULZ stack in the posting and I suspect it wouldn't be compatible with ICE. There are worse things than being stuck in Paris with plenty of lulz I would think but YMMV.
Perhaps you're doing what I'm about to recommend already, but I can't be sure based on what you wrote. It's in regard to "2. Team says, "Need to ship; we'll accept the risk".
If the Business Unit, for whom the software is being written, has a representative on your team, then make sure you explain the risk in purely business terms, not technical ones. A BU rep's ears are going to perk up with statements like "invalid posts may get written to the general ledger" or "1 in every 20 orders may get dropped" rather than "universally scoped variables are being overwritten by invalid data in some cases" or "uncommitted nested transactions may cause a core dump."
If your team doesn't include a BU rep, then you could always get friendly with one and explain the potential risks over coffee or lunch. Perhaps even suggest some questions the rep should ask the team before the mod goes live.
In my situation, a BU rep is always part of the team and I rarely have other developers on the team. The reps and I have lunch together regularly anyway, so they get my opinions and recommendations that way.
IMO there's nothing you can do to fix this culture. They're determined to ignore the inconvenient problems and then conveniently forget they were told about them. Even if you attempt to document these things, you'll just be labeled some negative name like "whistler blower" or "anal" and the same reputation problems will exist.
FWIW, 2 things mitigate this. First, some companies do actually remember people who fix things and get things done, so that's on your side. The other is that it's not likely you'll be there long-term anyhow. Companies that do this also generally fail in other departments, like paying you what you're worth as your worth increases. So you'll probably look for a new job eventually anyhow.
I know it's hard to see from where you're standing, but I wouldn't fret about it. Just keep doing your job the best you can and warning them, and let the chips fall where they may.
You have to win people over by making their lives easier or by making them look good. This does not necessarily have to be related to code or technology in any way.
Then, after people have a visceral positive feeling about you, make some tiny suggestion for improvement. Make the improvement, and whoever approved it, do something to make sure they associate your suggestion with a positive experience.
Slowly repeat. It is a slight selling of your soul. It is effective.
The only thing you're doing wrong is pointing out that you mentioned it two months ago. That's the last thing an organization faced with a problem wants to hear. What they want is for everyone to act like the problem was entirely unpredictable and have everyone make 'heroic efforts' to make the fix.
probably you're doing it too serious and taking it too personal. After 20+ years in the industry, I got desensitiveized enough to bother that much about small things, and when i point to the issue i usually do it in the "constructive" "spirit-sharing" and "team-building" way - "Ha! Just imagine how those suckers - customers or downstream devs - would be hitting that bug, completely lost at what to do, they would have no chances to make it work so we should give out a Grand Prize to the unlikely one who would make it through... " I noticed that various leaders/management/etc. have hard time to full-heartedly subscribe to that vision of future. Not that that gets the thing fixed or anything like this, mind you. Yet it helps with the blame part if/when it still comes my way - "Wow! when _we_ (me and you, the manager/etc.) were laughing at it _we_ did look into the crystal ball! _We_ are that smart!" The management somehow don't enjoy sharing in on that smartness :)
Perhaps you failed to build a paper trail (i.e. an email trail) to document the fact that you predicted the disaster, and who it was that decided to ignore your warnings. If you do that, when the fingers start pointing in your direction, you can send everyone copies of the emails that prove who is responsible for the mess.
No, that's not it, because usually management doesn't give a shit about that. Even if you have the paper trail, they're still going to say, "Quit whining; it's 3 AM and stuff doesn't work. Fix it."
If they want us to be responsible, then they need to give us what we need when we say we need it. You're saying they should be able to make us cut corners and then support it. You don't get to have your cake and eat it, too.
If drawing the line on what is and isn't harassment is subjective, perhaps they should focus on building better mechanisms for individuals to take filtering / blocking into their own hands? One could argue that Twitter has these features already, but apparently the "privileged class" (celebrities) are incapable of leveraging them?
The article explicitly calls out their lack of product development as hindering the process. The example given is of a feature they've been discussing for 5 years(!) where it would favour displaying replies made by individuals the original tweeter follows.
I don't use Twitter, never have, but I don't understand why the platform doesn't have a whitelist mode, where only those people you've added to a list can message you. Seems like it would sort the problem for good, but I'm probably missing something.
I'm in the same boat as you on Twitter usage. But I suspect it's because being able to talk at anybody, including celebrities, is part of the appeal of the platform. The whitelisting mode you suggested makes it more like a one-way broadcast - you can see what people are saying but not join in.
Looking at tenure in isolation of any other context is meaningless. I've interviewed candidates with multiple 6-12 month positions on their resume that turned out to be great contributors, and other folks with 5-10 year positions that were horrible.
My solution has been to place an Apple bluetooth keyboard -on top- of my 15" MBP keyboard and that seems to work pretty well, but wow, it shouldn't have come to this...