Edition 308 by Anselm Hannemann

Hey,

when I wrote the last summary right before the calm time between years, I thought the next edition will not feature a lot of articles. Since then, so many cool new notes and articles have been published that it’s about time to send this to you.

Personally, I’m working on two web projects at the moment with one being built from scratch with modern technologies and the other one being a quite tricky carry-all-components-over job from custom web components back to a theme library due to massive problems with the existing solution. In both projects the code I produce is nearly secondary and it’s more important to think about the issues in an abstract and unconventional ways, to make the right decisions for the software service, and maybe even more importantly, for the team. But on the other hand, I realized again that my CSS skills are the ones that usually make the difference in the teams where most frontend engineers are great at writing JavaScript/TypeScript. Therefore it fits well that this edition shares so many nice little tricks on CSS. Maybe it’s a good idea to read one of the CSS articles each day to get a bit up to date with modern CSS again.

News

Generic

  • As engineers, it can be really satisfying for us to implement clever, terse solutions to problems, relying on advanced tricks and techniques. As a result, we often write code that is hostile and inaccessible to the junior folks on our team. But now Josh W. Comeau makes the case that we should strive to write simple, accessible code, using the dumb old primitives that everyone knows. This is one of my favorite advices to developers: Build robust and straight-forward code without cleverness. And if you must use clever techniques, ensure it’s documented well.

UI/UX

Tooling

Security

Web Performance

HTML & SVG

JavaScript

CSS

Work & Life

  • We tend to please all the people as freelancers, as business owners, as responsible employees. But we forget that this mindset is a faulty one as we’re not able to be more than one person. As developer I’d call it a one-to-many relationship and it works one way pretty well but not back-and-forth with the same performance. Here’s a minimalist’s business philosophy: Closed when I have enough.

Go beyond…

  • By Leo Babauta: I’ve seen a lot of people with goals about changing how they spend their time, things like: These are wonderful goals. They all involve something that theoretically is pretty simple: simply change how you spend your time. But it’s rarely that simple, is it?

If you liked it, please contribute any custom amount here. Thank you!

Anselm


Source link

مدونة تقنية تركز على نصائح التدوين ، وتحسين محركات البحث ، ووسائل التواصل الاجتماعي ، وأدوات الهاتف المحمول ، ونصائح الكمبيوتر ، وأدلة إرشادية ونصائح عامة ونصائح