Live data from Hacker News

It’s 2019 and I Still Make Websites with My Bare Hands

medium.com

21–30 of 30 posts

Re: It’s 2019 and I Still Make Websites with My Bare Hands

#21
post #15

Earlier quoted context omitted.

I can think of two approaches: 1. Get a better idea of the tools already at your disposal (HTML5, CSS3). I can recommend Dive into HTML5 http://diveinto.html5doctor.com 2. Start building. Literally, start with the barebones Hello World given in the article. Then gradually turn it into your site, making liberal use of Stack Overflow (direct search) and Google.

Thanks for the link. This whole thread is refreshing. I am someone who does not do web development for a living but occasionally builds a website. Every time I start building a new site I am at a complete loss where to start. Yet I have been doing HTML and CSS since 1999. I am going back to basics, starting with your link.

Open web inspector when you develop a website. You can get a better feel for how changing CSS on the fly take place on the actual webpage.

I would save a copy of the HTML from the top level comment of this thread and use it as a base to start any new project.

I like to start from scratch and add Bootstrap should I need responsiveness once I get to that point. L

Re: It’s 2019 and I Still Make Websites with My Bare Hands

#22
post #21

Earlier quoted context omitted.

Thanks for the link. This whole thread is refreshing. I am someone who does not do web development for a living but occasionally builds a website. Every time I start building a new site I am at a complete loss where to start. Yet I have been doing HTML and CSS since 1999. I am going back to basics, starting with your link.

Open web inspector when you develop a website. You can get a better feel for how changing CSS on the fly take place on the actual webpage. I would save a copy of the HTML from the top level comment of this thread and use it as a base to start any new project. I like to start from scratch and add Bootstrap should I need responsiveness once I get to that point. L

Thanks for the tips.

Re: It’s 2019 and I Still Make Websites with My Bare Hands

#23

Is anyone else the backend version of this? Instead of using Docker, Kubernetes, AWS, etc. write your own bash scripts to provision servers, deploy code, etc. Instead of using fancy monitoring frameworks, just have a cron job that SSH into all your servers, and send an email if disk or memory usage spikes too high.

I could say I am, except that I just use plain sh running under openbsd instead. Not only for web stuff, but I also use simple unix tools a lot to process data - a lot simpler and most of the time it's even faster than using SQL or so-called "big-data" tools.

Re: It’s 2019 and I Still Make Websites with My Bare Hands

#24
post #4

I’m not even kidding, this is how I still make websites: I open a text editor, and stub this out (by hand, it only takes like 30 seconds — I’ll even do it as I write this post to be authentic — except stinkin’ tab doesn’t work here): I code stuff with my bare hands Hi there Then I open a new tab and make a CSS file; something like this: * { margin: 0; padding: 0; box-sizing: border-box; } body { font-size: 18px; colo…

Do you find * { box-sizing: border box } to be necessary? I don’t know why people need to set it for everything when it only makes a difference in a specific situation.

Re: It’s 2019 and I Still Make Websites with My Bare Hands

#25
post #4

I’m not even kidding, this is how I still make websites: I open a text editor, and stub this out (by hand, it only takes like 30 seconds — I’ll even do it as I write this post to be authentic — except stinkin’ tab doesn’t work here): I code stuff with my bare hands Hi there Then I open a new tab and make a CSS file; something like this: * { margin: 0; padding: 0; box-sizing: border-box; } body { font-size: 18px; colo…

Do you find * { box-sizing: border box } to be necessary? I don’t know why people need to set it for everything when it only makes a difference in a specific situation.

Less manual math when figuring out the true size of an element with margin, border, padding, and sizing applied.

Re: It’s 2019 and I Still Make Websites with My Bare Hands

#26
I used to make websites likewise (html boilerplate, css links and script tags at the bottom of body). I liked the no frills simplicity of it. But years ago I switched to using frameworks and don't think I would go back. Yes I could implement my sites in vanilla js and frankly it would be fun! But I would spend too much time reinventing the structure I get ootb with frameworks.

Re: It’s 2019 and I Still Make Websites with My Bare Hands

#28

Is anyone else the backend version of this? Instead of using Docker, Kubernetes, AWS, etc. write your own bash scripts to provision servers, deploy code, etc. Instead of using fancy monitoring frameworks, just have a cron job that SSH into all your servers, and send an email if disk or memory usage spikes too high.

Yes, I'm also like that with backend development. I write simple Go programs and bash scripts to provision all my infrastructure. Love it.

Re: It’s 2019 and I Still Make Websites with My Bare Hands

#29
post #9

Erh, I did the same for small personal websites but maintaining the content and having to change things on multiple pages made me switch to a build step. I do not understand how the author would deliver a website to clients without pulling in content from a (headless) CMS.

Sometimes you gotta do that. The Caddy blog is run with Hugo after every git push.

Re: It’s 2019 and I Still Make Websites with My Bare Hands

#30
post #3

I prefer the workflow that the author does, minus the Jquery just so I can maintain some street cred. document.querySelector solved 90% of what jquery solved for me anyhow. For consulting clients, I've done plenty of what I consider the "exotic workflows". My determination is that the primary benefits of react, angular, et al is that they organically create hierarchies among a group of multiple developers. It also cr…

"depersonalization" and "walls" is one way to put it. Though think of it from another perspective: You'd need to keep a team pulling in the same direction and speak a common language. When one person coded up something without any framework, they may understand the code structure perfectly, but the others who collaborate with them can easily get lost/be detoured. Publicly existing frameworks have conventions, docs and communities and a certain way of organizing things, which makes it much easier for a team to avoid wasted efforts.
Post reply on HN