11–20 of 30 posts
I don't mind when someone advertises their product through a good article, but this was way too condescending.
The title is also click bait as in he only occasionally writes extremely basic static websites for his own products.
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.
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.
If you add the backend skills above to the original post... It's what a full-stack developer originally was, and in my mind still is.
These folks can imagine a bug, features and architecture from different breadths and depths.
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…
I am interested in learning this style but keep getting drawn into some frameworks. What order would you recommend learning to create sites in this style?
1. Write semantic HTML in a sane, human-centric order. Do not write any CSS yet.
2. Open your new web page in a browser. Imagine CSS doesn’t exist and you’re stuck with whatever the browser gives you forever (shudder). Is your site well-organized? Is it easy to read, to navigate? Are the most important elements on your page afforded the appropriate level of prominence?
3. Imagine everyone looking at your website reads every line of HTML top to bottom. You’re not allowed to use classes or IDs. Do your readers know what, say, the title of your blog article is? Do they know where the navigation is?
4. Do you have multiple page “types” (e.g., blog post, blog index, about me, home page)? Do this for all of those types. Don’t forget to keep making your HTML semantic. Copy and paste similar bits (navigation, etc.) from pages you’ve already created. Yes, if you make changes to one, you will have to change both.
5. Once you’ve done all of these, put a tag linking to a single vanilla CSS file in the header of your simplest page. Start adding styles, beginning with text styling. Can you still tell that links are links? Is it still easy to find the navigation? Do headers look like headers? Good.
6. Did you have to pollute your HTML with a lot of classes to accomplish what you wanted to accomplish, design-wise? This might be OK, but you probably added too many. Can you accomplish the same thing using semantic elements instead? Do so.
7. Copy that tag to the other pages. Do they look pretty decent? They should. Add whatever additional styles those pages NEED.
8. Yes, it does suck having to copy and paste all these repeated blocks all over the place. Find a static site generator or use something like CodeKit[1] so you can use simple includes rather than configuring the mess that is most static site generators. I use a static site generator for my site[2] for fun but don't really need one.
Have fun.
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…
I am interested in learning this style but keep getting drawn into some frameworks. What order would you recommend learning to create sites in this style?
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.
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…
I am planning to add a blog to this landing portal and debating whether I should have comments on it or not. Because if I’ll have comments I’ll have to deal with complicated libraries and add-ons.
Maybe I’ll just have static HTML files linked from YYYY/mm folders as my blog posts and maybe some simple JS for next/previous if at all (in that case I’d want to name individual post files with some discipline so that I can parse it easily later)
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…
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 used to do that, still do once in a while, but I find Ansible to be much better for provisioning and configuring things. I rarely use modules that are not part of the base install; in fact at present I am not using any that aren't standard. I feel my playbooks are simplistic compared to what I see others doing, but they work for me. The idempotency and error checking that Ansible provides are well beyond what I feel is worth rolling by hand, so it's a good tradeoff. I can still write simple things that I understand.
Earlier quoted context omitted.
I am interested in learning this style but keep getting drawn into some frameworks. What order would you recommend learning to create sites in this style?
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.