snockerton

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...

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.

Impressive lulz in this post. Do you require an outrageous sense of humor as well?

This is the same CYA attitude that I have been assuming the last 2 years because it's such a frequent occurrence.

The only issue is that I still get blamed. I don't know how many times I've repeated this scenario:

1. I highlight gap / issue in code.

2. Team says, "Need to ship; we'll accept the risk"

3. During go-live, fecal matter hits fan because of aforementioned gap in code.

4. Everyone acts surprised.

5. I point out that I mentioned it 2 months ago.

6. Everyone makes excuses / claims they don't remember it that way / moves on to burn down another project.

7. I'm left to clean up a mess / have taken a hit to my reputation.

Not sure what I'm doing wrong...

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?

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.

Was hoping for good read on economics, found guy whining about his parents' views.

Usually Massimo's stuff is quite well thought out and practical when it comes to adopting new models in the Enterprise, but this article has a "I'm annoyed by this platform because it doesn't work how I want it to" sentiment throughout. He seems to miss a lot of the potential value that the serverless architecture model brings to the table.

It's pretty well established that Amazon's usual approach is to provide a "toolbox" of services that can used to build any number of app architecture permutations, without all the typical fluff and polish expected by large business customers. I for one, as an engineer, appreciate this model since it's much more accessible and lightweight.

I agree that the lack of an easy, declarative deployment capability is one of Jenkins' biggest flaws and doesn't get near enough attention.

General macroeconomic scare mongering has an upside in that perhaps some fat will be trimmed. Those with a product or service with real value should remain standing.