Lea Verou

>I (maybe I am wrong) have been intending to treat team-members as "some dudes with bumps on their chest that may have various after hours habits that are none of my concern".

FWIW, this is personally my ideal working environment. I can't speak for women in general, and I'm not a moral authority, but this is exactly the kind of treatment I want from my coworkers.

>what should I do to be better?

I don't know, honestly. I know that's an inadequate response, but I'm not sure how to appropriately address ingrained societal sexism either. As far as subconscious bias in hiring goes, having rubrics and standardized interviews goes a long way at eliminating it. I'd theorize that standardized metrics for performance reviews would help on that front, too, though I don't think that's been studied.

If you browse the million and one women in tech posts out there you can see people talking about it at length, though I would be wary of taking somebody's opinion as truth just because they're female, and I would be doubly wary of taking a tech blogger at her word vs an actual female engineer. Your personal set of ethics re: equality of opportunity vs outcome also plays into what you "should do" quite a lot. Some suggestions (like formalized hiring rubrics) are completely valid whether or not you believe in equality of opportunity vs outcome, but others (like instituting diversity quotas in hiring) are not.

This blog post is well cited and worth a read, it has a few good suggestions IMO:…

95% of the more complex errors I've seen* in CSS have been some combination of a misunderstanding of positioning (https://developer.mozilla.org/en-US/docs/Web/CSS/position) and the box model (https://developer.mozilla.org/en-US/docs/Web/CSS/box_model). The other 5% of relatively complex display errors are actually due to unfortunate choices when writing the HTML.

I think once you understand those, the rest is really quite simple. Media queries, clever nonsense with things like ":target" or ":not([class]) > div > img", it's all ultra-simple because there are no logic bugs you can introduce once you know the syntax – the only logic you need to think about is in the positioning of elements on the page.

As a backend web developer, you will find it all very simple. A bit of bloody-minded Googling will solve the majority of your problems, and the CSS answers on StackOverflow are more helpful & polite than they are in many other areas.

For HTML, some features I have found useful include definition lists, dfn, nav, header, section and article elements. It may also be useful to check out Schema.org.

So I guess my recommendation is to get the box model and positioning down pat for CSS, and get semantic elements down for HTML5.

If you like genuinely clever and awesome tricks, check out Lea Verou (http://lea.verou.me/).

*"seen" as in "made myself"

Small suggestions (just based on the website copy): consider supporting other colour spaces, like Display-P3, DCI-P3, Adobe RGB, CIE... not sure what the source data from the camera can tell you though. LCH color picking based on CIE might also be useful http://lea.verou.me/2020/04/lch-colors-in-css-what-why-and-how/

It’s worth pointing out that Pantone generally only matches print colours, and labels digital representations seemingly exclusively in sRGB, not wider colour spaces. https://www.pantone.com/color-intelligence/articles/technical/what-are-your-color-spaces for the sRGB chart. Here’s an example exception: https://www.nanosysinc.com/blog/2012/12/11/color-of-the-year-for-2013-falls-outside-srgb-gamut Despite this, it has an sRGB hex value, so I’m not sure what to make of it. https://www.pantone.com/color-finder/17-5641-TCX It seems odd that Pantone lists these color values without listing absolute or relative values by named color space...

This is nice. I didn't try but to get a pseudo-random variation of the book height, will it be possible to do a pre-defined Cicada Principle[1] method, say, pick 20-30 heights and keep picking them up.

There seem to be quite a lot of people who have their own book collection. I'm still looking for something simple that can spit out a HTML front; and yet to find something I like.

On another note, recently I was looking for a Library Management System for a small community, with a current book collection of over 25,000. I looked a bunch of Open Source Solutions (most are too complex). I also do not want to do build anything from scratch.

I settled on Libib[2] and the subscription is economical enough for what we are looking for.

1. https://lea.verou.me/2020/07/the-cicada-principle-revisited-with-css-variables/

2. https://www.libib.com

This seems like a good opportunity to bring up the old, more hacky, but also more performant and predictable CSS random effect using backgrounds of prime number sizes to achieve a "random" distribution. The "cicada principle"

https://www.sitepoint.com/the-cicada-principle-and-why-it-matters-to-web-designers/

https://lea.verou.me/blog/2020/07/the-cicada-principle-revisited-with-css-variables/

In this case you would use multiple transparent tiles of different star patterns (images, or gradient/clip-path tricks), each one a different prime number in size. It should work with anything you can tile and overlay in CSS though.

This seems to be a pretty low-effort post without any real substantive details.

I'd much rather see discussion of the "Parallel Evolution of React and Web Components" article that got posted earlier today. I don't agree with that author's strong stance against React, but it's at least a well-written post with substantial thought and significant technical detail:

- https://news.ycombinator.com/item?id=41790499

or these other relevant posts:

- https://nolanlawson.com/2024/09/28/web-components-are-okay/

- https://lea.verou.me/blog/2024/wcs-vs-frameworks/

- https://mastodon.social/@molily/113215236512572084