Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "styling"
-
EDIT: devRant April Fools joke (2020)
-------------------------
We've been at this a few years now, and over the last 6 months we've been working closely with a brand consulting agency, and after numerous developer interviews, surveys and focus groups, we've come to realize "devRant" is simply not capturing the cultural zeitgeist of this new decade. Therefore, we have a bold new brand that will be rolling out over the coming week. devDucks is our bold vision for the future, today. devDucks speaks to a new generation of software engineers who resonate with a more upbeat, optimistic tone when they go to an anonymous web community to swear and lament their current work situation. While we finalize the new logo and other key marketing collateral, we have started a staged roll-out of our new brand styling, including the conversion of all avatars to literal devDucks. We hope this brings more joy to your ranting, as it has to ours. Sincerely, David & Tim (@dfox & @trogus) - devDucks co-founders56 -
Me: Oh it's just a simple formatting/styling issue, shouldn't take but a minute
Computer: *laughs in html*7 -
You know what's the difference between
- static page written purely in HTML with inline styling
and
- dynamic page generated in PHP, that actually loads data from MySQL database and is correctly styled in separate CSS document
on national level exam necessary to earn a title of technician?
ONE HACKING PERCENT!
Ok, backstory. So, few days ago I got results from that exam. To be honest, it was very, very easy so I wasn't worried at all, unlike some of my classmates who just don't understand programming at all (you need at least 75% to pass). Our task was to create database, write website in PHP that shows contents of that database and use CSS to give it a look that of example web page and run it on XAMPP. I've got result of 96% and while I was wandering what I've done wrong i hear my colleague almost screaming with joy "I passed! And I haven't even touched PHP. I was soooo sure I'll fail." So I asked him what's his result and he says 95%. And then another colleague said he got 95% without PHP. So, in other words what I thought to be the main task was worth 1%. Apparently, what was more important was for the page to look identical to the example, so I guess some examiners didn't even look into the source. And don't get me wrong, I don't wish my classmates had failed. That's not why I'm ranting. But why in the name of Ada Lovelace the task said to use PHP and all that if it weren't supposed to check our knowledge of programming in PHP? Sometimes I think the people who design these tests don't even know what they're doing.10 -
Incompetent doesn't even start to describe this one:
1. Uses Google drive instead of an online repository for code sharing
2. Uses multiple files instead of version control
3. Preferred variable names like a, a1, b, temp
4. Didn't like "wasting" space. The result was unreadable unindented code
5. Would rather use deprecated HTML tags rather than proper CSS styling
He was more like the personification of bad coding practices8 -
Friend - Hey man, why so angry?
Me - Nothing on my fucking page is
styling correctly!
Friend - Lemme see your code...
You know you forgot the
semicolon on your first CSS
line right?
Me - ... OH FUUUCCCKKK3 -
Manager: What’s taking so long on that PR?? It’s just some small styling adjustments
Dev: No it’s not you added an entire new calendar module that doesn’t work
Manager: Ok but besides that it’s just a small couple of css edits
Dev: You made styling changes in 50 files, half of which break our mobile responsiveness
Manager: Well then STOP talking to me and FIX IT if you’re so smart.
Dev: You also added a series of filters on a table in this same PR that cause th—
Manager: OK SO I GOT A BIT DISTRACTED THE FACT IS IT ALL NEEDS TO GET DONE SO IT DOESN’T MATTER IF IT’S ALL ON ONE PR SPLITTING THINGS UP INTO SMALL UPDATES IS JUST UNNECESSARY BUREAUCRACY AND IF YOU LIKE THAT THEN GO. WORK. FOR. THE GOVERNMENT!!!
Dev: …10 -
When your boss asks for a web application that has drag and drop, resize, popup, fade inand out, dynamic styling and mobile compatibility but must work on IE8
You feel like:
Mission: Go to the moon
Tools: Broom's stick
Yeah i'll just pretend to be a witch and fly away7 -
Let me preface this by saying I'm not a designer.
While I can make individual bits of a site look good, and I'm actually pretty skilled with CSS/Sass, overall design completely escapes me. I can't come up with good designs, nor do I really understand *why* good designs are good. It's just not something I can do, which feels really weird to say. but it's true.
So, when I made the Surfboard site (that's the project's internal name), I hacked everything together and focused on the functionality, and later did a branding and responsive pass. I managed to make the site look quite nice, and made it scale well across sizes/devices despite being completely new to responsiveness. (I'm proud, okay? deal.)
After lots of me asking (in response to people loudly complaining that the UI doesn't have X feature, scale properly on Y device, and doesn't look as good as Z site), the company finally reached out to its UI contractor who does their design work. After a week or two, he sent a few mockups.
The mockups consisted of my existing design with a darker background, much better buttons, several different header bars (a different color) with different logo/text placements, and several restyled steppers. He also removed a couple of drop shadows and made some very minor styling changes (bold text, some copy edits). Oh, he also changed the branding colors. Nothing else changed. It's basically the same exact site but a few things look a little better. and the branding is different.
My intermediary with the designer asked for "any feedback before finalizing the designs" -- which I thought odd because he sent mocks for two out of the ten pages (nine plus a 404 page). (Nevermind most of the mocks showed controls from the wrong page...).
So, I typed up a full page of feedback. Much of it was asking for specifics such as responsive sizing on the new header layout, how the new button layout would work for different button counts, asking for the multitude of missing pages/components, asking why the new colors don't match the rest of our branding, etc. I also added a personal nitpick about flat-looking controls because I fucking hate them. Everything I wrote was very friendly and professional.
... His response was full of gems. Let me share a few.
1. "Everything about the current onboarding site looks like a complete after-thought." (After submitting a design basically identical to mine! gg!)
2. "Yes [the colors match our current branding]." (No. They don't. I checked. The dark grey is different, the medium grey is different, the silver is different, the light blue is different. He even changed the goddamn color of the goddamn LOGO for fuck's sake! How the fuck is that "matching"?!)
3. "Appreciate the feedback [re: overlapping colored boxes, aka 'flat'], design is certainly subjective. However, this is the direction we are going." (yet it differs from the rest of our already-redesigned sites you're basing this off. and it's ugly as shit. gg again :/)
4. "Just looked at the 404 page. It looks pretty bad, and reflects very poorly on the [brand name] brand. Definitely will make a change here!" (Hey! I love that thing. It's a tilted, dotted outline of a missing [brand product] entirely drawn with CSS. It has a light gray "???" underlay and some 404 text inside. Everyone I showed it to, coworkers and otherwise, loved it. "Looks pretty bad". fuck you.)
I know I shouldn't judge someone so quickly, but what the fuck. This guy reminds me of one of those pompous artists/actors who's better than everyone and who can never be wrong, even while they're contradicting themselves.
just.
asfjasfk;ajsg;klsadfhas;kldfjsdl.undefined surfboard another rant about the same project long rant pompous designer apples and asteroids design8 -
( rant || !rant ) && idiots
console.info( this.isLongRant );
console.warn( "contains strong language and wordpress" );
A friend of mine sent two of his "friends" to me because they wanted me to build a website for their new business (~idea).
So I had a meeting with them.
First of all they wanted me to have a look on the current (work in progress) site.
First impression of the frontend:
OH BOY!?
Well, imagine this:
- a 90s/2k background (dotted/pixelated cloud in baby-blueish as backgroud with repeat)
- the logo was made by the sister of one of the guys, it wasn't too bad, but badly aligned, asymmetrical
- some obvious $offTheShelfShopPlugin with $randomStockContent
- the fucking slider had a small loading bar to indicate changes, it appears like an hyperanxious child on ADHS
- below the logo TWO FUCKING GIF SPINNERS to indicate nothing else but how fucking brain amputated these two dudes are, including the dev who is responsible for adding this. (to this point, they only told me, that a webagency did the setup and some basic work on the site, more on that later)
- no styling concept at all, random fonts and stuff everywhere including default styles of the shop plugin.
- FUUUUUCK WTF wil come furtherin this meeting?
After seeing a pile of binary puke fisted out of a 60yo nonstop-intern who changed his jobtitle from dildo-traveling-salesman to fullstack-frontend-dev by wrinting it on a post-it-note, I imagined, there has to be something wrong with the backend as well.
Boy was I right!
Yes, you guessed it! A random Wordpress adminpanel login appeared! OH NO....
I really wanted to levae this meeting immediately.
I was not able to hold my disgust back and I told them right in their face, what a shit pile of nutty squirrel turds this current page is. And that Wordpress is not the right choice at all for a shop.
Then came the best part: They basically told me, that they terminated the previous contract with the webagency because they were too expensive (they are cheap, compared to others, I know people who know their prices) and that they wanted to create A BIG MARKETPKACE with multiple ressellers who can have their shop in their website. Something similar to FUCKING AMAZON. ON FUCKING WORDPRESS!?!?!?
They even asked me if I wanted to be their partner & developer and that they can't pay much at the moment until the marketplace starts to grow.
I more or less told them to go fuck themselves with a rusty pitchfork.2 -
I'm trying to sign up for insurance benefits at work.
Step 1: Trying to find the website link -- it's non-existent. I don't know where I found it, but I saved it in keepassxc so I wouldn't have to search again. Time wasted: 30 minutes.
Step 2: Trying to log in. Ostensibly, this uses my work account. It does not. Time wasted: 10 minutes.
Step 3: Creating an account. Username and Password requirements are stupid, and the page doesn't show all of them. The username must be /[A-Za-z0-9]{8,60}/. The maximum password length is VARCHAR(20), and must include upper/lower case, number, special symbol, etc. and cannot include "password", repeated charcters, your username, etc. There is also a (required!) hint with /[A-Za-z0-9 ]{8,60}/ validation. Want to type a sentence? better not use any punctuation!
I find it hilarious that both my username and password hint can be three times longer than my actual password -- and can contain the password. Such brilliant security.
My typical username is less than 8 characters. All of my typical password formats are >25 characters. Trying to figure out memorable credentials and figuring out the hidden complexity/validation requirements for all of these and the hint... Time wasted: 30 minutes.
Step 4: Post-login. The website, post-login, does not work in firefox. I assumed it was one of my many ad/tracker/header/etc. blockers, and systematically disabled every one of them. After enabling ad and tracker networks, more and more of the site loaded, but it always failed. After disabling bloody everything, the site still refused to work. Why? It was fetching deeply-nested markup, plus styling and javascript, encoded in xml, via api. And that xml wasn't valid xml (missing root element). The failure wasn't due to blocking a vitally-important ad or tracker (as apparently they're all vital and the site chain-loads them off one another before loading content), it's due to shoddy development and lack of testing. Matches the rest of the site perfectly. Anyway, I eventually managed to get the site to load in Safari, of all browsers, on a different computer. Time wasted: 40 minutes.
Step 5: Contact info. After getting the site to work, I clicked the [Enroll] button. "Please allow about 10 minutes to enroll," it says. I'm up to an hour and 50 minutes by now. The first thing it asks for is contact info, such as email, phone, address, etc. It gives me a warning next to phone, saying I'm not set up for notifications yet. I think that's great. I select "change" next to the email, and try to give it my work email. There are two "preferred" radio buttons, one next to "Work email," one next to "Personal email" -- but there is only one textbox. Fine, I select the "Work" preferred button, sign up for a faux-personal tutanota email for work, and type it in. The site complains that I selected "Work" but only entered a personal email. Seriously serious. Out of curiosity, I select the "change" next to the phone number, and see that it gives me four options (home, work, cell, personal?), but only one set of inputs -- next to personal. Yep. That's amazing. Time spent: 10 minutes.
Step 6: Ranting. I started going through the benefits, realized it would take an hour+ to add dependents, research the various options, pick which benefits I want, etc. I'm already up to two hours by now, so instead I decided to stop and rant about how ridiculous this entire thing is. While typing this up, the site (unsurprisingly) automatically logged me out. Fine, I'll just log in again... and get an error saying my credentials are invalid. Okay... I very carefully type them in again. error: invalid credentials. sajfkasdjf.
Step 7 is going to be: Try to figure out how to log in again. Ugh.
"Please allow about 10 minutes" it said. Where's that facepalm emoji?
But like, seriously. How does someone even build a website THIS bad?rant pages seriously load in 10+ seconds slower than wordpress too do i want insurance this badly? 10 trackers 4 ad networks elbonian devs website probably cost $1million or more too root gets insurance stop reading my tags and read the rant more bugs than you can shake a stick at the 54 steps to insanity more bugs than master of orion 313 -
This codebase reminds me of a large, rotting, barely-alive dromedary. Parts of it function quite well, but large swaths of it are necrotic, foul-smelling, and even rotted away. Were it healthy, it would still exude a terrible stench, and its temperament would easily match: If you managed to get near enough, it would spit and try to bite you.
Swaths of code are commented out -- entire classes simply don't exist anymore, and the ghosts of several-year-old methods still linger. Despite this, large and deprecated (yet uncommented) sections of the application depend on those undefined classes/methods. Navigating the codebase is akin to walking through a minefield: if you reference the wrong method on the wrong object... fatal exception. And being very new to this project, I have no idea what's live and what isn't.
The naming scheme doesn't help, either: it's impossible to know what's still functional without asking because nothing's marked. Instead, I've been working backwards from multiple points to try to find code paths between objects/events. I'm rarely successful.
Not only can I not tell what's live code and what's interactive death, the code itself is messy and awful. Don't get me wrong: it's solid. There's virtually no way to break it. But trying to understand it ... I feel like I'm looking at a huge, sprawling MC Escher landscape through a microscope. (No exaggeration: a magnifying glass would show a larger view that included paradoxes / dubious structures, and these are not readily apparent to me.)
It's also rife with bad practices. Terrible naming choices consisting of arbitrarily-placed acronyms, bad word choices, and simply inconsistent naming (hash vs hsh vs hs vs h). The indentation is a mix of spaces and tabs. There's magic numbers galore, and variable re-use -- not just local scope, but public methods on objects as well. I've also seen countless assignments within conditionals, and these are apparently intentional! The reasoning: to ensure the code only runs with non-falsey values. While that would indeed work, an early return/next is much clearer, and reduces indentation. It's just. reading through this makes me cringe or literally throw my hands up in frustration and exasperation.
Honestly though, I know why the code is so terrible, and I understand:
The architect/sole dev was new to coding -- I have 5-7 times his current experience -- and the project scope expanded significantly and extremely quickly, and also broke all of its foundation rules. Non-developers also dictated architecture, creating further mess. It's the stuff of nightmares. Looking at what he was able to accomplish, though, I'm impressed. Horrified at the details, but impressed with the whole.
This project is the epitome of "I wrote it quickly and just made it work."
Fortunately, he and I both agree that a rewrite is in order. but at 76k lines (without styling or configuration), it's quite the undertaking.
------
Amusing: after running the codebase through `wc`, it apparently sums to half the word count of "War and Peace"15 -
Dear software companies,
As much as I appreciate all the dark themes being used lately either as default, or added as options (Youtube, Discord, Postman, Windows Explorer, etc)... you guys still suck at theming.
A #000 background with #fff font is almost as bad as the reverse. Too much contrast! Then there are some apps which use grayish tones, others brown/orange stuff... pretty ugly if you use it all next to each other.
So how about just adding good theming support? Or even better: what about a global theming standard, a styling preference, a system wide json file which defines UI elements for all apps?4 -
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 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?6 -
Well. Here is the story.
Started making a React app a week ago with a friend; his job was styling some jsx i "already" wrote. hmmmm. and i just pulled his last commit.
file [index.scss]
3 lines:
body {
font-size: 16px;
}
😐😐😐😐😐14 -
>be me
>I hate front-end dev, but I can do it. I hate switching between markup, styling, and logic.
>I like back-end and low level programming
>stay unemployed for a year and a half, because all offers are for React and Angular
>find backend job, yay
>they actually make me work on front-end shit
>mfw pic related7 -
Can we all take a moment to appreciate what a complete mess web technologies are.
We're abusing a markup language made for scientific writing, by styling it with css and in order to make it dynamic somehow, we run a weird ass scripting language on the clientside.
Because nobody really wants to use this burning garbage can, some of us invented web frameworks.
And let's not get started on php...14 -
The nightmare continues.
Currently dealing with a code review from a “principal” dev (one step above senior), who is unironically called a “legendary dev” by some coworkers. It’s painfully obvious he didn’t read the code, and just started complaining and nitpicking.
It’s full of requests to do things that make absolutely no sense, and would make the code an unmaintainable mess.
• Ex: moving the logic and data collection from the module’s many callers into the module instead of just passing in the data.
• Ex: hiding api endpoint declarations by placing them in the module itself, and using magic instance variables to pass data to it. Basically: using global functions and variables instead of explicit declarations and calls.
• Ex: moving the logic to determine which api endpoint to use, for all callers, into the view.
More comments about methods being “too complex” (barely holds water) right next to comments saying “why are these separate? merge them together!”
Incredulously asking how many times I’m checking permissions and how ridiculous it all is. (The answer? Twice.)
Conflating my “permissions” param and method names with a supposedly forthcoming permissions system overhaul, and saying I shouldn’t use permissions because my code will all have to get rewritten. Even if that were true, and it’s likely not, the ticket still needs to use the current permissions. I can’t just ignore them because they might be rewritten someday.
Requests to revert some code cleanup because the reviewer thought the previous heavily-nested and uncommented versions (with code duplication) were easier to read. Unsurprisingly, he wrote them.
On the same ticket, my boss wants me to remove all styling and clientside validation, debouncing, and error messages from a form. Says “success” and “connection failed” messages are good enough. The form in question sends SMS and email using arbitrary user input for addresses. He also says it shouldn’t be denounced on the server, and doesn’t want me to bother checking permissions. Hello, spam!
Related: the legendary dev reviewer says he can’t think of a reason why we would want to disable the feature for consumers, so I should remove the consumer feature flag.
You can’t make this stuff up.7 -
A nice word to all developers who say stuff like "I know I write bad code, but what does it matter.":
Please try to think in a logical way about what this part you are about to write has to do. It is much more difficult to rewrite code, the longer you wait after you started to code.
Bad code can have big impacts on different levels.
For example financially: Bad coding style or program structure can lead to thousands or much more in losses because of nasty bugs, bad performance, expandability or maintainability.
Think about quality over quantity.
A little example: I had to work together with other coders to meet a fucking tight deadline. The last day we coded like crazy and these dudes started to apply styling changes (CSS) directly as inline styles to the HTML code, instead of taking a few minutes more to find where in the CSS files they had to make the changes.
At the end of the deadline we had more stylingbugs than before. It took us another whopping 3 hours to fix what they had done.
So next time you code: Thinking before coding is mostly faster than just straightahead coding and fixing at the end. 😉2 -
I worked for over 13 hours yesterday on super-urgent projects. I got so much done it's insane.
Projects:
1) the printer auto-configuration script.
2) changing Stripe from test mode to live mode in production
3) website responsiveness
I finished two within five minutes and pushed to both QA and Production. actually urgent, actually necessary. Easy change.
The printer auto-configure script was honestly fun to write, if very involved. However, the APIs I needed to call to fetch data, create a printer client, etc... none of them were tested, and they were _all_ broken in at least two ways. The CTO (api guy in my previous rant) was slow at fixing them, so getting the APIs working took literally four hours. One of them (test print) still doesn't work.
Responsiveness... this was my first time making a website responsive. Ever. Also, one of the pages I needed to style was very complicated (nested fixed-aspect-ratio + flexbox); I ended up duplicating the markup and hacking the styling together just to make it work. The code is horrible. But! "Friday's the day! it's going live and we're pushing traffic to it!" So, I invested a lot of time and energy into making it ready and as pretty as I could, and finally got it working. That page alone took me two hours.
The site and the printer script (and obv the Stripe change as well) absolutely needed to be done by this morning. Super important.
well.
1) Auto-configure script. Ostensibly we would have an intern come in and configure the printers. However, we have no printers that need configuring, so she did marketing instead. :/ Also, the docs Epson sent us only work for the T88V printer (we have exactly one, which we happened to set up and connect to). They do not work for the T88VI printers, which is what we ordered. and all we'll ever be ordering. So. :/ I'll need to rewrite a large chunk of my code to make this work. Joy :/
2) Stripe Live mode. Nobody even seemed to notice that we were collecting info in Test mode, or that I fixed it. so. um. :/
3) Responsiveness.
Well. That deadline is actually next Wednesday. The marketing won't even start until then, and I haven't even been given the final changes yet (like come on). Also! I asked for a QA review last night before I'd push it to production. One person glanced at it. Nobody else cared. Nobody else cared enough to look in the morning, either, so it's still on QA. Super-important deadline indeed. :/
Honestly?
I feel like Alice (from Dilbert) after she worked frantically on urgent projects that ended up just being cancelled. (That one where Wally smells that lovely buttery-popcorn scent of unnecessary work.)
I worked 13 hours yesterday.
for nothing.
fucking. hell.undefined fuck off we urgently don't need this yet! unnecessary work unsung heroine i'm starting to feel like dark terra.7 -
I was getting a freelancer job to do some backend work for a company in India that is working for a huge company in Saudi Arabia.
The customer in india was my primary contact, I wasn't allowed to talk to the guys in Saudi Arabia. My contact, we'll call him Aman, asks if i can do frontend too. I decline. Now what follows were 4 weeks of backend work during which Aman called me 10-15 times per day via skype to ask me how I was progressing, and if "insert spec here" was already done. He even called me in the middle of the night, well aware of the different time zones.
But in the end all the work is done, Aman is happy. I request payment.
Aman: We can't pay you yet, you didn't do the frontend!
Me: I'm not doing frontend.
Aman: It's just a few simple changes and then we're done.
Me: Gnnn, fuck it, what do you need?
Aman: Our customer would like the frontend to look better.
Me: Ok, so what exactly should look better?
Aman: All of it.
Me: Do you have any specs?
Aman: No just make it look more modern.
Me: So you want me to rework the whole frontend? That's not just a few simple changes...
Aman: How long would you need?
Me: I actually don't do that kind of work.
Aman: We pay you double your hourly rate if you do this and finish it fast.
(This is were I should have just said no... but the greed...)
Me: Ok, but it will take me about 3 weeks to do that.
Aman: OK.
Me: Do you have any preferences as to how it should look?
Aman: No, just surprise us.
(After this sentence I really should have gotten the hell out of Dodge)
After working 3 weeks changing over 20.000 lines of CSS and most of the HTML I present Aman with the changes.
Aman: No our customer doesn't like the changes. Can you make a different version?
Me: What doesn't he like, any specifics, coloring, styling of lists or the buttons?
Aman: He doesn't like the whole thing. Please make us another version.
Me: Ok, you are the customer, but it would really help if you give me some pointers as to how it should look like.
Aman: Just do your best.
Me: ..., ok, that's helpful.
2 weeks later...
Aman: No our customer liked the version before better. But could you make it look more modern.
Me: *Bangs head against wall repeatedly*
Me: What do you mean by modern?
Aman: It should look more modern, as a whole.
Me: Ok, I get that, but could you give me an example?
Aman: Sends me a screenshot of the overview screen with all the elements encircled and modern written beside them.
1 week later...
Aman: The customer has decided, he likes the original version best. Can you undo all the changes?
Me: Sure but that'll take like 1 hour.
Aman: Oh by the way we were asked by accounting why the price for this project was so high?
Me: *hugh* *gnn* what?
Aman: Well at the beginning, you estimated the backend and frontend work to be done in 4 weeks.
Me: The frontend was never part of the original estimate.
Aman: Can you do anything concerning your hourly rate, so that we can get back to the original pricing.
Me: *make a mental note to never work with an intermediary company in india again and cancels the job requesting the due payment*
Luckily I got paid the full amount but not before having another 10 Skype call with Aman...17 -
I was straight out of uni so I didn't mind recruiters getting in touch, I just wanted a job.
The whole conversation was just generally awkward, it was just as if he hated his job, being there, and me. He had a wordpress project lined up which I was extremely ambivalent about, but I didn't want to rule anything out. We talked about my experiences with VueJS, React, material styling, how I had done a project which is live in production more or less solo fullstack, and some of my side projects.
He nods knowingly through it all while taking notes, before asking if I had heard of javascript or if I'd be willing to look at it until next time.
That's when you just get struck with this sense of "what can I do to leave this room as soon as possible without making a scene".2 -
Fuck web dev.
I dabbled in many areas but I do web dev most often. And seriously: fuck web dev. Your site has to work on multiple browsers. Multiple screen resolutions. The code has to be tiny for load time. The images have to work for every resolution and still be small. The styling can look different in different browsers. So many useful javascript features are only supported by modern browsers. An on top of that: IE.
I’ve gotten quite good at all of this, but still: it’s such a fucking pain.10 -
Yesterday I completed a transactions module that used an external payment processor, similar to PayPal. It was hard, but after few hours of trying out different options I finally managed to get it to work.
I decided to create a simple prototype UI without any styling just to show my progress to the manager and let him know that it's working.
His response? "yeah, that seems to work, but that UI is terrible and not appealing at all. Change that immediately and try to add more thought into your design"
I guess I won't be making prototypes any time soon6 -
While styling a website, I realise that I would be fired on the first day if I had a Web designer job
-
I've been working on implementing a fairly large feature on a project at work--
**Sorry. I should rephrase that**
I've been *trying* to work on implementing a fairly large feature on a project at work.
It's slightly complicated because I'm not as "in the know" with the project as I should be. I get tossed around projects a lot as the only designer+developer so I've got my hands in a lot of buckets... Or git repos I should say... My source tree has a lot of tabs open and each project is run by someone with their own ideologies on how stuff should be done and laid out and what not. Basically jumping between these projects leaves you mildly capable on all of them but not amazing at any of individual one them--
--I digress.
There's a bug I've been trying to fix.
--Stupid simple bug, literally just a casting issue or something but there's so much data in this one object that it's taking a few solid minutes of concentration to figure out which variable is busting it all up. It shouldn't take long to fix...
But it has. It has taken 4 days.
FOUR. DAYS.
...To fix what is basically a null reference exception.
Every time I sit down to work on this bug real quick I get pulled away to do a wireframe or change a flow chart or diagram or colour or print styling.
Every. God. Damn. Time.
4 days. Soon to be 5.
My commits are real low at this point guys.
Please boss man, just let me code...4 -
STOP. LOOKING. AT. HALF. FINISHED. SPRINTS. FOR. STYLING. ERRORS.
For the love of god I know it's not right yet leave me aloooooone7 -
I am much too tired to go into details, probably because I left the office at 11:15pm, but I finally finished a feature. It doesn't even sound like a particularly large or complicated feature. It sounds like a simple, 1-2 day feature until you look at it closely.
It took me an entire fucking week. and all the while I was coaching a junior dev who had just picked up Rails and was building something very similar.
It's the model, controller, and UI for creating a parent object along with 0-n child objects, with default children suggestions, a fancy ui including the ability to dynamically add/remove children via buttons. and have the entire happy family save nicely and atomically on the backend. Plus a detailed-but-simple listing for non-technicals including some absolutely nontrivial css acrobatics.
After getting about 90% of everything built and working and beautiful, I learned that Rails does quite a bit of this for you, through `accepts_nested_params_for :collection`. But that requires very specific form input namespacing, and building that out correctly is flipping difficult. It's not like I could find good examples anywhere, either. I looked for hours. I finally found a rails tutorial vide linked from a comment on a SO answer from five years ago, and mashed its oversimplified and dated examples with the newer documentation, and worked around the issues that of course arose from that disasterous paring.
like.
I needed to store a template of the child object markup somewhere, yeah? The video had me trying to store all of the markup in a `data-fields=" "` attrib. wth? I tried storing it as a string and injecting it into javascript, but that didn't work either. parsing errors! yay! good job, you two.
So I ended up storing the markup (rendered from a rails partial) in an html comment of all things, and pulling the markup out of the comment and gsubbing its IDs on document load. This has the annoying effect of preventing me from using html comments in that partial (not that i really use them anyway, but.)
Just.
Every step of the way on building this was another mountain climb.
* singular vs plural naming and routing, and named routes. and dealing with issues arising from existing incorrect pluralization.
* reverse polymorphic relation (child -> x parent)
* The testing suite is incompatible with the new rails6. There is no fix. None. I checked. Nope. Not happening.
* Rails6 randomly and constantly crashes and/or caches random things (including arbitrary code changes) in development mode (and only development mode) when working with multiple databases.
* nested form builders
* styling a fucking checkbox
* Making that checkbox (rather, its label and container div) into a sexy animated slider
* passing data and locals to and between partials
* misleading documentation
* building the partials to be self-contained and reusable
* coercing form builders into namespacing nested html inputs the way Rails expects
* input namespacing redux, now with nested form builders too!
* Figuring out how to generate markup for an empty child when I'm no longer rendering the children myself
* Figuring out where the fuck to put the blank child template markup so it's accessible, has the right namespacing, and is not submitted with everything else
* Figuring out how the fuck to read an html comment with JS
* nested strong params
* nested strong params
* nested fucking strong params
* caching parsed children's data on parent when the whole thing is bloody atomic.
* Converting datetimes from/to milliseconds on save/load
* CSS and bootstrap collisions
* CSS and bootstrap stupidity
* Reinventing the entire multi-child / nested params / atomic creating/updating/deleting feature on my own before discovering Rails can do that for you.
Just.
I am so glad it's working.
I don't even feel relieved. I just feel exhausted.
But it's done.
finally.
and it's done well. It's all self-contained and reusable, it's easy to read, has separate styling and reusable partials, etc. It's a two line copy/paste drop-in for any other model that needs it. Two lines and it just works, and even tells you if you screwed up.
I'm incredibly proud of everything that went into this.
But mostly I'm just incredibly tired.
Time for some well-deserved sleep.7 -
Nearly, nearly ready to deploy self-hosted maps, fucking awesome!
Aaaand now comes the goddamn styling since these will be vector tiles..
I fucking hate designing/styling and I fucking suck at it too. 10 attempts which all pretty much look like shit.
Fucking great.14 -
LONG RANT ALERT, no TL;DR
* Writes an email to colleague about why I can't create a page on our CMS without at least a H1 title. She wants to me to put up an image with text on it (like a flyer), for multiple reasons, I say I need a textless image. *
30 minutes later:
* Casually plans a frontend optimization project, by looking at files on the CMS, in order to make further development easier and less time-taking*
*** EMAIL NOTIFICATION ***
* clicks *
"Hello, this is [Graphic designer] from the company who created the image with text on it. I do not understand why you can't put display:none on your <h1> tag. Also, being a web company, we are used to making themes and my solution of display:none will work. It's pityful to work on a design only to have it stripped out from most of its concept. If you can't do that, do tell me what resolution you need."
My first reaction:
"Dear [Graphic designer], I am managing our corporate identity, our backend and frontend codebase, I am a graphic designer myself, and am also SEO-aware. For at least 8 reasons (redacted, 'cuse too long), I will need an image without text. As told to my colleagues, I need a 72/96 DPI 16:9 ratio image, 1920x1080 is a good start but may be bigger. Also, looking at the image, it'll have to be in JPG, at 100% quality, exported for the web. Our database software will optimize the image by itself."
Reasons are about SEO issues, responsiveness issues, CMS tools issues, backend and frontend issues.
Instead, I sent following email "We can't. Image please."
I mean seriously. A bit of clarity for you:
In my company, nobody has the slightest idea what I do. They don't understand how a computer works (we all know it works by magic, right?). So of course, when one thinks what we don't know, we know it better than the one who knows, my colleague thought our CMS was like a word document, and began telling me how I should display her bible-length text-infected image, by using some inline css styling display:none.
I tell her "nope, because of my 8 reasons". She transmits that to the agency who's done the visual, now I have this [Graphic designer] not understanding that there are other CMSs than Wordpress on the web, and she tells me, me being one of the most aware on this CMS we have, how I should optimize my site?
Fucking shit, she connects on our CMS for 1 second and she'll get cancer since it's so bad. I'm in the process of planning a whole new rewrite so the website is well designed (currently I am modifying a base theme made by an incompetent designer). I know the system by heart and I know what you can, or can't do.
Now I just received an answer: "so it's only a pure technical problem". NO, OUR WEBSITE WAS CODED BY A CHIMPANZEE WHO THOUGHT WEB DEV WAS AS EASY AS WRITING "HELLO WORLD" ON A SHITTY CMS THAT FORCES DEV USERS TO USE A FUCKING CUM-WHITE-THEMED EDITOR TO EDIT THE WHOLE SITE!!!
I can't just sneeze and "oh look, it's working!"1 -
Dear coworker,
We have a very nice SASS setup so WHY THE FUCK ARE YOU POLLUTING OUR HTML WITH INLINE STYLES!?!?!? It's not like it's even necessary to use inline in this case, I can achieve the same thing by just moving your styling to the scss files. So I ask again, WHY THE FUCK???
Sincerely,
A mildly pissed person who hates front-end dev work3 -
you fucking idiots
why do you always base your library components on some dumbass clown fixed width / height system?
everything should be flex by default, anything else is absolute amateur clown town pile of dumbass horseshit...
...i'll brawl and take down anyone who says otherwise
you waste my time, you waste other's time, when everyone has to go hunting around for your stupid library's unorthodox way of styling
thanks again for wasting and making my evening a living hell7 -
Am I the only one that gets fucking pissed when others write unnecessary <div>s?
I know sometimes it's necessary for styling, but my coworkers do it because it's easier to add a new div than extending the style of an existing element.
What's worst, when I do it they reject my PR saying to create a new div instead. Fucking fuck off.5 -
GRANDPAFUCKING RETARDS!
I HOPE YOU ALL DIE ON SOME ELEPHANT DICKS TURNED AROUND YOUR HEADS WHILE GETTING RAPED BY THOUSANDS OF GIRAFFES (EACH OF THEM BEING SO HORNY THAT THEY ALSO COULD FUCK YOUR WIFE AT THE SAME TIME!)
THEY ASK ME A FUCKING QUESTION AND ONLY GIVE ME THE OPTION TO AGREE ON THE COOKIE POP-UP TO ENTER THE WEBSITE! YOU DIPSHITS!
YOU SISTERFUCKING ASSHOLES!
WELL... I FUCKING CLICKED "AGREE" AND WHEN I FINALLY FOUND THE PRIVACY CENTER (LOL) THE SAME FUCKING POP-UP DID APPEAR!
HOW ABOUT YOU FUCKING FUCK YOURSELF, DISTROWATCH?!
Btw. they really still use tables instead of proper css styling.
DO WE LIVE IN THE FUCKING STONE AGE?!10 -
Spent 4 hours debugging a “button” styling, worked fine locally but not on production.!
After striking out “cache” issues, “browser” versions, “fonts”, “sass errors” the error was with a stupid chrome extension that appended a css class attribute to the “HTML” tag 😡
And the other developer thought that was a part of what was written in the code !!
Hate these kinda plugins that manipulate the DOM 😪
P S the plugin is "Grammarly".2 -
Retarded person I met today : "JS is gay cos you require strict mode for blah blah blah"
Me (and my webdev friend): pfft...
[Shows our ESLint Styling rules]
him: "o-oh... How the f-"6 -
I am good as Front End developer, using JavaScript I can do the job, the whole job. Developing, Styling, designing and deploying the web applications is my daily job for few years now...
Today I quit my job for a new position as Back End developer using a new programming language I totally know nothing about it!!!
I am not sure about my decision... but I would like to take the risk....2 -
Oh the beauty of WYSIWYG etitors...
I don't know which one I'm more amazed of. All that beautiful styling for a simple line break or that incredibly accurate and absolute neccessary line-height value.
I guess it's time for a strip tag massacre.4 -
I just logged into my bank account to see that everything has changed. More basic, primitive styling and in general it is shit. Why am I ranting about this, because I could tell from looking that it has been done to be more mobile friendly. Sure enough I resized the screen and everything snapped into place like it would on a mobile.
Now I've got to put up with an inefficient and more time consuming UX all because some twat in the bank has decided to pander to mobile devices nearly ten years after they've been introduced even though there's already a mobile banking app for that.
Responsive design is like living with a dwarf, because one of you is small, nobody else is allowed to have cupboards on walls anymore. Bastards!4 -
What is the point of a CMS if you are gonna do every page custom with no common functionality or styling? FML
-
Me: Why did you exit the build?
Webpack (W): Build exited with code 2 - Eslint error at 2:1 in *filename*.scss 'Expected 2 line indent'
Me: internally *ARE YOU KIDDING ME?!?!?!? YOU FAILED OVER AN ESLINT STYLING!!!* *curses out original dev profusely under breath while fixing styling*4 -
Finally fucking managed to setup quite fast map tile hosting including the tile generation after ages of research and trial and error.
I love this open (source) maps (openstreetmaps) project but man, figuring out what to do from a gazillion sources can be rather hard.
Now I'm just having some styling issues and the filesize is fucking insane (only the Netherlands with all data, 20gb+ if I remember correctly) so I'm just generating road maps for now. If someone knows some more about the styling as for the maps, please let me know!
Yeah, this is fucking satisfying.2 -
So recently my open source project took off and got trending on GitHub (680 starts and 225 forks). This was the first time a project of mine really gained some traction and invested more of my time and weekends to maintain this project - I wrote comprehensive docs, contributing guidelines and reviewed PRs and made sure I commented on every single one of them. Sure, it isn't easy to review 50 PRs a day after coming home from work but the excitement of seeing this project becoming trending fueled me.
First 2 weeks it was good. I would come home from work and have dinner and sit down to maintain the project. Whenever contributors would be stuck, I would help them and write comments on each PR.
But the problem started since last week. People just really want to see their contribution activity graph get populated and hence they would make stupid PRs and literally no one followed contributing guidelines - I mentioned in that that the code should adhere to Pep8 styling but no one gave a shit. Each day I would spend reviewing PR with crappy formatted code and no sign of Pep8, and even some will just file PR and add a fucking docstring to every function or add paragraph of comments. Also, the PR quality was bad with unsquashed commits amounting to 10 or 20 or even sometimes 50.
I wrote the contributing guidelines doc and in that I mentioned every source that contributors could find helpful like how to squash commits, how to file a PR and Pep8 and not to write useless comments. Seriously people, grow up!6 -
A back-end developer at my company thinks CSS is easy, tries to fix some styling by himself without consulting front-end developers and messes up the styling of multiple web apps that rely on those styles. The next Jira ticket related to fixing those styles is, of course, assigned to me (with the highest priority)...
FML2 -
Witch hunting:
I just spent the last 90 trying to fix a visual bug with the UI
I made a functional component to render pretty forms with minimal information in React
Turns out some random ass fields were not rendering with their respective lower borders
Refactored the shit out of the components
Actually got them to follow a strict styling
Two cups of coffee later it clicked: everything was perfectly functional, I just have a shitty small monitor and tried zooming in
WOULD YOU LOOK AT THAT, IT'S THE FUCKING BORDER I WAS LOOKING FOR ALL ALONG!
Don't be like me: check les differents view ports5 -
When you've been working on styling most of the day and you later have something you really need to tell a friend and type !important at the end of it by accident 😑2
-
Interviewed for a Q&A position.
Found bugs and errors on the test questions just fine.
Found broken assets and errors within the test itself outside of the questions. (Misspellings, typos, broken images, botched styling, etc.)
Didn't get hired because they thought I'd spend too much time finding bugs.
What gives?7 -
Client says the styling of a particular component on their website is wrong. It looks fine to me. They can't give me an example of how it should look, or tell me what's wrong with the way it looks currently, but they want me to fix it.3
-
About every project at my last job. Impossible to like any project with a boss that legitimately thinks frames and tables are a better option than learning css.
But why not, attribute styling on html-elements are the future indeed.7 -
Why would someone in their right mind change a piece of code that was working fine (and it wasn't a complete mumbo jumbo in styling, logic, transparency, was in line with how the project was coded etc..) to use dapper just to call a stored procedure?! Dafaq is wrong with people!?
Or is it just me & I'm overreactig again?!
I hate when people add more stuff to projects that are already overbloated with fw/techologies to do something so trivial.. like adding 6827646 js fw so you can use one function in each (or are simply still there because they didn't know how to use it and left it in project) which could easily be achieved with our own fw we use...wtf?! O.o
// me cringing, cussing etc..4 -
A little late but whatever.
About half a year ago, I started working on setting up self hosted (slippy) maps. For one, because of privacy reasons, for two, because it'd be in my own control and I could, with enough knowledge, be entirely in control of how this would work.
While the process has been going on for hours every day for about half a year (with regular exceptions), I'll briefly lay out what I've accomplished.
I started with the OpenMapTiles project and tried to implement it myself. This went well but there were two major pitfalls:
1. It worked postgres database based. This is fine but when you want to have the entire world.... the queries took insanely long (minutes, at lower zoom levels) and quite intimate postgres/tooling knowledge was required, which I don't have.
2. Due to the long queries and such, the performance was so bad that the maps could take minutes to render and when you'd want that in production... yeah, no.
After quite some time I finally let that idea sail and started looking into the MBTiles solution; generating sqlite databases of geojson features. Very fast data serving but the rendering can take quite some time.
After some more months, I finally got the hang of it to the point that I automated 50-70 percent of the entire process. The one problem? It takes a shitload of resources and time to generate a worldwide mbtiles database.
After infinite numbers of trial and error, I figured out that one can devide a 'render' (mbtiles aka sqlite database) into multiple layers (one for building data, one for water, one for roads and so on), so I started doing renders that way.
Result? Styling became way more easy and logical and one could pick specific data to display; only want to display the roads? Its way more simple this way. (Not impossible otherwise but figuring out how that works... Good luck).
Started rendering all the countries, continents and such this way and while this seemed like a great idea; the entire world is at 3-4 percent after about a month. And while 40-70 percent generates 10 times as fast, that's still way too slow.
Then, I figured out that you can fetch data per individual layer/source. Thus, I could render every layer separately which is way faster.
Tried that with a few very tiny datasets and bam, it works. (And still very fast).
So, now, I'm generating all layers per continent. I want to do it world based but figured out that that's just not manageable with my resources/budget.
Next to that, I'm working on an API which will have exactly the features I want/need!13 -
I think I might change my middle name to "I told you so"
Couple of weeks ago I proposed integrating a daily process job into an existing WPF application (details of what+why would be too long to explain) and the manager suggested I make the changes
Me: "I can do it, but Jay has the most experience with that application. I don't have his WPF skills"
Mgr: "How hard can WPF be? If it uses the MVVM pattern, it should be a snap."
Me: "Its nearly an 8 year old WPF project with several chefs in that kitchen. I pretty sure I could figure it out, but that is a difference between 2 weeks and 2 days. Integration is pretty straight forward, Jay could probably do it in a day."
DevA: "WPF is easy. MVVM makes it even easier. I worked on the shipping app."
Me: "That's was a brand new, single page app, but yea, it should be easy."
DevB: "WPF has been around a long time and the tools have really matured. I don't understand what is so difficult."
Me: "I didn't say anything would be difficult, I know with that application, there is going to be complexity we need to figure out."
DevB: "It uses the MVVM, so all we need is the user control, a view model, controller, and its done."
DevA: "Sounds easy to me."
Mgr: "If you need more time to work on the vendor project, I'll have DevB work on the integration."
<yesterday>
Me: "How is the integration going?"
DevB: "This app is a mess. I have no idea how they got the control collections to work. If I hard-code everything, I can get it to work. This dynamic stuff is so confusing. Then there is the styling. Its uses dark mode, but no matter what I do, my controls show up in light mode."
Me: "The app uses Prism, so the control configuration is in, or around, the startup code."
DevB: "That makes sense. Will it fix the styling too?"
Me: "I have no idea. When I looked at it, some controls loaded the styles from the main resource, other's have it hard-coded. Different chefs in the kitchen, I guess. How far have you got?"
DevB: "I've created invoice button. That is as far as I got"
Me: "I'm finished with the vendor project and I'll be wrapping up the documentation today. I can try to help next week."
DevB: "Thanks. I think we might have to get Jay to help if we can't figure this out."
Me: "Good idea"
Two weeks and only a button. A button? I miss Delphi.3 -
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 lines9 -
So lets start here, as i have been preparing myself for a while for that rant. I have been putting it off for a while, but today I had enough.
Fuck react-native and fuck facebook react-native team. Bunch of lazy incompetent twats.
The all amazing framework that suppose to be speed up your development process, since you don't have to compile your code after each change. SO FUCKING WHAT if the god damned framework is so fucking buggy and so fucking shit that you constantly have to fix build, dependancies etc issues. Every day since I work on this project that is using react-native I have to deal with some of the react fucked up behaviour. You got an issue ? don't worry google it just to find out that 100 other people had the same issue. Scroll through down the bottom of the page just to find out that facebook devs have closed the issue as resolved (without fucking fixing it) because there wasnt recent replies to the post. Are you fucking kidding me? It's ok thou, create a new issue just to get an automatic reply from the bot that locks the thread and keeps it locked till you update your React-native version to the newest one. You do that and guess fucking what? Their newest version fucks up remote debugging on iOS(fucking android been broke for over a year) so say good bye to debugging your js code. Documentation is fucking trash. You found a nice function like autoCaptialise on your text input? Great! Ah wait, its not fucking working, what is wrong? You google this just to fucking found out it, function never worked on android, so why the fuck you still have it exposed and still have it in your docs? You want to add package? So fucking ez, just type npm install <name of the package>. Ha! fuck you, you still have to go and add them fucking manually in gradle in android and in pod in xcode, because obviously react-native is a one big fucking bullshit. Oh and a scroll view is a fucking glorious highlight of that framework, try add some styling to it, you gonna have loads of fun. Fuck react-native. And fuck the fucking idiot who convinced my boss that framework is so fucking great and now I have to work on this shit. Sincerely Xamarin Developer.9 -
I am just sick of the things that's been going on.
Joined a mid level startup as full Stack developer working on angular and node js . Code base is too shit and application is full of bugs(100+ tickets are being raised for bugs)
Since the product owner(PO) wants to demo the application he is pushing for bug fixes.
UI code:
1. Application is not handled for responsiveness all these years, it is now being trying to address. Code base is very huge to address though .
2. The common reusable components of UI has business logic inside. Any small change in business logic we are forced to handle in common components which might break up on another components.
3. Styling in 40+ components are made global. Small css change in component A is breaking up in component B due to this
4. No time to refactor.
5. Application not at all tested properly all these years. PO wants a stable build.
6. More importantly most of developers have already left the company and we are left with 2 developers including me.
I am not in a position to switch due to other commitments adds up a lot to frustration11 -
Why do people feel so compelled to create their own custom components when the component library you're already using HAS ONE ALREADY?!
You can change the styling and animations using CSS and props. Stop building buggy shit from scratch.7 -
Client: I just want a very basic modification, something a skilled developer could do in a couple hours.
Me: sounds great, can I look at your requirements?
*sees user-defined fields, workflows, navigation, roles, styling, customization everywhere*
D:3 -
IM DONE
BORED WITH WRITING CSS
Don't get me wrong. it's a beautiful styling language. I know how to use it, I've been even teaching it.
I'm just damn bored writing css
writing a ".", then a damn class name, "{}" and "color:shit"
BRO IM DONE
.ME{
STATUS: "DONE WITH WRITING CSS"
}13 -
My most intense day was in the company at the day we had to publish a website containing lots of jQuery & CSS animated stuff.
We planned to go live at 3pm but due to the fact that before lunch time there began to appear more and more styling and animation problems, we went live at around 9pm. I was sweating and nervous as hell the whole time.
At least my boss and I went to drink a few beers right after that. ;) -
My top 3:
* Inline styling instead of creating a class.
* slapping the new class at the end of a 700 LOC CSS file.
* Using !important14 -
Im getting annoyed by the new layout of google. Hovering the sidebar will make a scrollbar appear but the main part of the site's scrollbar will disapear. This results in most content moving from their original place. Let's make a Stlyish script to fix this problem I thought. Guess what now somethings stay where they should be, but the things that were first on the right place have moved. Also this will make the header shorter. I'm getting more and more amazed how shitty some frontend devs are at google.
To fix one bug they, instead of solving the bug, tried to counter the result of the bug.
I do like the z-index of the sidemenu though (it's 2005, the year youtube was created)12 -
WTH...
While styling some frontend stuff with LESS, I experienced that on one page template the <header> was not displaying the given line-height eventhough the whole fscking code was 1:1 identical with the other template in which everything was fine. I checked EVERYTHING... caching, URL, source, classes, open / wrong tags, HEAD, ... I even did a diff compare. NO FSCKING DIFFERENCE!
After one hour of pulling out hair I suddenly saw that in the faulty template file 2 lines were missing:
<!DOCTYPE html>
<html lang="devRantLang">
WHOEVER DID THIS: YOU ARE FSCKING STUPID!!! (it was me...)7 -
So I just was invited to look at an internal issue at a company that has modified BEM styling rules for their website, because the website started looking very weird on some pages..
I instantly knew that someone had to have fucked with them, because theres no way margin--top-50 all of the sudden isn't working.
Looked at their git history and apparently a senior approved a juniors styles change, where he modified things like margin--bottom-0 to be 500px or block--float-left to be float: right in specific containers with an id like "#uw81hf_"
WHY DO YOU APPROVE THIS GARBAGE WITHOUT CHECKING IT?! AND HOW DID THIS PASS A SECOND CHECK?!!! WTF -
I am a junior web developer, currently working in my first job for a small company, I was hired because I have an interest in meteor and modern web dev.
When I say small I mean I am the only full time js dev.
So the project we are working (my first ever professional project from start to finish) is a travel booking web app (being a little vague, for the sake of privacy). I am the lead developer, as a new programmer of a project that is far from trivial. There are no other javascript devs in office, no sort of code review. We have an outsourced dev but as I got in a flow with one dev my boss supposedly told him to do it part time (without discussing with me), but haven't heard anything from him, so assuming he's just disappeared (probably annoyed at being treated like a commodity).
Boss has set up the stages, and forces me to move on to the next stage before that stage has been finished. I will have to go back over the whole thing to finish things off.
He will only hire cheap juniors, one front end guy with barely any experience is styling the site.
He is used to churning out WordPress and Magento sites.
Wish I had a senior I could learn off.
I want to stick at this project and see it through, but i can only see it ending in a train wreck.
At the same time I want out, I want to work under a better team with senior programmers and better code review.
I just have to do my best and see how it goes I guess6 -
Client: The new page template you sent us looks different on production compared to the other pages that use the same component.
Me: Oh, that's strange since the styling is at the component level. Hmm, let me dig in to it.
Start poking around trying to figure out what I managed to screw up only to find that it looks exactly the same on local and staging. Eventually find another style sheet the client is importing on the production site to change some of the styles.
You know, a change that isn't anywhere to be found in the repo, and no one ever asked for anything to be changed. Their "Dev" decided he would hack in a fix instead of shooting me an email.
Apparently he tried changing the SCSS file but the changes weren't showing up. He changed the minified stylesheet but his changes were overwritten on the next deployment..... #howdoesSASSwork?!
Same client as my last rant so I'm not sure why I'm surprised by this. Oh well, I'll take that hourly rate.1 -
Hey everyone!
I'm on the hunt for new and exciting languages!
I'll state the ones I already know:
Python, Haskell, C(++), C#, Java, JavaScript, Ruby, Rust, Lua, about every kind of Basic, some branches of Lisp, BrainF**k, assembly, Octo (Chip-8) and GML(basically JavaScript).
I've also learnt some styling languages:
Html, CSS, Markup and Markdown.
Some misc languages too: Regex and a runny bit of the Wolfram Language.
Also I'm kind of limited to Windows, Linux and Android, as I do not own any Apple hardware except I have access to an old iPad, so are languages like Swift still good?
Thanks!28 -
Why, for the love of all that is good, does anyone still code for absolute placements in css?!
I've spent 90%+ of my time lately making some changes, which is about 20x harder than it needed to be because this app (written in the last 1-3 years) has all of the styling set explicitly. How does anyone justify that?8 -
I bought a domain and need some styling suggestions.
it basically demonstrates how language barriers can hurt communication (and I want to screw over google)
so, it takes a phrase and translates it to a bunch of random languages with google translate to see how messed up it gets.
the link is:
https://translationiteration.com
READ BEFORE CLICKING: i still have an unresolved bug with php cookies and sessions so once the page loads, just press refresh ¯\_(ツ)_/¯
so now i need some styling suggestions, and advertiser suggestions (i’m thinking media.net) who respect user privacy and are contextual.
comment :)
p.s. does anyone still say advert or am I the only one ? 🙃20 -
"Hey guys, we should start using ESLint. It's a popular linter. There's 13,000+ styling inconsistencies it could streamline using `--fix`"
"Yeah... But these errors, they're not really errors, right? So, we don't need to fix them."
...
1. I never said they were errors. Do you know how a linter works?
2. Sure, I guess being consistent and familiar are overrated qualities of a codebase. Carry on!4 -
Never had a coding style argument because my workplace doesn't have any standards, mix of C# and VB sure why not, 2K line VB service with 6 comments total? Sure no problems there.
The only styling we have is our personal preferences, except when it's my projects, then every adheres to the styles I set because I won't merge their 800 line monstrosity of a file with 18 classes.9 -
5000 scss file with the name global.scss styling.
How fucking dumb can you be to fucking mess up a clean component based architecture like Foundation or Bootstrap and fill it with shit in a single file.
No wonder WP gets shit. The legacy code is usually shit.
And to put the shit cherry on top. This motherfucker had a settings.scss file with all general components and he never used it.
Fucker put different font size in px everywhere! Fucking asshole!!! -
Around 6 years ago I started at this company. I was really excited, I read all their docs then I started coding. At every code review, I noticed something was a little off. I seemed to get lots of weird nitpicking about code styling. It was strange, I was using a linter, I read their rules but basically every review was filled with random comments. About 3 months in I noticed, "oh! there aren't actually any rules, people are debating them in my code reviews!" A few more reviews went by and then I commented, "ya I'm not doing any of this, code review isn't a place to have philosophical debates." All hell broke loose! I got a few pissed off developers, and I said, listen I don't care what the rules are, you just need to clearly fucking articulate them and if you want to introduce one, I don't care about that either just don't do it in the middle of my review. I pissed off 1 dev real bad. Me and this dev were working together, the QA person on the team stood up and said "hey! you know what I love about your code reviews?!" The other dev and myself looked at each other kind of nervously, "I love that you're both right, these are all problems!"... 1 year later (and until now) me and the other dev are still friends. Leave it to QA to properly identify the bug.
-
I'm really not sure. When I was 7-8 years old, I liked to view source in IE, then I somehow managed to use Javascript in the browser. First only some dumb opening of windows. And I liked Batch, so I made some files for copying, backup and stuff.
Then I got to PHP during the years from some online tutorial about making dynamic websites. My website was more static than stone, but yeah, I did page loading with PHP! Awful experience anyway, because I had to install Xampp, get it work and other stuff. 11 years old or so. (and I used Xampp only as a fileserver between laptop and desktop later, because.. PHP4... just no.)
As 12 years old or so I experienced my first World of Warcraft (vanilla) on a custom server in an internet cafe and I thought it's a singleplayer game. When I found out that no, I googled how to make my own server (hated multiplayer back then and loved good games with huge storylines). Failed miserably with ManGOS, got something to work with ArcEMU. There I learned some C++ basic stuff, which I hoped would helped me to fix some bugs. When I opened the code I was like: "Suuure." and left it like that. I learned what a MySQL database is, broke it like four times when I forgot WHERE and still rather played with websites i.e. html, css, js and optionally php when I wanted to repair a webpage for the server. With a friend we managed to get the server work via Hamachi, was fun, the server died too soon. Then I got ManGOS to work, but there wasn't really any interest to make a server anymore, just singleplayer for the lore. (big warcraft fan, don't kick me :D )
I think it was when I was 13y.o. I went to Delphi/Pascal course, which I liked a lot from the beginning, even managed to use my code on old Knoppix via Lazarus(Pascal). At this age I really liked thoae Flash games which were still common to see everywhere. So I downloaded .swfs, opened and tried to understand it. Managed to pull some stuff from it and rewrite in Pascal. Nope, never again that crap.
About the same time I got to Flash files I discovered Java. It was kind of popular back then, so I thought let's give it a try. I liked Flash more. Seriously. I've never seen so much repetitiveness and stupid styling of a code. I had either IDE for compiling C++ or Pascal or notepad! You think I wanted my code kicked all over the place in multiple folders and files? No.
So back to Pascal. I made some apps for my old hobby, was quite satisfied with the result (quiz like app), but it still wasn't the thing. And I really thought I'd like to study CS.
I started to love PHP because of phpBB forums I worked on as 15 y.o. I guess. At the same time I think there was an optional subject at school, again with Pascal. I hated the subject, teacher spoke some kind of gibberish I didn't really understand back then at all and now I find it only as a really stupid explanation of loops and strings.
So I started to hate Pascal subject, but not really the lang itself. Still I wanted something simpler and more portable. Then I got to Python as hm, 17y.o. I think and at the same time to C++ with DevC++. That was time when I was still deciding which lang to choose as my main one (still playing with website, database and js).
Then I decided that learning language from some teacher in a class seriously pisses me off and I don't want to experience it again. I choose Python, but still made some little scripts in C++, which is funny, because Python was considered only as a scripting lang back then.
I haven't really find a cross-platform framework for C++, which would: a) be easy to install b) not require VisualStudio PayForMe 20xy c) have nice license if I managed to make something nice and distribute it. I found Unity3D though, so I played with Blender for models, Audacity for music and C# for code. Only beautiful memories with Unity. I still haven't thought I'm a programmer back then.
For Python however I found Kivy and I was playing with it on a phone for about a year. Still I haven't really know what to do back then, so I thought... I like math, numbers, coding, but I want to avoid studying physics. Economics here I go!
Now I'm in my third year at Uni, should be writing thesis, study hard and what I do? Code like never before, contribute, work on a 3D tutorial and play with Blender. Still I don't really think about myself as a programmer, rather hobby-coder.
So, to answer the question: how did I learn to program? Bashing to shit until it behaved like I desired i.e. try-fail learning. I wouldn't choose a different path.2 -
Somebody in Microsoft is playing with Github.com styling. Everything is broken from the last few hours.1
-
i spent two days fixing some bs styling made on our platform. this guy put redundant attributes in the classes and the elements themselves and instead of using :hover he just created hover with jquery. i stared at my screen for 10 minutes when i saw that. the worst part is he was not dumb, so how 🤦♀️9
-
Apart from linux, it has to be vue.js, quasar and express.js
Vue.js had made my development extremely easy, faster and managable
Quasar brought great Styling and various other powerful features to vuejs. Thus helping save even more time
And express.js don't need any explanation. Better code organization and easy to get started. -
A legacy custom made WordPress Theme.
Old developer made main styling sheet with 8000+ lines of code with no component separation. -
HEY REACT NATIVE I WOULD REALLY LIKE IT IF YOUR FUCKING STYLING AND KEYBOARDINAVOIDINGVIEW WOULD MAKE SENSE JUST FOR ONCE TODAY I'VE HAD ENOUGH OF YOUR SHIT WORKING +100 HOURS THE PAST TWO WEEKS I DONT NEED MORE OF IT NOW REEEEEEEEEEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
-
Them: You have 6 days to build this frontend page for our wordpress site.
Me: Ok...
*proceeds to spend 4 days trying to arse my way towards a semi reasonable bootstrapped website based on the existing website's styling.*
Me: *Presents website*, so... uh... yeah, I don't usually do frontend stuff, I'm more of a backend dev, but here's what I could do.
Them: This looks like absolute horseshit.
Me: So what do you not like about it?
Them: All of it. It doesn't look anything like the wireframe that I gave you.
Me: Ok... So let me get this straight, you want it to look exactly like how you designed it in your wireframe? *wireframe looks like a child drew it*
Them: Yes! Is that so hard?
Me: I mean, it's a little hard. I'm not exactly a front end developer. Aside from that, I think this design is not very user-friendly.
Them: we don't care about your opinions, OP. Get back in there and make it look exactly like the wireframe.
Me: Ok.
*proceeds to go to fiverr, and contract someone else to do it for me while I get to do fun stuff in the back end.* 😂
----
We'll see what they think of the project when it gets back to me. Wish me luck guys.1 -
I have never encountered a codebase so horrendous. The styles are so fucking bad.
Give me a codebase with a poorly implemented programming langauge, fine.
Give me a codebase with styles that have been copy/pasted off Stackoverflow a million times until something works, not fucking fine. -
I was minding my own business, fixing merge conflicts for my project lead when it struck.
There, in the middle of a React.js component, was a table, used not for displaying data, no, but for styling a form, which was not a form, but a series of table rows.
I feel sick -
Client: I need you to integrate with this API.
Me: ok cool, but what are we doing with it (where does the data go/styling)?
Client: what do think we should do?
Me: well it would be really cool if we did it like this *short and sweet explanation of really cool functionality and design*
Client: I LOVE IT! Let's do it, oh also I need it done by tomorrow...
Me: *GOD DAMNIT, why do you always do this...don't you dare say ok* ok, yeah I can totally do that.
...now at the market stocking up on redbull2 -
What in the fuck is the Roger's website built with? It takes way too fucking long to sign in and load my account. And there is a modal that pops up asking me which account I want to view when I sign in. 5 seconds later the styling for it finishes loading and the modal snaps down like 50 pixels, so right when I'm about to click one account, I accidentally click the wrong one. For such a large company, I would have hoped their shit wouldn't have been built by fucking idiots.
-
when CodeClimate reports it 2.0 GPA but your colleagues says it's good code-wise and styling wise...
turns out I didn't have the YAML override -
The longer I work on front-end the more controversial my opinions become:
- Styling a button with display:flex is dumb.
- The DOM is not hard, unlike what the React team wants to have you believe.
- Specifying a <form> action matters, even if it's empty
- ES5 was the real JS revolution, ES6 mostly sugar-coated marketing
- Disciplined BEM (S)CSS is simple and flexible enough for most needs (vs CSS-in-JS, CSS modules)
- If editor support for Jsdoc were as advanced as Typescript, you wouldn't need the latter.
- There are cases where using floats and inline-block displays is better than the flex CSS box model12 -
Not caring about code styling and just committing because whiny people annoy me. It works; it works. I should probably abid by code styling standards and do a precommit but bite me 🖕🖕🖕2
-
Every sufficiently advanced ui kit is indistinguishable from a half-assed html5 browser.
I think styling languages were the mistake of all time. And that we should go back to artists implementing themes on top of 9slice technology.
Fight me.5 -
This might just be me and my OCD talking, but am I the only one who gets super annoyed with sloppy CSS formatting?
So like, if somebody writes a sloppily formatted rule like this without spacing out each property and value:
#signUpButton {color:#FFF;background:#000;float:right;clear:both;padding:5px;position:absolute;top:5px;right:20px;height:100px;width:45px;}
As opposed to something like this, which just looks much cleaner:
#signUpButton { color: #FFF; background; #000; float: right; clear: both; padding: 5px; }
The formatting makes no difference in how the CSS is evaluated and rendered, but I find the spaceless style so ugly and difficult to read/edit, whereas the spaced out style is much more appealing to the eyes and easier to read
I find myself reformatting other people's CSS that works perfectly fine just so it will be easier to read/edit for anybody else that looks at it in the future8 -
So apparently south korean maps are top secret and do not allow for styling in google maps:
"Yes , Korea does not support some features offered by Google Map due to national law. Google Map Korea can not be export map data for data centers abroad or including the ability to dynamically change the map image. Many South Korea Maps and services are limited to the domestic uses and Google is striving to make this a better service."
sources:
https://snazzymaps.com/help
https://stackoverflow.com/questions...
https://productforums.google.com/fo...3 -
No matter how many times, or whichever way I explain, he still doesn't get it. Are people so fucking blinkered they do not want to listen, or even read what you write. Back story, produced some web design visuals for a client, and fortunately he had the good sense to listen and employ a copywriter. She had the first draft done when i was putting together the styling, so i placed actual copy on the visuals. 2 weeks pass, still no answer. I send the same email to him, every 4 days and cc his PA for good measure. Finally, he says he wants to make some tweaks to the copy. I explain that any copy changes can be done via the CMS once the site is built, and can I proceed and build the site? He replies I need to make changes to the copy first. I explained again about the difference between the visual and the actual website, same response. You Fucking Infuriate me! Cunt!
-
the more i learn about web dev, the more i realise the reason for its mess up . There are 2 major problems in it : the people who create various important concepts and tools for web dev were 1) working on it without any collaboration and agreements on the philosophy and 2) were too stubborn on their ideology i guess.
There is no limitation to anything's functionalities, and the limits that are "defined" are badshit crazy. for eg:
====================================
HTML creator : "I am gonna make a language that would provide a skeleton to web page. it will just have the text and basic markers to let the scripting and styling engines/languages know which text is supposed to be rendered and how.
It won't provide any click or loading functionality.
someone: "So i guess opening a page or loading an image would be handled by JS or other programming language? also, bold , italic or division would be added via CSS?"
HTMLguy : Nah, my html engine would ALSO do that.
someone : what , why? won't that just be stupid and against your philosophy?
HTMLguy : WHAT? am too awesome, can't hear you
w3c , 50 yrs later : sorry can't change this, gotta support the 50 yrs of web dev and billion sites
=================================
CSS guy: I am gonna make the world's best beautifying stylesheet language to provide colors, styling, fonts and backgrounds to a page. every loadings and clicks would be handled somewhere else
Some1: cool, then clicks, hover and running of animation would be handled by JS only
CSSguy :Umm, i guess i could handle those.
Some1 wha-?
CSSguy : Thankyou Thankyou Thankyou for the nobel price!
====================================
JS guy : I am gonna make a god web programming language! It can do everything: add/remove html tags, add styling, control animations, control browser, handle clicks , perform operations, everything!
some1: cool! you must be making very large programming language with lots of modules.
JS guy: No! i am gonna keep it small. no built in classes and file imports! just use the functions directly. if someone wants the additional lib functionality, install them on your server
some1 : innovative! what's typeof NaN ?
JSguy :shut up.6 -
Long story ahead
Background:
I recently started a job in a smallish startup doing web development in a mostly js stack as an entry-junior engineer/dev. I’m the only person actively working on our internal tools as my Lead Engineer (the only other in house dev) is working on other stuff.
Now I was given a two week sprint to rebuild a portion of our legacy internal app from angular 1.2 with material-ui looking components with no psd’s or cut-outs of any kind to a React and bootstrap ui for the front end and convert our .net API routes into Node.js ones. I had to build the API routes, SQL queries (as there were plenty of changes and reiterations that I had to go through to get the exact data I needed to display), and front end. I worked from 9am until 11pm every day for those two weeks including weekends as our company has a huge show this upcoming week.
I finish up this past sunday and push to our staging environment. The UI is 5.5/10 as we’re changing all of our styling to bootstrap and I’m no ui expert. The api has tests and works flawlessly (tm).
So we go into code review and everything is working as expected until one tab that I made erred out and was written down as a “Needs to be fixed.”
This fix was just a null value handler that took three minutes and a push back to staging, but that wasnt before a stupendous amount of shit being flung my way for the ui not looking great and that one bug was a huge deal and that he couldnt believe it slipped through my fingers.
Honestly, I’m feeling really unmotivated to do anything else. I overworked myself for that only to be shit on for one mistake and my ui being lack-luster with no guides.
Am I being a baby about this or is this something to learn from?1 -
Where do I start...
I have seen a QA load local code to a machine, run it and then say it was ready to deploy. Little did we know she wasn’t following the deployment process at all and didn’t even realize she had to. We were a week trying to figure out why the deploys wouldn’t work until she spoke up.
I knew a dev/founder that said to me “source control is only for large projects”, I tried to convince him and his cofounder to use github or bitbucket. Nope, they weren’t into it (fresh out of school listening to professors who hadn’t worked a development day in 20 years) One cofounder got disgruntled, thought he was doing most of the work and decided to quit, he also decided to wipe the code off his co-founders machine. I literally saw a grown man come out of a meeting crying knowing he would never gain back the respect of those mentors and advisors.
I once saw a developer create a printed ticket receipt for a web app. Instead of making a page and styling it to fit a smaller width, he decided to do everything in string literals. More precisely, he made one big long fucking strong literal and then broke it up using custom regex to add styling to different sections. We had a meeting and he was totally convinced this was the only way. In the end we scrapped the entire code and the dude didn’t last very long after that.
Worst of all! I once saw a developer find a IBM Model M keyboard and said “I’m gonna throw out this junky keyboard”. I told him to shut his stupid fucking mouth and give the the keyboard.
He did -
ChatGPT, Copilot, React, how to make a link in a frontend website?
To create a link in a frontend website, create a span, a div, or a paragraph that contains the link text. In your JavaScript web app, add an event listener to that element that opens the link on click. If you want to claim you're accessible, add an aria-role to the clickable element. To make debugging harder and only possible for the real arcane experts, let your framework generate generic ids and class name hashes for styling and event handling, like "item_09fcfck" or "elementor_element_foo_bar". Avoid, at all price, to use an a href element!2 -
When you explain thoroughly and in no uncertain terms that yes you can help your mate out at short notice by building a working prototype of his app, but that it won't even be MVP. It will be bare bones functionality with no design, almost no styling, no images, no color - but it will work in so much that it will do what it needs to do to show that it's possible.
Then he sees it and goes "it doesn't look great, can it not animate or at least have nice images and a color palette. Would it be possible to have filters on the search or I dunno, just make it look a bit more finished?"
Me: nope, but if you want I can delete the whole thing?5 -
Styling can be diffucult. You have the most beautiful idea for a masterpiece layout in mind. You begin to work on it and goes from 'very nice' to complete disgust..3
-
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_u12 -
Tailwind css offers a premium package where you have to pay $300 for access to their tailwind styling components. And even additional $150 and $150 and $150 packages depending if your app is for ecommerce application ui or marketing etc.
WTF????
While in Angular Google has provided 100% FREE MATERIAL DESIGN UI COMPONENTS
WHO THE FUCK PREFERS TO CODE IN REACT/NEXTJS/VUE over ANGULAR???23 -
When I was in 6th grade, and we were learning HTML, and I realised the power my fingers suddenly held as Chrome (ugh) loaded up my frst webpage with some basic styling. At that moment, I understood the extensibility, the dyanmicity (My English teacher would kill me), the pure awsomeness I could do with a text file. In three years (now), I finally made a calendar that works which has comments, is split into dedicated files, works, is clean and written in D, and works.
-
So last year I started a project, and gave up after 8 months (was an unemployed student, and made my todo list wayyy too long)
Turns out, over those 8 months I wrote over 13.5k lines of coding/ styling, while also spending a couple months revising for, and taking my GCSE exams where I didnt do any programming.
Somehow I was averaging around 2k lines a month and I wish I had that productivity still.3 -
OH MY FUCKING GOD. I HATE
H A T E
ACQUIA SITE STUDIO.
"Let's make a low-code 'solution' for developers who barely can stand working on Drupal as it is, and make the completely easy and perfect process of styling a website, COMPLETELY UNBEARABLE!"
Yea this is a great idea, experienced developers can now spend hours trying to fucking find where a single style is coming from. Oh it was too easy to cmd+f a stylesheet or a codebase to find something particular? Yea FUCK THAT. Lets turn EVERY SINGLE STYLE into a unsearchable .yml file where every style definition is now a machine hash. WAY easier to use. Isn't it so cool to fucking click on styles from a dropdown where they come off the edge of the screen. FUCK whichever stupid fuck came up with this dog shit nonsense. I fucking HATE this soul crushing work.2 -
Good code is a lie imho.
When you see a project as code, there are 3 variables in most cases:
- time
- people / human resources
- rules
Every variable plays a certain role in how the code (project) evolves.
Time - two different forms: when certain parts of code are either changed in a high frequency or a very low frequency, it's a bad omen.
Too high - somehow this area seems to be relentless. Be it features, regressions or bugs - it takes usually in larger code bases 3 - 4 weeks till all code pathes were triggered.
Too low - it can be a good sign. But it should be on the radar imho. Code that never changes should be reviewed at an - depending on size of codebase - max. yearly audit. Git / VCS is very helpful here.
Why? Mostly because the chances are very high that the code was once written for a completely different requirement set. Hence the audit - check if this code still is doing the right job or if you have a ticking time bomb that needs to be defused.
People
If a project has only person working on it, it most certainly isn't verified by another person. Meaning that only one person worked on it - I'd say it's pretty bad to bad, as no discussion / review / verification was done. The author did the best he / she could do, but maybe another person would have had an better idea?
Too many people working on one thing is only bad when there are no rules ;)
Rules. There are two different kind of rules.
Styling / Organisation / Dokumentation - everything that has not much to do with coding itself. These should be enforced at a certain point, otherwise the code will become a hot glued mess noone wants to work on.
Coding itself. This is a very critical thing.
Do: Forbid things that are known to be problematic in the programming language itself. Eg. usage of variables in variables, reflection, deprecated features.
Do: Define a feature set for each language. Feature set not meaning every feature you want to use! Rather a fixed minimum version every developer must use and - in case of library / module / plugin support - which additional extras are supported.
Every extra costs. Most developers don't want to realize this... And a code base that evolves over time should have minimal dependencies. Every new version of an extra can have bugs, breakages, incompabilties and so on.
Don't: don't specify a way of coding. Most coding guidelines are horrific copy pastures from some books some smart people wrote who have no fucking clue what you're doing and why.
If you don't know how to operate on people, standing in an OR and doing what a book told you to do would end in dead person pretty sure. Same for code.
Learn from mistakes and experience, respect knowledge from other persons, but always reflect on wether this makes sense at this specific area of code.
There are very few things which are applicable to a large codebase on a global level. Even DRY / SOLID and what ever you can come up with can be at a certain point completely wrong.
Good code is a lie - because it can only exist at a certain point of time.
A codebase should be a living thing - when certain parts rot, other parts will be affected too.
The reason for the length of the comment was to give some hints on what my principles are that code stays in an "okayish" state, but good is a very rare state -
MaterialUI? Is it shit?
A brand new code base. Old codebase (old employees) used MaterialUI, locking in a lot of the styling and layout in their grids.
I'm trying to identify the pros/cons that can come from experience using the framework.
Some questions to spark discussion:
Anyone used this in production for a period of time?
Did it hold up? Did the designers hate it?
How was mixing this with SASS etc.
Cheers8 -
>Making final changes to site.
>Added an li to a ul which some onhover styling. Styling didn't take.
>Added styling separately to li.
>Worked.
¯\_(ツ)_/¯
> 24 hrs later.
>Friend checked site. No styling.
ಠ_ಠ
>Removed added styling.
>Worked.
??????????????????????????????????????????
(╯°□°)╯︵ ┻━┻4 -
So here's a question for all the front-end web devs. I'm mostly a back-end dev, but currently learning Angular 6 for a personal project I'm doing.
Didn't realize that styling isn't what Angular does (or maybe it does, and I just don't know), but that you should use some framework for styling too.
So the question is: What is most commonly used, is it bootstrap or something like that?4 -
Let me start this off by stating I'm a Java dev, and a noob with C++.
Thought it'd be cool to learn some OpenCL, since I want to do some maths stuff and why not learn something new.
So I sat down, installed Nvidia proprietary drivers, broke my x-org server, purged, reinstalled, rebooted and after a while I got stuff sorted out.
Then on to my IDE. I use CLion and it uses Cmake. C++ noob knows shit about Cmake, so struggle for two hours trying to figure out wtf is going on with the OpenCL libs and why they're only partially detected. Fml.
Finally, everything is configured and I'm set. I start working on a Hello World program using OpenCL. Finish it in 20 mins, all good. No output. Do some googling, check my program a million times. Nothing wrong here. Check the kernel, everything as in the tutorial.
I start checking error codes after a while reported by OpenCL (which I had no clue was a thing) and I get some code saying the program was not created properly (to run the kernel). No fucking clue what's up with that. Google around, find another tutorial, rewrite my code in case I'm using outdated code or something. Nothing.
Fast forward an hour, I find out that OpenCL has logs! So I grab some code from the website I found it on, and voila, I finally get some info on what's going on.
Get a load of this bs.
In the kernel file, so that OpenCL knows that it's a function to run, you have to put __kernel. But in all the places I read, it said to put it as _kernel.
Add the underscore, compile, run and everything is perfect.
Then I tried just putting 'kernel'. Also compiles and runs fine.
Two hours hours and my program was fixed by adding an underscore. IF ONLY C++ GAVE AN INDICATION OF WHAT BLEW UP INSTEAD OF SITTING BACK AND BEING LIKE "oh wow man feels bad, work some magic and try again" THEN THIS WOULD NOT HAVE TAKEN SO LONG.
Then again, it was OpenCL that was being shitty with its styling enforcement or whatever the hell the underscore business is. But screw it. C++ eats shit too for this. Sure, maybe Java babies you by giving you the exact error and position that the error took place at. But at least that way you don't waste hours of your life chasing invisible bugs 😠😠
I'm going to eat some food... Too much energy was consumed fighting the system... Then I'll get back to OpenCL because 😇 but that doesn't make it less bs.1 -
Is there any benefit of having custom input field dialogs, eg. for date and time? Should I be using just the HTML5 tags as-is (only styling the field itself), or create custom dialogs (creating custom javascript dialogs on top of basic text fields)?8
-
css frameworks are a sign your ui/ux team is an empty bag of chips.
vuetify examples look like toys in their docs and work that way in prod. if you put any two vuetify components together on a page you basically dont have a website anymore. mx px are indicators that your styling abstraction is so bad that adding 8 resize shims to every single node on the dom is the correct solution to your visual spacing dilemma.
css offers so many powerful tools out of the box now, and it takes like a week to actually learn them. instead, we cloak all the functionality and expressiveness of modern css in black-box m a t e r i a l d e s i g n and pretend like obtuse blobs are a viable substitute for coherent, accessible, user-friendly ux.5 -
WTF YOUTUBE
https://i.imgur.com/wsst8Rr.png
why was this instantly pushed to master without QAs !??!
why the fuck do you cripple the search bar ignoring screen size 100%
yeah good luck with the search bar on big screens
i get it, its googles unifying, but! https://i.imgur.com/rNVeQfP.png
It's done with the wrong rules. If you look at any other google suite product (take inbox for example) the search bar is scaled OVER the content, not placed above as a grouper.
https://i.imgur.com/g1ioT6c.png
I hope something was just forgotten in the CSS, because this is fucking bad. It doesnt make sense.1 -
Why do people use fucking IE/Edge, that makes Styling so fucking complicated, half of the things are not fucking supported, and these fucking clients want support for those damn fucking piece of shit browsers.
I just want to blow up every fucking computer which still has no other browser Except those pieces of shit.2 -
Another one someone reminded me of when mentioning !important...
When I first started trying to figure out how to customize Wordpress and spent a week trying to figure out how to defeat its reformatting of my styling preferences when editing posts, only to throw it in the corner and ignore it for the next four years. -
Hey. Need to beef up my portfolio as well as gain more experience.
If anyone needs some design/styling help or input please hit me up!!
Doesn't have to be paid actually.7 -
That feeling when you type out a hilarious response to someone's rant on DevRant, written with meticulous code styling, and then you realise formatting is ignored!
-
The lead UX person at my company wants to get rid of the focus outline in our web apps. Some other people want to change its styling to be less apparent and remove it from some places all together.
I'm trying my hardest to explain why it's there and how important it is to accessibility but I'm at the point where I just want to scream at them. -
Styling Newsletters is like time travel..time travel in a retarded past that doesnt knew what beauty modern css is, also fuck your sincerly MS Outlook for being a propritary cunt.
display:block will not work for MS Outlook, cause, well reasons.3 -
Telling my group mate that he needs to follow a styles guide. Not any particular one, but just one...
His response, “but why does it matter? It works”
Fast forward two days. I open my first PR at work, change requested because of styling. -
min-height: calc(100% - 1rem)
AAAAA REEEEEEEEE WHAT ARE YOU DOINGGGGGGGGGGG IF YOU DONT UNDERSTAND CSS DONT USE ITTTTTTTTTTT
so much pain / time could be saved if devs just used a damn framework (i don't care, bootstrap or tailwind, have at it which is better, i could care less). stop trying to be fancy, like this above, because its ultimately wrong. sorry i'm not sorry7 -
How do you tell people in your team their code is poorly written?
I am not an amazing developer, I lack experience of real world and don't have many finished products under my belt.
But I feel/think my code is well separated into separate classes, follows DRY well and is generally considered as following good practises.
However, the main Dev in this new small team which has been put together and I have been appointed to manage sees things differently.
He writes good functional code(it completes it main purpose) however it's all in the one program.cs file, lacks good comments and is just generally untidy :(
I kinda fell into this whole management thing and it's kinda new to me..
Maybe he just needs a bit of direction? I am going to be putting in a code styling guide
Any tips on managing a Dev team would be very much appreciated.
PS. Iv been around for a while, and did previously have an account which was quite active, however I decided to delete and create this new more anonymous account :P10 -
C# styling question: in a constructor do you prefer:
public MyClass(int MyVariable) {
this.MyVariable = MyVariable;
}
or
public MyClass(int _MyVariable) {
MyVariable = _MyVariable;
}
?22 -
This is a bit of a hard one, but...
Does anyone know how to make a markup language (with browser styling)?5 -
Q:
I'm making a dictionary/glossary for a website. Any cool open source solutions? Something like Wiktionary, but maybe a bit more styling than wiki's plain old black on white.2 -
Wtf looking at a Pull Request today for styling 4 buttons...
750 lines of of CSS and not even able to style an anchor!!
How the hell is that even possible!!!1 -
>start new job, not very professionally experienced dev
>spend couple of months working on a feature that is supposed to be an MVP kind of thing, be rushed to finish and told to cut corners because it's "just an MVP", still lose sleep and have relationship suffer (and ultimately ruined) as I try to not lose deadlines created by the boss with questions like "you can have this done by <very soon>, right?"
>frontend created by fellow developer is a garbled mess of repeated code and questionably implemented subpages, frontend dev apparently copies CSS from Figma and pastes it into new non-reusable React components as envisioned by designer, I am tasked with making sense of the mess and adding in API consumption, when questioning boss what to do with the mess I am often told to discard stuff that the frontend dev has made and just reuse his styling; all of this on top of implementing the backend feature that a previous developer wasn't able to do
>specs change along the way, I had been using a library as a helper in some part of the original feature, now the boss sees that and (without further testing the library) promises CEO that we'll add that as a separate subfeature, but the performance of the library is garbage for larger inputs and causes problems, is basically shit that might not have been shit if we had implemented it ourselves, however at this point CEO has promised new feature to some customers, all the actual sense of responsibility falls upon my hands
>marketing folk see halfway done application and ask for more changes
>everything is rushed to launch, plenty of things aren't implemented or are done halfway
>while I'm waiting for boss to deploy, I'm called up to company office by CEO, and get new task that is pretty cool and will actually involve assessing various algorithms and experiment with them, rather than just stitching API calls and endpoints together, it involves delving into a whole new field of CS that I never had the opportunity to delve into before
>start working on cool task, doing research, making good progress
>boss finally deploys feature I had been originally implementing
>cut corners of original boring insane feature start showing up, now I have to start fixing them instead of working on cool task, however the cool task also has a deadline which is likely expected to be met
I'm not sure if I'm having it bad or not, is this what a whole career in software development will look like?6 -
My last workplace would fit to that tag quite well.
CTO who was also in charge of firing / laying off people is a code nazi that forced everyone to use some absurd code styling. -
So I've been a developer at my current job for about 12 years. I am the most senior level developer at my job. Let me state that I am a backend developer although I did frontend development off and on as well for the first 5 years of my career. However I have done no major frontend development for around 7 years now.
Effectively our frontend developer of 6/7 years just left.
We had an existing project in the queue and my boss expected me to do frontend development for this project which I did just to help out, but I am not getting any extra pay for this and I absolutely hate doing it. The only thing I was paid for was I overtime for completing the project quicker. With that being said I feel like I should be paid substantially more since I am doing double work and since they are not paying for a frontend developer. I'm literally doing her job and doing a better job than she did mistake wise doing her job.
Additionally many things have changed over the past 6/7 years and they have it in their minds since I did it in the past it should be the same now which isn't the case. So there are things in my project queue right now for future projects that they think I know how to do and I don't. It isn't that I couldn't eventually figure it out. It is just that I have zero desire to learn it .I just absolutely hate styling websites.
I'm ok with doing minor frontend things for projects but not entire websites
I literally develop the backend off all the sites we build setup Google tag manger tags/triggers, Google analytics, search console, Google looker studio, dns, site updates, manage all out Linux servers, do seo for content and sites. I can't handle something else on my plate. I'm currently having to rewrite a ton of code as well due to upgrades for our sites.
How do I respectfully tell my boss I refuse to do frontend work going forward or pay me substantially more on another project and that he needs to hire someone else without damaging our relationship?
I like my boss and my coworkers as people a lot outside of work, but I feel like I'm being taken advantage of financially and I'm honestly tired of it. As a developer for 12 years I'm honestly ready to just go elsewhere. -
Is there a sane way to allow external styling of vanilla web components' shadow dom? Right now I do it by using 30 CSS variables, but I feel like there should be a better way.7
-
Was going to change some css in our application which ruined some styling with !important. Found the less file responsible for the !important...
... the front-end guy had made a variable @important to add !important on rules... -
Is it possible to base a custom GTK+ theme on Adwaita without having to compile a custom GTK+?
I planned on following https://worldofgnome.org/creating-g... to solve a scrollbar styling issue for myself.
But that guide seems to be horribly outdated as Adwaita seems to be fully compiled in as an engine now - for performance reasons, wich they obviously would never expect to matter to people using custom themes (because else they would have optimized the application of all themes in general instead)...2 -
DevFolio
This is a simple responsive portfolio website template. You can use it and make it yours by changing things and colours to your style and liking! I made it with a lot of hard work, love and of course with code :) I'm not a professional coder, but I tried my best to make it look cool and yet still keep it simple.
Mistakes are proof that we are trying!
I learned so much while making this template, if you use it, please let me know. I would love to see how amazing people can make it! I hope you'll like it!
I have used:
- HTML5 for markup
- Pure CSS3 for styling
- Bit of JavaScript to make a hamburger menu to work on mobile devices
- Font Awesome for Icons
- Unsplash for Images
You can add more things to make it even cooler! The comments in the code will help you navigate through it. Have a nice day! :D
you can view the Github repo at https://github.com/achaljhawar/...1 -
Some client coming back to me claiming some page "suddenly" changed style and fucked stuff up.
Yea, stuff like that totally happens. I'm like 90% sure someone messed with the styling... -
.light, .dark {
background-color: white;
}
I wish this was as bad as it got, the styling of this app is all over the place, but I can understand how it got this way. The app is very large and old, multiple people work/ have worked on it and add to it—not worrying about cleaning up after themselves.3 -
Holy shit how have I not tried using an SVG inside of a sudo element before. That's awesome and will save so much time styling global elements.
-
People who use word-break: break-all on body paragraph content need to stand in a narrow, claustrophobia-inducing room, cut off their left hand, and hold it up against the right-hand wall, while holding the stump of their left arm against the left wall. That's what it feels like to read break-all in longform content.
-
Implementing html template with inline styling into Typo3 for newsletter, I'm so fucking bored I'm looking for a cozy place where I can safely faint and lay there for some hours.
-
Finally got my multi-page dialog with stepper to have validation on every field based on a schema in a way that doesn’t totally mess up styling and that still collects information from fields from both pages to send the Graphql mutation.
So happy I could cry. -
I see a lot of articles/posts about the difficult of CSS.
Finding it hard to maintain, or resulting in spaghetti code.
Is this a common occurrence?
Whilst I've come across it in a few projects before, I wouldn't say it's a regular.
Now a lot of our sites are built on CMS' (Umbraco), but here's my approach.
I'll style the generic elements first across all pages
User generated content is usually in its own CSS class (for nested targeting, e.g. ul/ol tags)
Then I'll give each Document Type (post type/page type) it's own body class and apply specific styling to that page where needed.
Hopefully that's of help to some of you. I'm interested to hear your approaches to it! :)5 -
style="whatever styling brainfart the client has today that needs to be removed tomorrow once he realizes that it looks like total ass on anything that isn't his personal device".
-
This is from riot.im on my phone in Chrome. Somehow the rest of the site is fine, of all the places to fail at styling!
Also that's not very many languages to make a claim like that, I appreciate the effort but they've only got 1/2 languages there for me xD2 -
I finally finished a website of a client where I‘m working on since 2012!!! WTF! I never hat such a client before. Sometimes I haven‘t heard anything from them 4 months then they called me, I changed some pictures a did a little bit of styling and then it took months again to get a feedback! To be honest, now 5 years later they need a redesign of their „new“ website.1
-
So I just started working on a site for a new client who has been working on getting their startup off the ground. Their CTO has built the site so far but I've never seen so much styling and js online in a RoR app... FML.1
-
Horror story and rant time I guess...
I haven't seen the main developer of this MVC project that I've been working on but I can totally assure that his seniority isn't in frontend development 😠 and I doubt the backend too... Fucking DataTables converted to IDictionaries<string,object>
Guess who need to build on top of the pile of shit!
Anyway, I wasn't really careful about what kind of template I was given to work on a new SPA page, so I'm doing the job given the time, but it's fucking gory:
- matrioska style layers (n.3) without documentation
- partials everywhere
- too much inline styling
- too many <style> sections (n per layer or partial)
- too many <script> sections (n per layer or partial)
- poor CSS styling or no styling at all! (classes without any style nor js association)😠
He's just been lucky that the browser is capable of handling his shit
Now that at the end of this year I'll leave this project (solo fullstack) and need to provide documentation for the next poor souls I was thinking to leave behind something at par of my skills and capabilities but analysing the current mess ticks my brain in a bad way, fuck you Marco!
Fuck you
and your seniority
and the Italian way of perceiving seniority that gives you a higher living in the wrong side of the field 🤬🤬🤬2 -
I finally created a kotlin android app for a simple project idea, just personal usage. Beginner level. Quite a good and bad experience.
Functionality is done, just sucks with UI, as I'm not proficient enough with styling on android.
The result is a predefined purple action bar at the top, an almost white text section right below it with *very* light-grey textview descriptions (you can guess how visible they are on my phone...). Center is a big recyclerview, which in android studio has white background with dark grey text items, yet is black on my phone with white text items. At the bottom 3 text inputs and a centered purple "add" button.
... It's a mess as long as you don't know how to design and style on android studio.2 -
!rant && advise
I have some expirience working as full stack developer, but focussed latly mainly on backend (php/java). However for one project, I need a desktop application and I was wondering, if you would recommend electron for it.
Pros:
- I could reuse some of the webapp stuff and cache it offline using web workers
- Styling done via HTML/CSS
- Portable between Linux/Windows/Mac
Cons:
- I haven't worked (much) with node js so far, but that shouldn't be a too big problem
What are the pros and cons from your point of view? Would you recommend electron? Why yes, why no? If no, what would you reccomend as alternative?
My knowledge so far:
Good: PHP/Java (without GUI)/CSS
Quite good: Javascript
Meh: Python (I can hack things together but wouldn't say I'm good with it...), C++8 -
So I came from a Laravel background, I love using it. I mean, Laravel is beautiful!
However, the city I want to move in have ZERO Laravel jobs, most of them are looking for Django and Rails developers. So already knowing Python, I decided to learn Django to get a job in that city and add it on my skillset.
I like it, I watched FCC's tutorial on Django, I'm ready to start and create my first Django project, was so excited and proud of myself until... I found out that:
1.) Django lacks built-in seeder
2.) It's confusing to customize the authentication function
3.) Styling of forms is in Python-level, not on template-level (unless you install a 3rd-party package)
4.) Integrating frontend framework requires manual setup
and many more...
I enjoy Python, and tbh I plan on making it my main language, but this is just... too frustrating. -
Hi guys. Finally cleared up my time. Well not really but I wanna do something else cause I've been depressed af lately so I wanna try stuff I enjoyed.
Anyway. Last time I got quite a few from here but anyone need help with design/styling of projects? Wanna boost portfolio. Can use sketch or directly code in the styling for you.
For free. Though I wouldn't pizza money haha.
Let me know if you have/need anything
Thanks.3 -
I got a job as Back End Developer in IT company, but in two month i only fix styling and layouting website.
I'am on the right company or not.?4 -
I've started using PyQT5 and I'm surprised at how easy it's been so far.
Anyone familiar with it, and if so, what kind of obstacles I can expect to encounter making custom widgets and styling?6 -
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.10 -
Right, budget constraints, in out project. Shop site. Lets go with a good online shop system (shopwired) and just brand up a suitable theme. Client wants to see design flats prior to starting. OK brief designer. Pick one of the themes that is close to their current brand styling. Grab the theme pages, set your browser to 1280. Mock up over the top with brand colours/fonts etc in Indesign and png the pages over to me (make sure we have them on google fonts). Designer comes back a few days later with branded up theme page visuals. Cool, they look great, shouldn’t take too long to rework the css and get this thing working. Client approves mockups. Great, so open the theme files and realise the designer has fucking moved stuff around. This has turned into something more than a styling job. Fucking hell. there goes my budget and deadline. Why don’t you designers ever fucking listen!!!!!
I should’ve done it myself but needed to save time as I’m already busy. Fuck, fuck, fuck, fuck, fuck, fuck, fuck! -
So I decided to learn sass today... Turns out you need to run that good old watch command every session to make your styling work...
It only took me 42 lifetimes to discover that one...1 -
I started a rice after 3 years of happily using KDE, and apparently everything uses CSS for styling now? I'm not complaining, Polybar offered like 4 options and we just played around with glyph fonts, compared to that this is a joyride.
Also, Eww is brilliant. I've seen people make full fucking UIs and custom notification centers and shit with it. I don't have that much time on my hands, but the option is there. All this with janky Lisp and Sass.
Eww also confirmed a suspicion of mine regarding Orchid; language adoption is a matter of convenience. I can get people to learn my language by offering cool trinkets and useful tools to people who have a predisposition to learning. Yuck is an aptly named language but it's not totally unusable, and because I had to learn it to make my status bar I'm now more inclined to write the corresponding scripts in it as well and I'm actually quite disappointed that I have to use Bash for that. -
Love it when a react module doesn't allow custom class names. /s
Now I'm stuck with both BEM like classnames and long ass selectors to style the module. x_x2 -
!rant
Is it unprofessional to have my web application and my static content hosted through different ports (like having the static content on 80, but when it posts to my database it calls different random ports)?2 -
What a day. I was cleaning up some of my styling tweaks for this react app; removing superfluous rules, nailing some hard to pin alignments that have been off up until now, and removing unused files and code in general.
I managed to delete an entire folder. I'm not sure how I did it, but apparently I had highlighted the folder when wanting to just delete one file via vs code. This was hours of uncommitted (yeah, my bad) tweaks and cleanup.
But - I still have the app loaded in my browser. I can't see the prebuilt source code, but I can see the compiled, raw main.chunk.js which gives me the exact code albeit not in the format I need.
So that's my day. Re-tweaking, re-adjusting everything while working my way down a compiled javascript file from top to bottom while explaining to my team why I haven't pushed my changes that I was just going to clean up.
Now I'm having a beer.3 -
This is very annoying. Even more annoying because everything appears to be working great other than this ugly malformed error message: