You got to love that alignment, it's ok though, imagine if they wrote a whole framework... Ohh wait...

TABLE BASED WEB DESIGN

I was surprised there were no rants about this topic before I realized it was more than a decade back 😳

We've never had it better! So to help add a little perspective for all those ranting about what is unarguably the golden age for web developers... let me fill you in on web dev in the late 90's;

JavaScript was a joke. No seriously! - I once got laughed out of the room for suggesting we try use it for more than disabling a button - (I wanted to check out the new XHR request thingy [read AJAX]).

HTML was simple and purely a markup language (with the exception of the marquee tag). The tags were basically just p,ul,ol,h*,form inputs,img and table and html took 10 minutes to learn. Any style was inline and equally crude - anything that wasn't crude could not be trusted and probably wouldn't render at all in most browsers (never mind render correctly).

There were rumors of a style TAG and something called a cascading style sheet which were received with much skepticism since it went against the old ways and any time saved would be lost writing multiple [IE version specific] style sheets for each browser just to get it to work - so we simply didn't.

No CSS meant the only tags you had to work with to create a structured layout were br, hr and table... so naturally EVERYTHING was in nested tables! JS callback hell can't touch this! - it was not uncommon to have 50+ nested tables all with inline style in a single page which would be edited without any dev tools or linting.

You would spend 30 minutes scanning td tags until your eyes bled to find something, make a change, ftp the file to the server, reload the web page and then spend 10 minutes staring at the devastation on your screen convinced you broke
the internet before spotting an un-closed td tag with your bloodshot eyes.

Tables were not just a silver bullet - they were the ONLY bullet and were in the wild west!

Q: Want an inline form or to align your inputs left?
A: Duh table!

Q: Want a border with round-corners, a shadow or blur?
A: That's easy! Your gonna want to put that table in the center cell of another table then crop a image of the border into 6 smaller images to put in the surrounding cells... oh and then spend 10 minutes fucking with mystical attributes like cell-padding and valign to get them flush.

...But hey at least on the bright-side vertically & horizontally centering stuff was a breeze!

Just before you, my fellow system programmer, scroll past this, let me say this:

🍬 The web is actiually simple. 🍬

Both HTML and CSS is declarative. It's all easy when you understand the concepts, learn how to be idiomatic and quit trying to do that imperative bullshit in languages that aren't imperative.

HTML is simple. You know the boilerplate: doctype, head, body, that's all. Just mark it up and do NOT look at it before you end, mark it up as it were article or something. The appearance is up to css.

CSS is simple. You may even forget bem or rscss, you're already a skilled software developer. Use common sense and your code-splitting and naming skills you gained reading The Code Complete or doing software development for years.

Forget mockups. Forget absolute positioning, forget setting width and height in pixels. Go to awwwards, find some inspiration. Draw some buttons and fields on paper with your good old pencil. Then go and write some css. Feel free to steal some shadows and transitions from codepen.

Read about 8-pixel grid system. Let every element push away from others by setting something like margin: 16px; and whoops! You've just got fully responsive and got great vertical rhythm without even using media queries!

Oh my god, do NEVER set width and height explicitly! Type something like button { width: 120px; } and bang! The entire web page is broken. Quit that shit. Let it resize as it should. It will resize itself to fit its contents.

HTML is by default ready for your template engine. That's how you receive data from server — as server-side rendered, plain old HTML page. On the other hand, the form element is the most axiomatic and simple way to send the data to server. That's how you send it — as plain old GET or POST that every webserver can handle.

All of there are true:
1. It's easy to get great 100% responsiveness without media queries.
2. It's easy to align items in row, it's just one line of css. Maybe two, if you still want elements to wrap, but want to use flexbox:
.parent {
display: flex;
flex-wrap: wrap;
}
3. HTML and CSS are fast by default.
4. You don't need mockups to achieve great visual experience. Mockups is imperative, web is declarative.
5. You may not even need JavaScript to make great website.

Go on, ask me a question about web! I'll ready to answer everything.

tldr: Fuck Adobe Premiere

What the flying fuck.
I have a school project together with a friend and decided to do a video. Not only do we now only have one fucking day left, because the teacher decided we dont need time or anything, but I have to learn video editing software, record clips and create the video withing one fucking day.
I've downloaded Premiere because I have a 7 day trial left and had Creative Cloud on my PC and WHAT THE FUCK kind of fucked up bullshit software is this human compiled piece of shit?! I needed to google how to add text and edit it because adding text gives you absolutely nothing, you get no possibility to edit the text in any way, except the content. After googling for 10 minutes because I have the newest version and they changed the text tool, I found out that you need to go to another tab... of which there is 7 and all have such telling names like: "Effects" and "Compose"...
I needed to go to "Effects" BECAUSE WHY THE FUCK NOT, TEXT SURE LOOKS LIKE AN EFFECT TO ME! Then I wanted to align it to the right so its on 50% of the screen. You fucking cant, I've tried and looked for an hour the only possibility you have is to align it to the center or just throw it somewhere. The snapping didn't even work correctly. So I tried to do something else because I was ready to punch a kitten.
A box. A box thats black. A box thats black and thats aligned to the... FUCK YOU, YOU CANT ALIGN THIS BOX.

I cant align a box...
They dont even give me the possibility to...
But I can align the text BOX, not even the FUCKING TEXT itself...

What
The
Fuck

This is the worst program I've EVER had to use. I'm fucking mad and this fucking project can FUCK ITSELF.

So, I'm about to be up shit's Creek. I need a new source of income, ideally either a new job or becoming a freelancer. I have been making intranet sites with ASP.NET for a while now, and I can tell two things:
1. It's too corporate minded, so I'll need a fucking degree
2. It's too corporate minded, so I'll be stuck with people like my boss, who still use tables to align content despite the project having bootstrap.

I need to do something more fulfilling, but I probably will have to leave my job by December anyway due to some major fuck ups in my life, do I need to get something lined up. I have been brushing up on my HTML, CSS, and JavaScript skills, but when it comes down to it, I suck at design so my "portfolio" is blatant clones to learn CSS and shitty Spartan things.

Basically, I'm anxious, terrified, and unable to figure out what comes next. Do I keep sending job applications and praying to whatever deity will listen, it do I start figuring out this freelance thing? If freelance, then how do I get into it? I'm terrified and desperate.

at one point documents were useful things to align people to the relevant information to the tasks they must complete for everything to work out

now documents are a ritual, and relevant information is even forgotten or omitted and considered secondary to the document existing and looking like a professional document

I wonder if this is how all industries evolve
at one point there were people who knew what they were doing, they created processes so nobody is left behind
and over time, whoever made the processes, the spirit for their existence, is forgotten
and you're left with empty rituals, so devoid of their original function, the humans subjected to these things, crushed by them, can't even discern what their usage is

evidently if you put monkeys in an enclosure with some apples up a tree with a mechanism that if a monkey goes up the tree and takes an apple it sprays all the other monkeys in the enclosure with water
the monkeys will learn to pull down any monkey trying to go up the tree, because they don't wanna get sprayed
and this will keep going, generations will change and yet they'll still religiously pull down the monkeys, in a ritual... nobody remembers why only that their parents did this to them, so they do it to others
if you take the trap away, they never figure it out, which is how this story is typically told
but regardless of if the trap is there or not
wouldn't you wanna know and see it for yourself instead of following empty rituals?!

and what of people who erroneously view things as traps, and pull people down, but they were just seeing things?!
self limiting myths to doom the ages!

Learn enough math to solve the problem Chat GPT (and two university math professors) have been unable to solve :(

The hardware is ready, the software is ready, and the only missing piece is to align a laser pointer with a Lambert's conformal conic projected map... I thought Chat GPT would be able to at least provide me with the necessary formulæ, but not...

You work in a team, for a team to move forward successfully the team should work in sync. A team always has a goal and a plan to get to it. There are times when the team needs to take a different direction therefore the set path should always be available for change because our environments dictate it.

We all have different styles of working and different opinions on how things should work. Sometimes one is wrong and the other is right, and sometimes both are wrong, or actually sometimes both are right. However, at the end of it all, the next step is a decision for the team, not an individual, and moving forward means doing it together. #KickAssTeam

The end result can not come in at the beginning but only at the end of an implementation and sometimes if you’re lucky, during implementation you can smell the shit before it hits the fan. So as humans, we will make mistakes at times by using the wrong decisions and when this happens, a strong team will pull things in the right direction quickly and together. #KickAssTeam

Having a team of different opinions does not mean not being able to work together. It actually means a strong team! #kickAssTeam However the challenging part means it can be a challenge. This calls for having processes in place that will allow the team members to be heard and for new knowledge to take lead. This space requires discipline in listening and interrogating opinions without attachment to ideas and always knowing that YOUR opinion is a suggestion, not a solution. Until it is taken on by the team. #KickAssTeam We all love our own thinking. However, learning to re-learn or change opinions when faced with new information should become as easy to take in and use.

Now, I am no expert at this however through my years of development I find this strategy to work in a team of developers. It’s a few questions you ask yourself before every commit, When faced with working in a new team and possibly as a suggestion when trying to align other team members with the team.

The point of this article, the questions to self!

Am I following the formatting standard set?

Is what I have written in line with official documentation?

Is what I am committing a technical conversion of the business requirement?

Have I duplicated functionality the framework already offers?

I have introduced a methodology, library, heavily reusable component to the system, have you had a discussion with the team before implementing?

Are your methods and functions truly responsible for 1 thing?

Will someone you will never get to talk to or your future self have documentation of your work?
Either via point number 2, domain-specific, or business requirements documentation.

Are you future thinking too much in your solution?

Will future proof have a great chance of complicating the current use case?

Remember, you can never write perfect code that cures every future problem, but what you can do perfectly is serve the current business problem you are facing and after doing that for decades, you would have had a perfect line of development success.