Life is ultimately calmer when one faces their problems head-on instead of avoiding them. You can avoid problems for quite a while, but in my 30s I had to face many of them. They eventually will catch up to you.
But don't do hard things alone.
Get a counselor, therapist, doctor, pastor, or life coach (depending on the situation). Or even just a close friend.* Have someone on your side.
(*Don't expect too much from friends. They're friends, not taking the place of trained pros.)
Build your conflict resolution skills! So many of my problems came about because I didn't know how to resolve conflicts effectively.
I see this in my friends. They suffer for weeks because they don't want to have one hard conversation. Or make commitments they can't keep.
Speaking of friends, be very intentional about who you spend your time with.
You're giving them access to your thoughts and influence over what you believe and your values. No matter who they are, they will have some effect on you.
Spend it with people you respect and admire.
There's a Proverb that says "As iron sharpens iron, so one person sharpens another."
I ran my business with little accountability for ten years. I have grown far more when I merged with another company and had to compromise with my co-owners instead of "command subordinates."
• • •
Missing some Tweet in this thread? You can try to
force a refresh
One of the things I’ve noticed about junior-level developers is they tend to optimize for the wrong things.
For example, they will get so nervous about taking too long that they won’t properly test their changes before submitting the PR.
This results in a lot more of the reviewer’s time to be spent testing and providing feedback. Which is fine here and there when you’re starting, but if it becomes a pattern, the reviewer can start to become impatient and lose trust.
Luckily, this isn’t too hard to fix.
Create a “PR checklist” that you use for each PR and check off the various things.
[ ] Works on Edge
[ ] Works in different screen sizes
[ ] Includes tests
[ ] Includes documentation
Last week, I got an email from a new consultancy founder asking some really good questions about running a consultancy. I answered her questions in detail in the email, but I'll also share some of the answers here.
1/
1. How do you manage the drought periods (those periods when no projects come in but you still have to keep the lights on)?
This is one of the toughest parts of having a development shop. Developers are _expensive_. Having them "on the bench" (as we say in this business) is
2/
...super difficult and can set you back months. Missing one week isn't just replaced by one week. If you have a 20% profit, that means every week missed is 4 weeks to make up the 80% cost, using each week's 20% profit.
3/
So, anyone want to see my bigger backyard project that’s been in the works for a couple weeks?
So, last year we installed an above-ground 18’ pool.
I had my brother-in-law flatten out an area 25’ in diameter, though, because I figured if this experiment went well we might want to upgrade to a 24’ sometime later when the pool needed to be replaced.
(Bear with me...this will go kinda slow. I’m doing this between sets as I work out, and will probably be tweeting over the course of the evening. I promise lots of pictures though.)
I received this Twitter DM from someone who asked the really interesting question: how do you manage underperforming team members?
I don't think we've entirely "solved" this, but after employing people for 10 years, I have thoughts.
1. Start from a position of empathy.
Most people _want_ to do better. They're struggling for various reasons, not all of which are professionally-related. Start by seeking to understand what might be impacting their ability to be productive.
Relationship problems, difficulty concentrating, lack of experience in a key area, communication problems, lack of sleep, slow computer, lack of enthusiasm, poor code by coworkers, lack of direction, too much direction -- all real reasons why people have underperformed for me.
Remote work requires new habits. I'll post tips on new habits to develop as I think of them in this thread. #remotework#remoteworkworks
Slack tip: in high-signal channels, if someone posts something important to the group and you read it but don't need to respond, mark it with an emoji reaction so the OP knows you saw it. It takes a couple seconds and is very helpful.
Never share a video camera on a video conference call. I don't care how much money you spent on that special conference room designed for it, just don't do it. One person, one camera, one headset/earbuds. Just get in the habit.