This is a weekly roundup of awesome DEV comments that you may have missed. You are welcome and encouraged to boost posts and comments yourself using the #bestofdev tag.
Create a clear separation between "home" and "work" space.
This allows one to easily "enter" or "leave" work-mode.
You also should probably make another session on your computer, for work only, as to avoid being distracted by "home" stuff (even better, another OS installation with some other, dedicated, disk. SSDs are cheap now).
For a nice separation, a plant wall is pretty and blends in most environment styles, and taking care of it will count as a pause ;)
- Grep through the logs for any obvious issues or errors. With decent logging, 50% RCA happens here.
- Try to replicate the scenario in local environments and see the bug in action.
- Keep adding
printfstatements after each line of execution. Occasionally use the debugger as well on local to triage the issue.
- Forget to remove
printfstatements when committing fix.
- Create hotfix commit to remove debug logs 😄
- Actually deploy fix to production.
I've had this alias in my
~/.gitconfig since about 2009:
pu = !"git fetch origin -v; git fetch upstream -v; git merge upstream/master"
The "display: none;" style on the button is just a possibility: it may have been better to simply make the button slightly transparent initially, and have it be opaque when the user has typed something, but of course, there are so many ways to implement this.
For example, I am currently building a password manager, which uses the placeholder-shown trick to display an arrow icon for entering the password-vault when the user has typed content into the password field.
In the spirit of #hacktoberfest, @colbymelvin
replied to a call for contributors, submitting their fix for an issue described in Call for DEV Contributors: Posts on front page do not load until scrolled down 🐛:
Be sure to check out the #hacktoberfest tag for more great articles an discussions.
See you next week for more great comments ✌