Explore >> Select a destination
|
You are here 
|
blog.stackblitz.com | ||
| | | | |
tomrenner.com
|
|
| | | | | It is upsettingly easy to work hard without being productive. The Lean Startup includes a quote I really liked: "[People] feel that a good day is one in which they did their job well all day." The point being that this doesn't account for whether you are doing the right work. This is a really common trap to fall in to. I know I have often worked really hard on something and produced code I'm very happy with, only to talk to my boss or the client and find that nobody else seems to be nearly as pleased with what I've produced as I am. | |
| | | | |
github.com
|
|
| | | | | Contribute to pashpashpash/shopify-mcp-server development by creating an account on GitHub. | |
| | | | |
egghead.io
|
|
| | | | | ChatGPT and similar conversational AI tools have quickly made impressions in the tech industry and beyond by giving the people using those tools a more ... | |
| | | | |
citizen428.net
|
|
| | | I originally wrote this article for Codementor in October 2014. It should have something for everyone, from fairly new git users to experienced developers. 1. Discard local file modifications Sometimes the best way to get a feel for a problem is diving in and playing around with the code. Unfortunately, the changes made in the process sometimes turn out to be less than optimal, in which case reverting the file to its original state can be the fastest and easiest solution: | ||
