181–190 of 547 posts
7 years old? Don't force kids If you need your kid to be kid. Hand coding HTML is just trash than collecting leaves & beautify the kindergarden book. I've no memory for last 10+ years other than computer and programming. All I've pretty beautiful memory from childhood.
I was significantly older when I built my first website (19, in 1996) but I'm so glad I had a space to pretty easily put up basic HTML (Geocities, though there were similar options). No WYSIWYG, no build steps, just the basic text-only HTML which created a foundation to build on. It's unfortunate there aren't really good options for that for today's younger creators. (is there?)
Earlier quoted context omitted.
Don’t 7 year olds deserve to learn how to improve too? The comment doesn’t appear to be done aggressively or in bad faith, so what’s the issue? Presumably it will be the parent who’ll read the comment, and they can pass it on or not depending on what they think the kid would prefer and/or would let them grow. Ironically, I find the most HN comments of all to be the ones who complain about something being too HN. Whic…
Unsolicited critique is almost always unwelcome critique, in my experience. Especially where someone else's 7 year old is concerned.
The communicator does have responsibility on how their message comes across, thought not all of it. It’s on the receiver to also make an effort to understand what was meant and not take unnecessary offence. The comment reads pretty much neutral, apart from a post scriptum which is explicitly about the author’s preference. It’s up to you to inject the writer’s feelings as either “this code sucks, here’s how you do it” or “congratulations on making something cool, here are a few suggestions”.
My experience is that life is much better if you take the latter approach. Default to empathy.
Consider listening to “This is Water” from David From Wallace.
Some issues she can improve on: - H1 content is too long, it should be less than 60 characters, use for the rest of secondary content - There should be only exactly 1 H1 per page
I hope the “/s” was implied. I thought about making a similar post, in the true spirit of a “Show HN”, but would have included the “/s”.
Earlier quoted context omitted.
Totally agree with you. Not a front end dev myself, and I have multiple variations of "how do i center a div" in my search history, haha. With varying degrees of angry expletives added to the query.
Kids these days don’t know how easy they have it with flexbox!
Keep it up, you're doing great! :)
Very cute! I did something similar with my dad when I was a kid. First basic HTML then Dreamweaver. A couple years down the road and I’m working at a SaaS company. Beware.
Me too. First framesets, handcrafted. Then Dreamweaver and Photoshop slicing (forgot what this monstrosity was called). Via PHP portals, CMSes (Drupal!). Decades later I'm tuning YAML files that trigger ansible runs on CIs that compile docker images in which we embed hundreds of npm packages that get transpiled from typescript. Which gets released to cloud serverless edge thingies that store stuff in a database and o…
Seriously, I think about this quite often. I recently found some old code that I wrote in the early 00s and it was wonderfully simple, and aside from a few visual trends that have changed, it looks pretty damn good. Straightforward layout, good information density, and very clean. The best part is the code is vastly simpler than anything I've seen/built in the last couple of decades (especially since CSS, packers/transpilers, etc started arriving). I grant that there are some good reasons to introduce CSS and divs and all that, and that once we've done that it is inconsistent to have some things done in html and others in css, but sometimes philosophically better isn't better in practice. Sometimes.