When a catastrophic issue arises on your project, the immediate push is to get in there and fix it as soon as possible. How can we patch? How can we get to the bottom of it? How can we make it work better? We do this, without fully understanding the extent or impact to the problem as a whole. We do this without possible fully understanding all the issues at large but wanting to do…
So many posts are geared towards that one single format in title that can lead to an increase in metrics. Take your message and cram it into that format. Does it fit? Doesn’t matter, because it needs to, if it gets watered down on the way out, it’s a problem with your content. Writing content, consuming content, in different ways, is what makes it incredible – so if your work does fall into the format…
The statement arises from a meeting that easily could have been an email. When I hear this there are generally two thoughts that go through my head. This meeting was a presentation (there is a difference), in which case, it wouldn’t work as an email because than people wouldn’t benefit from hearing each other’s thoughts and questions (which is where the magic in a presentation occurs). If it was meant to be an email, but…
Try a hashtag and get some retweets and likes. Now what did the use of that wonderful hashtag get you? You could write anything in the world and use that hashtag and get the same number of retweets, likes and engagements? Your business/side hustle/portfolio/project isn’t driven by the number of followers, shares or likes that you get – it’s driven by what you do, when you need to do it.
Are you not sure what that error means that your code just showed to the screen? No idea what to do next? Not sure where to find the corresponding log file? No idea how to reproduce it. Looks like there’s a problem with your code that needs to be fixed before it gets to the user – because if you don’t know what it means, they don’t have a chance of knowing what it means.