Jennifer Long retweeted
When I began learning front end dev, I almost quit. Several times in fact. I thought I would ever be a good developer. But I didn’t quit. If I had, I wouldn’t be here. Push through the self-doubt. You are awesome. Don’t let anyone tell you otherwise.
Jennifer Long retweeted
If developers created horror movies:
💻 Divs! Divs Everywhere!
💻 Weekend Without WiFi
💻 The Builds Are Broken
💻 Out Of Coffee
💻 Recursively Recursing
💻 404
Jennifer Long retweeted
A forthcoming defensive programming skill for front-end developers: assume third-party scripts are blocked (by ad blockers, the browser itself, etc) and gracefully handle the situation instead of throwing exceptions all over the places!
Three rules can simulate birds in flight. So cool! blog.drewcutchins.com/blog/2…
Jennifer Long retweeted
Tips for becoming an awesome developer:
1. Leave your ego behind
2. Never stop learning
3. Find a mentor
4. ☕️
I love fun tricks like this that can make a website unique! #CSS css-tricks.com/having-fun-wi…
Jennifer Long retweeted
"Good code" === creates enough value as a product to justify the labor it took to create it.
xkcd.com/844/
Who doesn't love sorting their socks? Watch how to sort them with #javascript! javascriptweekly.com/link/53…
Jennifer Long retweeted
Taking on a project without clearly defined requirements. Scope creeps will always happen
When the customer says "Who cares about database design? What about mockups? What about workflows?" 🤦♀️ ovid.github.io/articles/deat…
Jennifer Long retweeted
Better Boolean Variable Names 👏
Coming up with good variable names can be a challenge. For boolean values, you can follow this convention. Prefix it with `is`, `has`, or `can`. Just by reading the name, you'll know it's a boolean 👍
#100DaysOfCode #CodeNewbie #301DaysOfCode
"When we plan out new functionality, we have to consider whether the abstraction is right for our consumers, how it might evolve and scale over time, and how narrowly or broadly it can support the use cases of its consumers." ponyfoo.com/articles/module-…
Jennifer Long retweeted
My “Enough with the JavaScript already!” talk wasn’t about JS being bad, it was about HTML and CSS being good. If you can do something in just HTML, do it; if you can do something with just CSS, do it. Only when HTML+CSS fails you is it time for JS.
Jennifer Long retweeted
The most difficult-to-solve programming errors I’ve made were caused by typos.
Jennifer Long retweeted
There will be an entire generation of savvy computer users, who will not have a clue about “bug”. You have to explain it using their choice of word: “glitch”. Tip: spend some quality time with an avid Minecraft player.
Jennifer Long retweeted
🔥 Did you know CSS has a `turn` unit? It’s often easier to turn something `rotate(0.75turn)` instead of doing the math to `rotate(270deg)`
Jennifer Long retweeted
We all write buggy code. But there are obvious things we can do to limit the amount of time we spend hunting down bugs:
1. Write less code.
2. Strictly separate concerns.
3. Simplify anything and everything that can be simplified.
"These patterns provide a stable foundation for a project, of any framework, any methodology, any team size — reducing the need for documentation, refactoring, and amount of tears shed by the developers’ eyes." blog.usejournal.com/10-thing…









