Explore >> Select a destination
|
You are here 
|
humanwhocodes.com | ||
| | | | |
weidok.al
|
|
| | | | | I recently had 35 meetings in a week. This is a lot, but not uncommon for employees of large enterprises. While it is easy to lament an organization's "meeting culture", there are also actions individual employees can take to reduce their meeting load. I recognized that attending all the meetings on my calendar was not possible (one time slot was quadruple-booked!) so I developed the following approach for responding to meetings. | |
| | | | |
shiftmag.dev
|
|
| | | | | This article is a distraction. You should get back to your work! Or not? | |
| | | | |
mtlynch.io
|
|
| | | | | Updates about my life and what I learn about creating software | |
| | | | |
claritydev.net
|
|
| | | Lately, I have been asked increasingly often for some tips on how to become a self-taught developer, so I thought I'd write a post about it, reflecting on my experience and pointing out the things I'd do differently. In this article, I'll try to give general advice on how to improve for those considering or maybe already on the way to becoming self-taught software developers. It should be noted that the focus of the post is on front-end development since that's what I did; however, a majority of the advice can be applied to becoming a software engineer, irrespective of focus. | ||
