rident

I watched a lot of old Time Team episodes lately and this looks like more of the same from the era. Really nice, complex looking work but overall what can be expected for the time period. Cool that it's so well preserved though and hasn't suffered from having a plow or seismic event turn it into a puzzle.

Classics right there! We've got a long linage of this kinda stuff now from browser resets to full stylesheets to well specified content just for testing any of the above on. I love it! Simple. Consistent. And now more powerful than ever with the help of variables.

Might be fun to take all the w3 core styles rebuild them with modern CSS features. Maybe add some HTML5 elements to the test docs as well.

They don't get gore in my house like a snap trap does yet fit in the same places where a catch-and-release trap would not. The mouse still lives and I get maybe two of them a year, in the fall as the temps cool. I really don't think it's a big deal.

Who leaves a mouse on a glue trap until it dies? That's messed up! I can hear when a mouse is on those things and at that point I carry the frightened mouse outside, pour a cap full of vegetable oil around it's feet and it frees itself, running off into the yard, then the trap goes in the trash. Heinously cruel? Only if you're a lazy shit.

Yeah this is a great way to tackle it. Image and branding comes along for the ride. Even if it's your desire - the client's desire is typically going to be functionality, security, usability, accessibility, etc. All of which are a means to an end for a lone wolf designer/engineer. Listen and learn from them about their pain points before promoting your own skills or favorite parts of the industry.

It would be cool to see a reboot of Firefox OS with Rust and WASM some day.

There's a Lockheed A-12 on the USS Intrepid that you can get very close to with a guided tour. One of the facts the tour guides tell you about it is the titanium for the planes, as well as that of the SR-71s, was mostly sourced from Russia via shell companies for all kinds of bullshit reasons. So, America flew spy planes over Russia that were made from materials mostly of Russian origin.

The article says wraps up by stating the design hasn't lost any information but where's the fork count, watch count and other download options? Also, the lack of borders and flattening of button styles does not improve the design. Borders are even more necessary when data density is increased. Buttons, menus and links now have a variety of borders where they were consistent before.

The menu is marginally better but the extra density there makes the options run together, especially as counts increase, and lacks room for feature expansion. The grey background is useful also as it gives the page sections depth and context without having to label it. A all white background with various text sizes and lengths is not optimal for supporting more than the example design and projects using more text or with longer titles will suffer.

This design doesn't take into consideration how the homepage of a repo relates to the subpages of a repo. The article mentions showing more files yet the in the current design, file view one click away from the current homepage removes most of the account meta data and shows more files already.

This design also doesn't consider the logged out view which has a large call to action banner to get an account strategically embedded at the top of the code tab. This focal point is somewhat lost in the presented redesign and would likely require rounds of A/B testing to decide on a new content breakpoint for this business need.

5/10 - needs work

I think Wisconsin and North Dakota also have this system.