The programmer and the interns part 3.

Many of you asked me to keep posting about the interns that I'm responsible for.

I had the intention but never had the time or the energy. Since the interns only kept doing stupid, unthinkable things and just filtering out the good ones is a task of its own.

Time has passed, some interns left us by their choice, others were fired (for obvious reasons). Some stayed loyal and were given permanent positions. New ones joined. I no longer am directly responsible for their wellbeing, yet, somehow I am still their tech-lead and the developer of their tools.

Without further delay,

Case 0:
New guy get's into the internship, has his LinkedIn title set to ‘HTML Technician’.
Didn’t know about the existence of HTML5.
Been building static web pages in the early 2000s. The kind with embedded, inline CSS.
Claims that he is about to finish an engineering degree (sadly I believe him).
Fails the entry level Linux test. Complains about the similarity of the answer options.
Fails the basic web-standars test because "they change so fast, but the foundation is HTML and it's rock-solid!".
Get's caught taking home onions and milk from the kitchen.
Is spotted eating in a restaurant under our offices in his day off. Thrice. He lives a 30 minute drive away and comes here on a bicycle or by bus.
Apparently didn't know that the scrolling wheel on the mouse is clickable.
Said that his PC experience is mostly from his PlayStation (PC = PlayCtation apparently).
Get's fired, says that he'll go to the press. Never does.

Case 1:
Yet another new intern. He seems very eager to learn and work, capable, even charismatic. Has an impressive CV.
Does nothing.
Learns from the "case 0" guy and spends time with him until he is fired.
Comes to work at 8:00 AM and immediately goes to sleep on an office puff. In front of everyone.
Keeps dining alone, without a notice, at different times, for hours. Sometimes brings food into the office and loudly eats it there.
On his evening shifts keeps disappearing for long periods of time. Apparently drinking in the nearby bars and hitting on girls.
Keeps bragging about his success with getting their numbers and rants about those who reject him.
For over a year he fails his final training test and remains a trainee, without the ability to work on a real case.
Not fired yet.

Case 2:
Company retreat. Beautiful, exotic views, warm sun beams, all inclusive package for everyone on a huge half-island.
Simon (he's still with us, now as a true engineer!) brings his MacBook to the beach in order to work and impress all others.
Everybody get's drunk and start throwing huge inflatable balls at each other. One hits his laptop and it immediately is flattened.
Upset Simon is going in circles and ranting about the situation, looking for a solution.
Loses his phone on the beach.
Takes his broken laptop with him while searching for the phone.
Dips the laptop in the river while drunkenly ducking in order to pick a clam.

Case 3:
Still company retreat.
Drunk intern makes out with an employee's drunk wife.
Huge verbal fight. The husband says that he files for a divorce. Intern get's fired.

Case 4:
Still company retreat.
Three interns each take an inflatable swimming mattress and drift with the current. Get found on the other side of the resort three hours later, with red skin and severely dehydrated.

Case 5:
Still company retreat.
The 'informally fired' intern gets drunk again, climbs through a window into a room and makes out with an employee's drunk wife.
Again, gets caught when the husband returns to find a locked door but can see them though the window.

Case 6:
Still company retreat.
We all get ferociously drunk and wander off to the unknown in search of more booze.
Everybody does something stupid and somebody finds Simon's phone.
Simon is lost.
Frenzied horde of drunks is roaming the half-island in search of ethanol and the lost comrade.
Simon's phone get's permanently lost.
Five people step on sea urchins but find that out only hours later and then are unable to walk.
The mob, now including more drunk people who joined voluntarily, finds the sexually active intern making out with the enraged employee's wife yet again.
Surprisingly Simon is found sleeping in a room nearby.

Hey @Root! I know you won't have time to finish Ticket A before holiday vacation, so work on Ticket B instead.

I finished Ticket A in time. except for converting/fixing some horrible spaghetti monstrosity. More or less: "we overwrote this gem's middleware and now it calls back into our codebase under specific circumstances, and then calls the gem again, which calls the middleware again." Wtf? It's an atrocity against rationality.

The second day after vacation:

Hey @Root, drop Ticket B and work on Ticket C instead. Can you knock this out quick, like before friday? ... Uh, sure. It looks easy.

Ticket C was not easy. Ticket C was a frontend CSS job to add a print button, and for unknown reasons, none of the styles apply during printing. The only code involved is adding a button with a single line of javascript: `window.print()`, so why give it to the chick who hasn't been given a frontend ticket in over a year? Why not give it to the frontend guy who does this all day every day? Because "do it anyway," that's why.

And in somewhere between 13 (now 5) minutes and two hours from now, I'm going to have a 1:1 with my boss to discuss the week. Having finished almost all of Ticket A won't matter because it's not a "recent priority" -- despite it being a priority before, and a lot of work. I've made no progress on Ticket B due to interruptions (and a total and complete lack of caring because I'm burned out and quite literally can no longer care), and no progress on ticket C because... it's all horribly broken and therefore not quick. I assigned it to Mr. Frontend, which I'll probably get chewed out for.

So, my 1:1 with bossmang today is going to be awful. And the worst part of all: I'm out of rum! Which means sobriety in the face of adversity! :<

but like, wtf. Just give me a ticket and let me work on it until it's done. Stop changing the damn priorities every other freaking day!

Be honest with yourself. If you hate CSS or think it's broken or whatever... you just don't know how to write it well.

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.

Microsoft Internet Explorer is my least favorite enterprise software. We are forced to use it. I hate being forced. This is like being asked to climb a mountain with a broken leg...not fun, painful, hopeless, threatening, discouraging, slow, and ugly, and infected...it is downright evil corporate bullshit.

<!--[if IE]>
<link rel="styleshit" type=trash/css" href="die-die-die-you-evil-bastard.css"/>
<![endif]-->

Just push it over the edge with a chrome sword stuck in its back. I will just sit here by the fire with my pet fox and watch the opera as I listen to vivaldi.

I'm editing the sidebar on one of our websites, and shuffling some entries. It involves moving some entries in/out of a dropdown and contextual sidebars, in/out of submenus, etc. It sounds a little tedious but overall pretty trivial, right?

This is day three.
I learned React+Redux from scratch (and rebuilt the latter for fun) in twice that long.

In my defense, I've been working on other tasks (see: Alerts), but mostly because I'd rather gouge my freaking eyes out than continue on this one.

Everything that could be wrong about this is. Everything that could be over-engineered is. Everything that could be written worse... can't, actually; it's awful.

Major grievances:
1) The sidebars (yes, there are several) are spread across a ridiculous number of folders. I stopped counting at 20.
2) Instead of icon fonts, this uses multiple images for entry states.
3) The image filenames don't match the menu entry names. at all. ("sb_gifts.png" -> orders); active filenames are e.g. "sb_giftsactive.png"
4) The actions don't match the menu entry names.
5) Menu state is handled within the root application controller, and doesn't use bools, but strings. (and these state flags never seem to get reset anywhere...)
6) These strings are used to construct the image filenames within the sidebar views/partials.
7) Sometimes access restrictions (employee, manager, etc.) are around the individual menu entries, sometimes they're around a partial include, meaning it's extremely difficult to determine which menu entries/sections/subsections are permission-locked without digging through everything.
8) Within different conditionals there are duplicate blocks markup, with duplicate includes, that end up render different partials/markup due to different state.
9) There are parent tags outside of includes, such as `<ul>#{render 'horrific-eye-stabbing'}</ul>`
10) The markup differs per location: sometimes it's a huge blob of non-semantic filthiness, sometimes it's a simple div+span. Example filth: section->p->a->(img,span) ... per menu entry.
11) In some places, the markup is broken, e.g. `<li><u>...</li></u>`
12) In other places, markup is used for layout adjustments, such as an single &nbsp; nested within several divs adorned with lots of styles/classes.
13) Per-device layouts are handled, not within separate views, but by conditionally enabling/disabling swaths of markup, e.g. (if is_cordova_session?).
14) `is_cordova_session` in particular is stored within a cookie that does not expire, and within your user session. disabling it is annoying and very non-obvious. It can get set whether or not you're using cordova.
15) There are virtually no stylesheets; almost everything is inline (but of course not actually everything), which makes for fun layout debugging.
16) Some of the markup (with inline styling, no less) is generated within a goddamn controller.
17) The markup does use css classes, but it's predominately not for actual styling: they're used to pick out elements within unit tests. An example class name: "hide-for-medium-down"; and no, I can't figure out what it means, even when looking at the tests that use it. There are no styles attached to that particular class.
18) The tests have not been updated for three years, and that last update was an rspec version bump.
19) Mixed tabs and spaces, with mixed indentation level (given spaces, it's sometimes 2, 4, 4, 5, or 6, and sometimes one of those levels consistently, plus an extra space thereafter.)
20) Intentional assignment within conditionals (`if var=possibly_nil_return_value()`)
21) hardcoded (and occasionally incorrect) values/urls.

... and last but not least:
22) Adding a new "menu sections unit" (I still haven't determined what the crap that means) requires changing two constants and writing a goddamn database migration.

I'm not even including minor annoyances like non-enclosed ternaries, poor naming conventions, commented out code, highly inefficient code, a 512-character regex (at least it's even, right?), etc.

just.

what the _fuck_

Who knew a sidebar could be so utterly convoluted?

Fucking evopdf, I spent 2 days trying to figure out why the fuck my js isn't rendering the html for printing. I created the structure in html already, and it's rendered perfectly with js DOM, when evopdf ran from backend it shows nothing, tried not using external script, tried to put value one by one, it works, my css is also broken, thanks fucker, the client only asked to directly download the html page instead of save as PDF. I thought why the fuck not?

evo pdf modified my CSS element for some odd reason, flex and grid got messed up, page width also fucked along with font size, doesn't support some javascript function. I shit you not the .after and let doesn't work. Fucking garbage

Edit: it worked now, but I spend hours today rewriting everything just to looks decent and it still looks like shit fml

Okay so even at my advance 52 years of age, I still pull all nighters to handle emergency remediation projects, and clean up other peoples messes. I don't mind, I'm a geek, I get high on the challenge of fixing shit that is broken all to hell.

But tonight was different. Tonight has me raging.

I am tasked with renovating a website, and building a sister site to that main site as well. no bother, I haven't done any web dev in 15 years but I'll power through pulling 18 to 20 hours a day for a couple of weeks to get in the groove...

Little did I know... CSS is a pain in the ass to be sure, but FLEXBOX is total and complete bullshit.

I don't give to shits about all the fancy shit it can do, it can't do simple shit worth a damn. Fuck Flexbox, and anyone involved in producing that useless layout model.

The sheer number of idiots promoting that hunk of shit a solution that is to be applied to any task other than wiping my ass is astounding.

Fuck all you jerk offs out there posting your shitty mark up turds as if they are gold, when you know better than anyone it works, sometimes, then doesn't, and is so easy to break it may as well be called "Web Design Jenga".

I'm still tired as hell, and tomorrow I will go back to slogging through CSS as the layout method, but at least I feel a little better now.

Oh and before I forget FUCK YOU FLEXBOX you piece of shit.

Why does CSS never work the way you'd expect? All I want to do is align something to the bottom of a div. No. Will not happen. You'd think it might be something simple as 'v-align' or 'align: bottom' or 'fucking put it at the bottom: now;'

No, it's never that simple. I try every result I can find from googling. Nothing. Simply does not work.

How about trying to keep a div to a square when you resize the page? That should be simple? height = width right? Fuck you. Ha hahah, no you have to implement some horrendous arcane hack involving fake elements and other bullshit.

You finally fix one thing and everything else you had working is now broken.

...and then some fuckwit comes along and goes "Oh, CSS isn't hard..." and it takes everything you have not to beat them to death with your rubber duck.

What the hell is wrong with CSS? It's not even programming! It's just pure, sadistic hell! FUCK CSS!!!!

I'm so close to giving up. Yesterday, I travelled 4 hours in one direction for a job interview for a graduate position as a web developer. As I arrived at the interview, I was welcomed by a senior dev and one of the HR people.

I sit down and they start explaining how everything will commence(standard procedure stuff) and afterwards hand me the technical test. At this time I am super calm cause I did my homework, checked out their products, their websites and knew right away what I was going to work on. As I turn the page, I see at the top with huge fucking capital letters "JAVA OOP test".

I take a minute and look back at them, like wtf is happening. Turns out that they are looking for a java dev. They picked me for the role because I had literally 1 fucking sentence in my CV and where I have said that I studied java in one semester of uni. FYI my entire portfolio, cv and cover letter are focused on JS, html, css both for client and server side.

As the fucking HR guy stood there and asked me "is there something wrong", I felt broken inside. For the first time in my fucking life I felt like I was done and couldn't continue anymore. I felt like this is some bitch-slap from karma about something but I still can't figure out what. I just walked out of there being unable to realize what happened.

I just feel like I should end my developer career before it has even started, just go do business analysis or something. Why the fuck would someone put a job description entirely talking about Angular, Less/SASS, bootstrap and jQuery and then say that is a Java dev OOP role. Who the fuck allows those people to take good salaries yet still deliver the up most shittiest quality service.

Before the interview, I checked out their websites which are simply horrendous with the comparability of a fucking baked potato. Idk really what to do, I don't mean to sound as a whiny little b.... but as I walked out of their office, I felt broken inside. Sorry for the long rant.

Everytime I hear "there's a problem" in my office I cringe so bad I have the impression I'm making holes in my teeth.

I hate this "janitor" / "plumber" role I have here, so insulting in terms of brain power.

** randomly codes something **
** colleague breaks silence **
C: Phlisg? There's a problem.
Me: what now?
C: Well when I enter a title that is 500+ characters for my blog post, it breaks the layout.
Me: obviously the title is too long. Shorten it.
C: I can't because [reasons] (unfortunately true reasons)
Me: ** deep sigh ** yeah, will look at it... ** proceeds to hide anything longer than 10 characters **
C: perfect!

--- 3 days later
C: Phlisg? there's a problem.
Me: mh?
C: the text is too short, can you make it longer
Me: ** FFS ** guys, you should've asked for a "Word-type" website if you just wanted to do any kind of layout. No, can't, sorry. Choose either between broken layout or shortening your damn text.

-- 1hr later, pm comes in
PM: Text is too short
Me: Yep. Any longer will break everything visually
PM: can't you fix this?
Me: Yes I can, but it'll be a whole CSS revamp because it was not MEANT that texts should be so long.
PM: How many hours?
Me: ** overestimating ** 10 hours (2.2 days of work)
PM: nah, okay, just add it as a side project

** me, inside : WOW, WHAT A FUN PROJECT OMG **

WebDev jobs should come with big warning signs:
"You absolutely will lose your sanity!"
"IE11 might indirectly lead to impotence!"
"You won't get laid more often by using CSS Grid!"
"You will have to fix websites which only appear broken on iOS Safari!"
"Get some extra terabytes ready for your node modules!"
"Get ready to yarnify your npm dockerized webassembly blobs while gulping on your mocha chai latte with no karma!"

Can't we just go back to the good old times with Quick Basic and chill?
Man, the ladies were flocking around those programmer boyz, I tell ya... Klickety klackety on the mechanical

Hey Designer/Developers, I got a question for you. Yeah, you 👇🏽

When working on a project codebase that is expected to grow and evolve heavily. How do you usually split up your CSS (SASS, LESS etc) in a good way to take into account all the different device sizes?

I am not asking how it is done but more about the design of the code. This would be for a production codebase to be released.

Do you use large blocks broken down by media...

(Media width) {

~site code

}

(Other media) {

~same site code with diff sizes

}

Or do you do individual media queries inside css classes...

.className {

(Media size) {

}

(Other media) {

}

}

Or a mixture of both?

If it is a mixture of both then how do you decide which way to go about structuring the code.

I have been endeavouring to greatly improve my CSS and have done so. But this question has been bugging me. Both sides seem to be a bit sloppy and my programmer side is fighting the repeatitipve code.

Note: all code examples are gibberish and only intended for visualization.

So, you may know this already...But fuck CNET once again! Don't get me wrong, even if I loved the auto-playing video ads I would still be angry af. The site loads with a decent layout at first, but then in a second it changes and all I get is a pile of shit broken because of some <sarcasm>really great</sarcasm> CSS.

P.S. Yeah, I know it's probably my ad blocker killing something that is vital for the site to keep it's shape, but I don't care about that at all. I'll never give it up. (Or let it down, for that matter)

Public CSS discord: "Oh, awesome thanks, man! No need to apologize, I'll check the code. I DM'd you."

DM: Total meltdown cry baby freak-out... "Oh yeah... well, if the code is broken - then why does my repo have 63 stars? I think I'd know if my code didn't work - it must be your computer. Why won't you let me team-viewer into your computer and see your screen? I don't care about your personal information. It's made with React, not CSS. I thought you would be helpful - but you're not at all. You aren't professional..."

Uh... (I can see the code... team-viewer isn't going to help you... and I'm at work... and I already spent 15 minutes helping you - you fucking prick)

Compiled a small style change in LESS file. Whole page is broken. Realized holiday replacement made all changes in main CSS file which is generated through LESS compiling.

Dear Tailwindcss,

Fuck you.

Fuck you and your messy as fuck html files.

Fuck your shitty pseudo 90s 'Let's dump all our shit in a single html file'.

Fuck your claims of being responsive, most of your widths and heights are done in FUCKING PIXELS.

Fuck your claims of being flexible, adding a 10% width class took 20 minutes of scrolling through your shitty docs.

And the worst part is, the poor devs 4 years from now are gonna be stuck maintaining this goddamn shit because shitty enterprise companies desperately trying to stay relevant are treating this shit like the Holy God of Frontend styling, the solution to CSS once and for all

FUCKING IDIOTS CSS ISN'T BROKEN, THIS GARBAGE IS!!!! WE DON'T NEED A SHITTY SOLUTION TO A PROBLEM THAT DOESN'T EXIST

Tailwind can go fuck itself with it's 200 character html lines

"Can you review this pull request?"

Ok, sure

- Description in broken English
- HTML/CSS changes seemingly just for the fuck of it
- No user story listed OR
- User story listed has no description
- Mockup does not specify what should be changed
- Owner is offline because this entire team operates out of India
- Requirements said to exist but their location is unknown

rant!

Fuuuuuuuuuuck..... why is CSS so fucking ASS when it comes to working the way it is supposed to. Why would someone create such a broken tool.

end rant.

Thats all, have a good day.

Fuck Wordpress, Fuck Wordpress's PHP
I'm so fucking tired of everything in this godforsaken CMS. Import a JS File? Sure, just add a *completely obvious* line into a very specific PHP File, where you'll have to specify a lot of "useful" parameters. No, I somehow DON'T want to specify that I don't wand jQuery in every import. And don't even get me started on Content Delivering. Embed CSS? Sure, just write the fucking whole path to the file, or use the broken get_stylesheet_uri() Function. Embed an Image? Sure, let me just go to the Backend and wait 6 Minutes for this bullshitty System to upload the image and then copy the hard-coded Link. Oh, you want to remove googleapi embeds? Sure, let me just fuck up your whole Website in return.
You want jQuery? Well instead of using the "$" Symbol, you have to use the jQuery() Function. Except when you don't have to, which is 100% random each time you reload the page. Oh, you actually did import a JS File? Sure, let me just not run it. Thank you fucking piece of shit thats calling itself "WordPress" and fuck you and everyone whos actively encouraging its usage

I’m convinced that CSS is black magic and those that can visualize what it’s going to do before changing code are witches/warlocks.

Usually my attempts end up in humor as the website ends up /comically/ broken. Elements shifted around to not anywhere near they belong, drop downs appearing from completely nonsensical places...

No idea how you all do it.

Drupal makes me want to go back to the moment that life first crawled out of the ocean, and shoot that first land-dwelling organism in the head – just to make sure that the animal kingdom never evolves to the point where a crime as ghastly as Drupal can occur.

Drupal somehow manages to be both unforgivingly, bureaucratically rigid, and an anarchic, spaghetti-coded mess – at the same time. Other frameworks are toolboxes. Drupal is a series of windows at the IRS or MVA – and it *will* take you days to figure out which series of forms you have to submit, with which boxes checked, in order to accomplish your goal.

The documentation is complete and utter trash.

It models content in a way that makes all sorts of assumptions about your use case. And those assumptions don't have anything to do with *how websites are actually designed and built*. In 20 years of building websites, I've never *once* wanted to use anything resembling the bizarre data model that Drupal *forces* you to use. Nor have I ever thought "gee, I wish my platform forced me to stop writing code every 20 seconds, so I can use an atrociously designed point-and-click interface".

I ask the community how to accomplish [insert extremely fucking basic task here], and they say: "well, you just install these 17 modules, glue them together with a bunch of configuration that couples your database to your code, and then shrug at the hideously broken HTML/CSS that comes out, because we give exactly zero shits about UX! isn't it great how Drupal makes things so easy?" Like, no – literally *every other framework on the planet* allows you to accomplish the same thing with just a few lines of code.

Most of the community seems to have little or no experience with other frameworks – so they seem solipsistically unaware that these are even problems. If your platform has been stabbing you in the arm for as long as you've been building websites, then you're just gonna assume that being stabbed in the arm is part of developing websites, you know? They seem oblivious to the fact that things are *so much easier* when your platform just lets you build whatever abstractions you need, instead of forcing its own weird-ass, undocumented assumptions on you.

Uruururrrrrrrggghgh. I can't understand how anyone defends this piece of garbage. If you're a Drupal developer reading this – please, for the love of God, try learning another framework. Once you've spent a couple of weeks learning saner ways of doing things, you'll never look back. I cannot comprehend how Drupal is still a thing.

I am so fucking tired of sitting here all day every day adjusting paddings and margins. Oh fucking hurr durr you got one of the millions of fucking elements to not overflow on your page, well does it work on *this* resolution and *this* orientation? No, well fix that and then go back and fix what it breaks.

I swear to God I never want to touch fucking CSS again it's all I've done for a yesr and it is driving me up the god damn wall. This is my career, I shouldn't fucking dread coming in to work because I know how much bullshit I'll have to deal with. It's awful.

I don't get how anyone has good looking complicated pages that just look good on every possible resolution, it's fucking mind boggling that anyone can sit there and adjust heights and widths and paddings and margins and floats for hours on end nonstop just watching shit get broken and fixed and broken and fixed and AHHHHH

I need a fucking smoke and a pint just so I don't have to think about this anymore

I dislike Google page speed. I understand their intention but sometimes it's just stupid, like inclining critical CSS and loading in the rest of the CSS using JavaScript.

What happens if the user has JavaScript disabled? They get a half rendered site they can't use that looks broken, but hey, at least the crappy site loads quickly.

Got some Freelance work(PHP) via my friend so i said ok lets see. Those were some college students and wanted their project to be deployed that their seniors built and none of them knew how to fix the issues so here i step in.
Nightmare of a design, no signs of framework, html/css looks like it was designed by a 10th grader, no prepared queries, every file uses db config seperately so a minor change would require me to edit those 50+ php files... overall a broken mess. FML.

It's been long time that I use the JavaScript blocker add-on by default, and I pretty much get accustomed to see and perceive the web as broken styling trash for most of the times.

And this broken state(on non-SPA websites) isn't even justified because CSS has never been as powerful as nowadays. So... WTF?

On my side, I never let the absence of JavaScript ruin the template/style of a webpage u_u

"Mobile optimized" themes, templates, websites etc that are looking completely broken on an actual mobile device are fucking ironic, especially those "css framework" websites.

Does anyone know any offline program like jsonresume to create pdf resumes..? It seems jsonresume is broken, and everytime i try it builds a pdf with no theme at all..

I need a resume where space is not wasted and i dont want to rewrite the entire css to make that happen. Suggesting a specific jsonresume theme i.e. style.css and .hdr file would also help because i found a blog where it was explained how to build a html resume using these..

And is there any offline html to pdf converters ?

2 seconds after I checked in some work on a web page, co-worker runs to me, freaking out because "This is not how I wanted it to look!" and waving a printed mock-up in my face.

I inherited a shitty, bloated, broken, 10-year-old site with dumbass CSS, but I did my best to work with it. I'm not surprised it's broken, so calm the fuck down and let's talk about what you're seeing and I'll happily fix it. It will be okay!

Just spent 10min trying to figure out why everything was broken in Chrome after refactoring custom CSS to its own page, and the header to its own JSP... I forgot to clear my browsing history and thought it was broken everywhere but IE.

FUCK. YOU. WINDOWS. FORMS.

This fucking old ass piece of shit with zero features and broken core fucking functionality, why the fuck does it have to BREAK THE WHOLE FUCKING UI DESIGNER UI whenever i rebuild the fucking project, WITHOUT AN OPTION TO RESTORE IT OR EVEN PRESS ALT+Z. WHY did this fucking piece of shit ever come to existence, it's not relevant anymore for the last 50 years or when was that crap born.

I'm tired of this fucking shit. TIRED OF IT. Oh my god if I could just write the ui in html and css. BUT I CAN'T, instead I'm stuck with this fucking clusterfuck fucking fuck someone send help sdsdfmoksfd

CSS background-color is completely broken in Chrome Canary on the macOS Sierra beta. Unfortunately using Canary is the only way I can use Chrome on Sierra because of a different bug with Chrome.

I fucking hate it that "front end developer" came to mean "data flow for react engineer". It seems most frontenders now don't understand shit about HTML and its standards, don't know anything about basic accessibility and proper content structuring.

It's even worse with the styling. Cascade? The fuck is cascade? Scope everything! And, of course, write that CSS as a JS object because how else. Fluid typography? If by fluid you mean 16px, sure. Any more advanced techniques? Lol forget you're getting rounded boxes with a shadow and you're gonna like them.

But yeah, I'm glad they're overengineering Redux again because their reactivity model is fundamentally broken. That's exactly what """frontend""" should be about.

That moment you update your ui library, to find out this update has a small align-items css prop that breaks every form on every page.... imagine the impression when you see it all broken... priceless

Wow Chrome, you can just go fuck yourself. I am trying to make this epic CSS effect for one fucking hour just to find out filter animations are completely trash and broken there. At least our Firefox clients will still see it thanks to @supports...