123 karma · joined October 14, 2011
The book 'Deep Work' by Cal Newport has some good perspectives on this.
Don't: * Ask my current and expected salary requirements
Performance testing can highlight areas of the code that need help, so work to improve scaling and performance abilities can be used to justify resources to refactor related code.
Sometimes a new feature request can be used similarly where the refactoring and new feature development is a better option than trying to develop only with existing code.
Got tired of carrying laundry downstairs, so I changed one bathroom cabinet drawer into a laundry chute.
Current self checkout systems appear to only move the work of a cashier onto the customer, then force them to wait longer for anything that needs correction.
First story: The Fireman by Ray Bradbury
When remote, the communication tools are different. Instead of walking over to talk to others, you're likely using chat, voice, or video calls. The meetings include shared screens with conference calls. After a meeting, you may chat or call someone for a private discussion. Those private discussions are likely how you build social bonds and get to know others personally. They can also make it clear you're available to help.
In the office or remote, your communication style builds a perception of how involved you are in projects, what you can contribute, and whether you're viewed as a needed or disposable.
I use them to send these weekly reports to our developers: Slow queries, lock waits, transactions with the most rows affected, transaction by highest statement count, largest statements by rows affected, busiest tables, queries doing full table scan or full join, and busy writes.