Web Development Reading List #109

Web Development Reading List #109

Advertisement

Building products or software is not easy. As developers, we are constantly aware of this fact. As managers, we also know this. As product owners, hell yes. But the most important thing is to also teach our customers. It’s important that we figure out a holistic approach to build a product that pleases the user and all others who are involved.

News Link

4
A non-HTTPS website with a login form

General Link

  • Sending cloud-based, self-hosted emails is a challenge. From my own experience, I can recommend everyone who is planning to do so the “The Hostile Email Landscape5” article. It explains why it’s so hard for newsletter senders (like me) to avoid the spam folder and why the system is still broken.
  • Creating front-end components can be hard, especially if you want to give others the opportunity to style or extend them on their own. Nicolas Bevacqua shares lessons learned from building and sharing his components6.

Tools Link

Security Link

Accessibility Link

  • Wouldn’t it be great if we could set a flag in our developer tools to see outlines of elements for accessibility debugging? That’s exactly what this Chrome DevTools discussion12 is all about.

JavaScript Link

  • When you want to build a public JavaScript library you have a couple of decisions to make13. What to provide support for? Which technologies to support? Nolan Lawson gives some tips on what to do and what not to do.

CSS / Sass Link

Work & Life Link

  • We can find some good advice on how to fix the pricing of our projects18 in advance. The key to success here is to find the right explanation, wording and reasoning for what you ask for. Because only then the client will realize that an upfront payment might make more sense for the project.
  • We all know the situation when our to-do lists are too big to handle on time. Overloading your list is the worst you can do. Here are some tips and tricks on simplifying your tasks19 so that you don’t get overwhelmed.

Go beyond… Link

And with that I’ll close for this week. If you like what I write each week, please support me with a donation21 or share this resource with other people. You can learn more about the costs of the project here22. It’s available via E-Mail, RSS and online.

Thanks and all the best,

Anselm

Footnotes Link

  1. 1 https://letsencrypt.org/2015/10/19/lets-encrypt-is-trusted.html
  2. 2 https://twitter.com/jaffathecake/status/656034298148048896
  3. 3 https://ma.ttias.be/firefox-nightly-starts-marking-login-forms-in-http-as-insecure/
  4. 4 https://twitter.com/rlbarnes/status/656554266744586240
  5. 5 http://liminality.xyz/the-hostile-email-landscape/
  6. 6 https://ponyfoo.com/articles/designing-front-end-components
  7. 7 https://remysharp.com/2015/10/14/the-art-of-debugging
  8. 8 https://www.npmjs.com/package/npm-run-all
  9. 9 https://www.npmjs.com/package/parallelshell
  10. 10 http://meyerweb.com/eric/thoughts/2015/10/22/firefoxs-screenshot-command/
  11. 11 http://androidvulnerabilities.org/press/2015-10-08
  12. 12 https://code.google.com/p/chromium/issues/detail?id=468044
  13. 13 http://nolanlawson.com/2015/10/19/the-struggles-of-publishing-a-javascript-library/
  14. 14 https://css-tricks.com/reverse-text-color-mix-blend-mode/
  15. 15 https://wiki.csswg.org/ideas/mistakes
  16. 16 http://meowni.ca/posts/a-story-about-input/
  17. 17 http://www.tomango.co.uk/thinks/using-quantity-queries-to-write-content-aware-css/
  18. 18 https://expensiveproblem.com/100-percent-up-front
  19. 19 http://zenhabits.stfi.re/overloaded/?sf=azaywb
  20. 20 https://brooksreview.net/2015/10/death-to-analytics/
  21. 21 https://wdrl.info/donate
  22. 22 https://wdrl.info/costs/
(Visited 1 times, 1 visits today)