Hallo @Telekom_hilft, ich brauche dringend Hilfe: Nach 7 Monaten und 4 gescheiterten Terminen (fehlende Ausrüstung, falsche Teamgröße, zuletzt No-Show) habe ich immer noch keinen Glasfaseranschluss. Läuft bereits im Forum: https://t.co/3mPz9SDakC Könnt ihr das bitte übernehmen?
.@enterprisecares@Enterprise absolutely abysmal situation at FRA. Took almost 2 hours in line to get to a desk agent. Then told they’ll give us manual instead of auto, and will contact us later when the car is ready. 😧 and now nothing, u told my wife that I have to contact you
@engineering_bae Doesn’t sound dramatic to me. The upside of a highly skilled manager is huge.
It’s more important than ever to have a management chain that earns your trust. With the volatility in the job market right now, even an average manager can put you at much greater risk.
If you assume ppl who are different are worse at their jobs, don’t pretend this is a sociopolitical opinion. Don’t hide behind the term “DEI hire”. Say what you mean. Use the slur.
Complaining about "DEI hires" is a wild display of insecurity, ignorance, and bigotry. Under qualified ppl do not keep senior roles on high performing teams. Underrepresented peeps have to be extra badass to overcome bias.
Complaining about "DEI hires" is a wild display of insecurity, ignorance, and bigotry. Under qualified ppl do not keep senior roles on high performing teams. Underrepresented peeps have to be extra badass to overcome bias.
Here’s the thing folks. I’ve been coding 32 years. When something like this happens it’s an organizational failure. Yes, some human wrote a bad line. Someone can “git blame” and point to a human and it’s awful. But it’s the testing, the Cl/CD, the A/B testing, the metered rollouts, an oh shit button to roll it back, the code coverage, the static analysis tools, the code reviews, the organizational health, and on and on. It’s always one line of code but it’s NEVER one person. Implying inclusion policies caused a bug is simplistic, reductive, and racist. Engineering is a team sport. Inclusion makes for good teams. Good engineering practices makes for good software. Engineering practices failed to find a bug multiple times, regardless of the seniority of the human who checked that code in. Solving the larger system thinking SDLC matters more than the null pointer check. This isn’t a “git gud C++ is hard” issue and it damn well isn’t an DEI one.
I need y'all to understand something:
This isn't Willie Mays.
This isn't Satchel Paige.
This isn't Josh Gibson.
This is REGGIE JACKSON. HE PLAYED WHEN I WAS A KID in the 70s and 80s.
THIS. IS. RECENT.
Persuasion tips for devs:
- Be concise and clear
- No one wants to hear they are wrong
- Assume the other person wants what's good for the org
- Garbage in/Garbage out (You'll get back whatever you put in. Don't be a jerk)
- Patience (It's your emergency, not theirs)
As you move through your career, you are going to get bad feedback. Your job is to understand if the feedback comes from a good place and a way to apply it. Don't simply take feedback – good or bad (even from your manager). Understand why it's important and how it can help first.
It’s extremely difficult to do great work in fear. Fight or flight blocks logical and creative reasoning.
This is why org health is paramount, and critical to the bottom line. These things are not separate, they’re parts of the functioning whole.
@trisha_gee DRY principle. I take time on every task to factor all the tedious boilerplate I find myself writing into cross-project sharable utils. In PRs I encourage teammates to do the same. This snowballs making everyone more productive. Code is more readable/testable/reliable too.
@trisha_gee Dev env to code/run/test/debug/repro all in one place (ideally local). This is not a given working on aging systems that have proprietary lib and runtime dependencies. All friction in the core dev loop is poison.