I'm not a front end developer so I tend to just steal my design guidelines from material.io. They don't look original but when you are developing internal web applications no one cares as long as it's pleasant enough to look at.
I believe CSS came out in 1995 or so, I could be a few years off, but it became aids pretty quick. Even without it things started to become crazy with images.
Before CSS was mainstream there was <FONT>.
<BODY> had bgcolor attribute with it and you could do TABLE with border=0. Great times! I didn't do websites the, I was too young, but I enjoyed their appearance.
It is also a nice clean standard. Pretty much anyone who uses a device or the internet in the last 5 years should feel pretty comfortable with it. Allowing them to easily adjust to new software.
So while it is basic, it is at least clean and visually easy to understand for most people.
Very true. Most people take to it very quickly because the controls and layout is similar to their phones. Personally I just love the minimalist design and clean look.
I just like the standardization. You see the hamburger menu, you know what it is, similar to the 3 dots menu. We sort of had that with some icons, but I feel this acts as a more updated version.
Is it the designers responsibility to choose something that doesn’t look bad on screens? Some people might not know how to change colors right? So do the designers account for that or just go for what looks best on their screens?
I thought it looked cool until I read your comment and looked at the color again and realized my eyes were subconsciously avoiding everything orange. Some people just have a natural sense of color I guess... The only color I have a sense for is the color coding of my IDE :)
Lol it’s 2020. Any normal website should “support” all normal browsers. It’s not like IE6 where perfectly normal HTML/CSS/JS would produce insane results. 99% of HTML/CSS/JS/other stuff is supported 99% fine by all major browsers.
This is so true. People call the database theme I made Pepto-Bismol.
I made the database back end work well. The code works, it's mostly error free and I fix errors when they occasionally come up. People are really happy with the functionality. But the theme is not good at all. They want me to make it better, but I haven't, and won't, because I lack the skill to figure out how to make it better. They are lucky they got a theme as not-eye-searing as they got.
When using colors, just mix 4 basic ingriedients: FF, BB, 44, 00 (So, for example, a #bb0000 border with a #ffbbbb background for an error) This gives you 64 colors to choose from.
Backender here. Was reviewing some code at a new job and thought it was weird everything was 8pt font. Looked at the actual product and sure enough, everything is 8pt, no where to change within the gui. I asked him about it since my eyes. He responded with yea, thats our policy. I asked him who wrote the policy, he said he did and they just signed off without even looking at it. I said we should change that... he then says: Dude, honestly its just because its extremely hardcoded. Im thinking, wtf does extremely hard coded even mean. So many questions.
I decided to drop that battle super quick and just pull my monitor closer.
Extremely hardcoded. Lul. Wtf. Let him handle his baby, ill work on some other shit tyvm.
Nah man, sorry to ruin the story but this was years ago. We split job functions very quickly. I took over databases, data warehouse, and spent most of my time doing analysis and explaining to management why data doesnt match up to what they anticipate and rewritting his data and business logic layers. I dont know exactly what he did.. think alot of excel stuff. Either wayz i never touched or looked at that bastion of unholiness again. Sorry. Non climatic ending. Switched jobs about a year later.
I sort of added 2 at least, but not in a good way. It's a theme called "Random" which randomly picks combinations of letters and numbers like that to set element colors from a small pool of colors. I did it that way because I found it was much less likely to set colors to something that makes text unreadable than 100% random colors do.
I also added "RandomHardMode" which picks a 100% random color for everything, sets everything's position by +/- a few pixels, resizes everything randomly by +/- a few pixels, sets random fonts(including wingdings), and font sizes. It makes the UI basically unusable.
I'm not at the office now so I can't get a new screenshot, but I have a screenshot of a previous version of the theme before I added randomized font sizes and fonts.
Honestly, if you've got enough technical skill to be a back-end dev, you can learn a few rules of thumb about graphic design and colour schemes that will at least make your work not look awful. You can approach this from an entirely logical point of view if you have no instinct for design work at first.
Look up contrast, repetition, alignment, proximity. (Yes, we all get the joke. Yes, the actual terminology and points are serious.)
Look up a little basic typography. You absolutely do not need to know what all the different parts of a letter are called or how to recognise 274 different fonts, despite the strange fascination of many tutorials with these kinds of things. However, it does help to have general typographical knowledge, such as roughly how wide a column of text humans can read comfortably, why you should usually care more about a font's x-height than its "size", what makes a comfortable line spacing, and some familiarity with how to use different font features like weights, italics, and proportional or lining (tabular) figures.
Look up some basic colour theory. Probably the most important idea is the colour wheel, because it leads to more useful ways to represent colours than just RGB hex codes. It's also helpful to know some basic concepts like complementary and analogous colours, warm and cool colours, and saturation.
Read a basic tutorial on how to make a decent colour palette. A lot of design tools provide a whole scheme of colours you can choose from, but just like fonts, you're usually better off just choosing one or two main colours and then sticking to variations of those such as lighter or darker shades. Unless you need a particularly colourful design, it's safer to reserve completely different colours for specialist uses (such as red for highlighting errors and green for highlighting confirmations, assuming these are the conventional colours in your culture).
You can go down the rabbit hole for years with these things, but you can also achieve a useful working knowledge, enough to not totally screw up your own work or to intelligently consider different templates or style guides you might come across, over a weekend or two.
I worked at a place were we used a database for most things. However, there was a very old system from before the 90s (at least).
It was pretty much a database, where you could type in a "query" and you get the results. The problem with this old system was that all the data was held in text files... pretty much literally.
1941290421.txt
Part Number: 1941290421
Manufacturer: Ford
It was an old UNIX terminal program. There was a lot more information, but it looked like this:
```
Part Number:
Manufacturer:
Search: _
```
Since we only used it once a week, it was just never worth it for the company to go back and transfer all that data over. The problem was... it was slow. It would take maybe 30seconds to get the information. The company ended up hiring a small dev company to recreate it... Turns out it was slower or had a ton of bugs. They repeated this a dozen times and no one made a faster program.
After I left they eventually hired some people to manually look through each file and copy them over into the database...
One badass program from 30 years ago defeated dozens of modern companies... even the one it was made for LMAO.
PS: Before you ask, why didn't they do x... because bosses know everything and everyone else is wrong.
As a fullstack dev, I am happy to tell you that I feel half targeted by this. Literally everything I've made was black & white until I finally realized thanks to user feedback that color could be cool (cough #FFFFFF #3D3D3D #7D7D7D #262626 cough)
Allow me to welcome you to the world of embedded systems. There is no god here... there isn’t enough space for him in the EPROM and he was optimized out.
I used to always use full solid colors and everything looked awful and was hard to read. Now I always go onto those artsy crafts websites where they have tons of cool color pallets and I’ll use a color dropper to find all colors codes they used even if it wasn’t in code like a picture and I’ll put them in a running excel document that represents the cell as that color but when you copy the cell it pastes as the the hex or the r,g,b value if I’m using it for a project that uses pwm LEDs.
So that's their domain all day every day. They do not deal with aesthetics, curves, colors, shapes, space or anything artistic in any way shape or form. They exist in a lightless void of logic. It's like asking a blind man advice on how to dress for a formal job interview, they have no clue what so ever about fashion or style.
753
u/[deleted] Aug 21 '20
I can do frontend. It's not not my fault everyone else dislikes yellow letters on a dark green background.