Lumberjack coffee programmer

I always enjoy looking into what other people are doing with their smaller (but 100+ views) websites, thanks for posting.

Usually “this is a good website” websites are pretty text-heavy with the occasional picture. These sites only need HTML anyway and frequently say “you only need HTML anyway”.
Although the linked webpage – a debatable list of opinions (e.g. Cloudflare privacy is hotly contested by people with at least as much credibility as the author) – is an example of this, I was pleasantly surprised by the national grid map under /data and the use of math rendering, which at least surpass the complexity of writing a HTML 1.1 compliant site.

The use of CC0 is a variable choice – some want their work to be more forcibly public, but I guess I see her viewpoint.

As for her gripe on the opacity of code minification, I can’t say I understand that. Just make your site source code open and obvious to remake, as she did with grid. It’s the same result, but with the added benefit of less JS bytes for when you do do something more complex.

Cool I guess. Dark mode is broken on darkreader on this site tho.

I don’t know why you were downvoted, but without being judgmental, you remind me of a certain someone when they were starting out on the ropes ;)

If I had to surmise, you’re young and unsure of your skills. What should I do? I used to think. Is there a canon I should be following? I feel inefficient, like I code too long! Maybe I should use this language instead?

And then I just gave up on tutorials and books and all that, and just bit down on… solving problems that I “made up”. And I don’t mean HackerRank whiteboard problems or turning buttons blue.

• I had 50 million bookmarks – I made a Python tree view to comb through it all.
• I wanted to share pirated books with my old phone – I made a teeny Python server (thanks, docs!).
• I wanted to argue with my math teacher – I made a Python stats sim. (I was wrong.)
• Installed Linux on my spare dino computer. (LMAO Lemmy moment. But seriously there’s so many problems to invent and solve – after some time, Linux is playing on easy mode)

My pets never got past 500 lines of code. But when little me saw I wrote 500 with my own sweat and tears and StackOverflow army, I beamed – and it was very beam-worthy.

Don’t fall into tutorial hell. Know the basic eight or ten things (how to store values, how to store procedures, how to store groups of each, how to interact with user/net/system) – and try to grab a real something, not easy but not too hard, and with fun before the work. Don’t belittle yourself. Find a rewarding fun both during and after the play – is it automation? a cutesy thing? It needs to pay to keep you playing.

Hell, try using a whole Astro blog, or a C game that you can WASD in. Languages are just tools for jobs – it’s not how many you know but how well you know one. Because once you know one…

If you even read this, downvote iff this was patronizing or totally wrong. I don’t know why I got this impulse.