Help support Dawg Nation Hockey Foundation by donating or retweeting. https://t.co/sdAhqQNzGf They really care about the people in the local hockey community.
"Habits are the compound interest of self-improvement. Over the months and years their effects can accumulate to an incredible degree." ~ @JamesClear: https://t.co/CjOiOPMGM2
Going smaller can help you move forward.
Is a problem hard to solve? Break it down.
A topic challenging to learn? Try it in chunks.
Finding an exercise hard? Reduce the intensity.
Master the first step then take the next.
Any recruiter that expects you to drop everything and respond within a day is clearly looking for head-count instead of good fit.
Which is a good signal to me about the culture of the position...
Here's @KentBeck on 100% coverage: "I get paid for code that works, not for tests, so my philosophy is to test as little as possible to reach a given level of confidence." Works for me.
Talking with a senior engineer I noticed a pattern. There were bugs. Nobody knew how many. They weren't on anyone's roadmap.
So the engineer dug in. Discovered curious & horrifying facts. Discovered a lack of organizational urgency. Fixed stuff. Encouraged others to fix stuff.
Don’t use UA sniffing!! Dave is right. It almost never works, especially over time.
Use feature detection instead — in your JavaScript, or in your CSS (using @supports). That way, as soon as a browser ships what you are testing, you have a whole bunch of new users with support.
I highly recommend every web developer check Can I Use regularly. I often hear from folks grumpy about something not being supported… when it is. It already is! Go to https://t.co/ar5PF0Djvk to see what’s already arrived in browsers and what’s coming soon.
Tip: Progress is not always linear.
Sometimes it can even feel like you're going in circles. Step back and acknowledge small wins towards your goals. They add up. Even if you have to start over, it's not always from scratch, it's often with experience.
yes. individual engineers can *write* software, but only teams can deliver, ship, maintain and own software.
the smallest unit of software delivery is the team.
@rodhilton It is easy to assume others use a service for the same reasons as you do (such as the privacy of DuckDuckGo). It is jarring when others have different reasons (such as actually desiring links to anything but the truth to reinforce their personal bias).
@avdi@cvennevik I love “full-circle developer” because it is about doing work that impacts the e word (in however small a way) and seeing that impact and then improving it
@jeanqasaur@michael_nielsen Yeah. 👆 Most people have never worked on a high performing engineering team. They literally don't know what they're missing.
Which creates 0 pressure for low performing teams to improve.