Sony worries that Microsoft might undermine PlayStation "simply by not making it as good as it could be" by making Call of Duty games for the platform perform worse or by raising the price of its games for the console.
https://t.co/xVDvu0UqxH
@housecor I think the guideline being broken here is "Things that change together, live together.". If a single logical change requires you to touch more than one repo, that's a smell indicating that those two things are actually one thing.
Refactoring, by definition, provides no new user value. It is not a story (which describes your user's work, not yours). Refactoring is not a task either. It's just something that you do continuously as you work—part of the development process.
So, no. Never.
@KarlGerm My strategy is to listen to audio books while I'm doing something relatively mindless eg driving, mowing the lawn, etc. I can crush books this way.
What's with all these "cocktails for the Big Game" flooding my inbox? I mean, sure, moose and elk would be much easier to shoot if you got 'em liquored up first, but I just don't think it's a practical strategy, or really very sporting.
Moving from software engineer to senior software engineer is a big step.
Most engineers get hung up on assuming that their technical depth is the key to growing their position. But is that really what's holding them back?
🧵
When you're interviewing for a new role, you might find that the company/team is messy or disorganized. Should you take the role?
Here's what I observed: if everything works well-oiled, there's little to fix. At a messy place, fixing things can be hard: also hugely impactful.