Teaching 7-8 year olds the basics of web design. We're we're playing with CSS and changing colours of block elements and text. One girl put up her hand, completely confused as to why it wasn't working. Her code:

Section {
Background-color: rainbow;
}

Oh the wonderful mind of children

i have seen a lot of people like this.

p.s. i need the devRant sticker😁😁😁 help me out.

When they force you to comment every single thing you do but you're too lazy.

Dance like noone is watching.
Encrypt like everyone is.
Sudo like you have backups.
Tag like you're a SEO.
Vim like you know how to exit.
Ticket frontend like you're the project manager.
Commit like saying "fuck you" in the message is appropriate.
Alert like you would use console.log
Design like you know CSS.
Comment like you aren't the only dev.
Code like PHP isn't outdated.

And finally:

Try to work like you know how to quit devrant.

Fact!

Here's the design, you just code it.

All of my friends are designers. None of them can code. And when I try to design...

Just interviewed a guy with ~8 years of experience:
Me: *Asked him to write a simple algo logic on a paper*

Him: I don't do much of algo design. I'm much of a design patterns and software design guy.

Me: How would you design a singleton class in Java?

Him: *writes a sloppy code*

Me: Hey, thanks for your time. Our HR will get back to you with further updates.

Moral: Interviews can be very short when the candidate doesn't code.

I never wanted to be any sort of developer. I was studying graphic design. I partnered with a friend to create an app. He would code and I'd make things pretty. He flaked, and I picked up programming. That's my story.

Designer: The design is done and approved by you. Set the launch date. We just need to put some code behind it and the shop project is finished.

After the meeting the programmers heard what the designer said to the customer in the meeting.
Programmer: *facepalm*
PM: *facepalm*

Don't design a database we just implement tables as we code the app.

$ rant --ridiculous

So today my beautiful and glorious presence was asked to a meeting, I was supposed to present the hosted platform for a project, well, the meeting took place in a building I had never been in so I got lost, when I arrived the design team were presenting a completely different design that what they had given me, which I had spend 10+ hours cleaning and organizing and integrating with the code, and during the whole time I was there I was never involved in the conversation, so basically I was pulled out of my coding liar for nothing oh and because who doesn't like a good ending ... I crashed on my way home after the meeting. Cool day huh?

I have a lot of respect for anyone who can design a good looking website.

I can code like crazy. And I was a freelance classically trained illustrator for 10 years. But ask me to design a website and it's all spinning giffs, midi tracks, and Comic Sans. Some kind of early 90's geocities nightmare.

Person: I liked your personal website’s design, is it ok if I use it?

Me: A personal website should reflect your own style of design. Try creating one instead of using mine.

Person: Oh well, I liked yours more so I used it. Thanks anyway!

They literally have an exact copy of the code with different content. 😒

How can I un-see this 😑😑

To all the C++ programmers who haven't read "Modern C++ Design" by Andrei Alexandrescu yet, READ IT! Its great. To me, it opened up an entirely new approach to designing classes with a whole new dimension of possibilities. And it reads really well! Sometimes I got shivers because the code was so sexy 😅😂😂

"Any fool can write code that a computer can understand.
Good programmers write code that humans can understand."

— Martin Fowler,
Refactoring: Improving the Design of Existing Code

About two years ago I get roped into a something when someone was requesting an $8000 laptop to run an "program" that they wrote in Excel to pull data from our mainframe.

In reality they are using our normal application that interacts with the mainframe and screen scrapping it to populate several Excel spreadsheets.

So this guy kept saying that he needed the expensive laptop because he needed the extra RAM and processing power for his application. At the time we only supported 32 bit Windows 7 so even though I told him ten times that the OS wouldn't recognize more than 3.5 GB of RAM he kept saying that increasing the RAM would fix his problem. I also explained that even if we installed the 64 bit OS we didn't have approval for the 64 bit applications.

So we looked at the code and we found that rather than reusing the same workbook he was opening a new instance of a workbook during each iteration of his loop and then not closing or disposing of them. So he was running out of memory due to never disposing of anything.

Even better than all of that, he wanted a faster processor to speed up the processing, but he had about 5 seconds of thread sleeps in each loop so that the place he was screen scrapping from would have time to load. So it wouldn't matter how fast the processor was, in the end there were sleeps and waits in there hard coded to slow down the app. And the guy didn't understand that a faster processor wouldn't have made a difference.

The worst thing is a "dev" that thinks they know what they are doing but they don't have a clue.

I'm working on my own code editor with 'multiplayer', option to draw stuff, option to design algorithm schemes, option to browse SQLite databases and most importantly - I've based entire interface on HTML/CSS/JS and entire backend on C# and PHP, so it works both online (via browser) and offline (via program).

Tell me whatchu think, it's still work in progress.
(I've removed the name of it so when I share this project with my future employer, he doesn't connect the dots)

Made a video-call interview. I was asked to design and start the development of a chatbot. I sent my work. Never had a response. A friend of mine was recruited and told me, my entire code was used in the company. :)

Just a test they said.

When a Frontend dev turns hacker.

Rant rant = new Rant
rant.isRant = false // !!!

I woke up this morning after not thinking about my code for a day, and realized i had a flaw in my validation design. I fixed it before opening my eyes.

It's kind of amazing how not thinking about a problem can help solve it. Even if you don't know it's there!

These clowns make my blood boil.

fullStackClown: Hey I need some info on that specific color you want for this design

managerClowns: Yes it should look like this <<sends screenshot>>

fullStackClown: That is not a color, it is a screenshot

managerClowns: Yes it should look like this

fullStackClown: Do you know what hex code that is for that color? Can you ask the design team what color from our corporate identity they used?

managerClowns: Yes it should look like this

fullStackClown: Not helping... okay fine I used the eyedropper and I see the hex code is not used anywhere else in our app, so what color should I use?

managerClowns: Yes it should look like this

fullStackClown: ...

He: Hi Lexter, our client made a website on WIX.
Me: And he wants to remake the website due to SEO, shit code, design and all other aspects.
He: How do you know?
Me: Realy?

Client: Hi Johny, we finnaly finished design of our eshop. Half of year of hard work. Can you code it in week? We have deadline. :(
I: Sure, i can code in speed of light.
Client: How about money?
I: Tripple of sallary.
Client: What?
I: My sallary also grow in speed of light.

Some clients can not understand they can't throw shits on my head. Take it, hire someone else or stop giving mi impossible conditions.

Haha. Users will always be users 😂

My Aunt works for a company for which I did a website. She shows me a plastic cup with a pretty design and a qr code on it and asks me if I knew anything about that. I declined and she continued to tell me that her boss claims I can connect the qr code to some location on the website. Of course I can't. Now they have 2000 of these things lying around the office with a stock qr code that is invalid

When you code without design patterns

I'm really close to just quitting coding all together. This job is sucking the life out of me. I've lost my interest in code and the idea that there are better jobs out there.

My "boss" who's not even really my boss but behaves like he is, is micromanaging my every tag, and is an information hog. He doesn't document, he doesn't tell me anything, I've been here six months and still don't know half of what I need to know to do my job properly!

I'm expected to implement a new responsive design, but we don't have design specifications.
Cool, you'd think, new ideas, complete overhaul! Let's get a good foundation in bootstrap going!

WRONG! It needs to fit in with the old, fuck- ugly pre 2000 design.

Not because of any design constraints in particular, but because HE wants it that way. You know what was fucking trendy in 2000? Tables. Tables fucking everywhere. YOU KNOW WHAT TABLES ARE NOT? RESPONSIVE YOU FUCKING ICE LOLLY CHEWER!

We have no development timeline, no process management, no fucking project management. THE FUCKING PASSWORDS WERE STILL STORED IN PLAIN TEXT UNTIL LAST MONTH YOU IRRESPONSIBLE BANANA DEEPTHROATER! 😤😤😤😤😤😤

I'm doing my best here to get something resembling the old page, but there needs to be some fucking compromise! We are in fucking 2017, let's work with Bootstrap instead of against it, how about that you fucking bald cactus!

I know enough about UI to know that the way we're going, this is just going to be another unusable fucking clusterfuck.

YOU KNOW THE BEST FUCKING PART? I'M A FUCKING BACKEND DEV AND I WAS HIRED AS SUCH! GIVE ME A DESIGN TEMPLATE AND I'LL DO MY BEST TO IMPLEMENT IT, BUT FUCK YOU FOR EXPECTING FRONT END LEVEL DESIGN KNOWLEDGE YOU DUMB FUCKING SPAGHETTI!

At my previous job a coworker left positive comments alongside any negative ones on my code. “Nice job here. Very clean”, or “nice use of X design pattern here!” Kinda made me look forward to his code reviews.

When I discovered Clean Code, design patterns, TDD and BDD. It just clicked. Ever since everything build so easy and obviously. I no longer have most of the code problems folks rant here about.

That's when it came to me: it's not enough to know how to write code. To climb off those amateur shoes I must adopt those methodologies, so that the code would be decoupled from me, from my style, and I've got to let tests drive my code rather than vice versa to have a flexible and reliable codebase that is cheap and easy to maintain/extend.

I tend to respect project managers who came from production (ie. who can code, design, or produce something tangible), vs. "professional" managers who have no idea how the work is actually done.

Sadly I didn't encounter many.

Everything but UI/UX
Because I suck at it, lame but true, I love every kind of code, from MEAN and LAMPP to assembly, but when it comes to UI I just lack of the imagination and creativity to design something that looks averagely good.

Design first, code second

Totally skipping the design phase and start typing code. Sometimes causes rework.

when you design and code at the same time

rant.

when you're a programmer surrounded by designer friends, it feels frustrating sometimes.

people appreciate what they do more because they can clearly see the end product: beautifully designed ui, animated splash screens, clean colorful themes. even though it probably does squat other than to print statements.

then they look at your overly simple design and cant see the beautiful underlying code within.

end rant.

To new web devs from a new web dev:
Try to design your site before you write a single line of code. Be it Photoshop, Paint, a piece of paper, a literal goddamn canvas, you name it. You may thank yourself for it later.

I think I want to quit my first applicantion developer job 6 months in because of just how bad the code and deployment and.. Just everything, is.

I'm a C#/.net developer. Currently I'm working on some asp.net and sql stuff for this company.

We have no code standards. Our project manager is somewhere between useless and determinental. Our clients are unreasonable (its the government, so im a bit stifled on what I can say.) and expect absurd things from us. We have 0 automated tests and before I arrived all our infrastructure wasn't correct to our documentation... And we barely had any documentation to begin with.

The code is another horror story. It's out sourced C# asp.net, js and SQL code.. And to very bad programmers in India, no offense to the good ones, I know you exist. Its all spagheti. And half of it isn't spelled correctly.

We have a single, massive constant class that probably has over 2000 constants, I don't care to count. Our SQL projects are a mess with tons of quick fix scripts to run pre and post publishing. Our folder structure makes no sense (We have root/js and root/js1 to make you cringe.) our javascript is majoritly on the asp.net pages themselves inline, so we don't even have minification most of the time.

It's... God awful. The result of a billion and one quick fixes that nobody documented. The configuration alone has to have the same value put multiple times. And now our senior developer is getting the outsourced department to work on moving every SINGLE NORMAL STRING INTO THE DATABASE. That's right. Rather then putting them into some local resource file or anything sane, our website will now be drawing every single standard string from the database. Our SENIOR DEVELOPER thinks this is a good idea. I don't need to go into detail about how slow this is. Want to do it on boot? Fine. But they do it every time the page loads. It's absurd.

Our sql database design is an absolute atrocity. You have to join several tables together just to get anything done. Half of our SP's are failing all the time because nobody really understands the design. Its gloriously awful its like.. The epitome of failed database designs.

But rather then taking a step back and dealing with all the issues, we keep adding new features and other ones get left in the dust. Hell, we don't even have complete browser support yet. There were things on the website that were still running SILVERLIGHT. In 2019. I don't even know how to feel about it.

I brought up our insane technical debt to our PM who told me that we don't have time to worry about things like technical debt. They also wouldn't spend the time to teach me anything, saying they would rather outsource everything then take the time to teach me. So i did. I learned a huge chunk of it myself.

But calling this a developer job was a sick, twisted joke. All our lives revolve around bugnet. Our work is our BN's. So every issue the client emails about becomes BN's. I haven't developed anything. All I've done is clean up others mess.

Except for the one time they did have me develop something. And I did it right and took my time. And then they told me it took too long, forced me to release before it was ready, even though I had never worked on what I was doing before. And it worked. I did it.

They then told me it likely wouldn't even be used anyway. I wasn't very happy at all.

I then discovered quickly the horrors of wanting to make changes on production. In order to make changes to it, we have to... Get this

Write a huge document explaining why. Not to our management. To the customer. The customer wants us to 'request' to fix our application.

I feel like I am literally against a wall. A huge massive wall. I can't get constent from my PM to fix the shitty code they have as a result of outsourcing. I can't make changes without the customer asking why I would work on something that doesn't add something new for them. And I can't ask for any sort of help, and half of the people I have to ask help from don't even speak english very well so it makes it double hard to understand anything.

But what can I do? If I leave my job it leaves a lasting stain on my record that I am unsure if I can shake off.

... Well, thats my tl;dr rant. Im a junior, so maybe idk what the hell im talking about.

The commonly touted "best" experiences are when you just get told "wow, this code is amazing!"

I hate those code reviews.

The best ones are the ones where I get my code completely ripped apart by 10 different people in 10 different ways. Some of them might be amazing. Some of them might be arseholes thinking slating other people's code is how you climb the career ladder. But they all generally teach me something, and they all cause me to stop and think "hmm, have they got a point, or is my original design better?" The discussion that comes from those reviews is also often very interesting; and (when done well) the whole process can become somewhat of a teambuilding exercise for everyone involved.

Let junior dev design module.

Make code review.

What junior dev says: "It is a totally flexible concept!"

What junior dev means: "It is extremely shitty to use for the one use case it was meant to do, but it will be equally shitty to use for all the use cases we will never have."

Back to square one.

Hey I got reminded of a funny story.

A friend of mine and me were in internships in the same company. The company was specialized in territory resources management (managing water for agriculture, money to build industrial zones...). He got the interesting internship (water predictory modeling) and I got... The repairs of a reference sheet manager that never happened to work. It was in C# and ASP.NET and I was in second year of CS. I expected the code to be nice and clear since it was made by a just graduated engineer with +5years of studies.

I was very wrong.

This guy may never have touched a web server in his life, used static variables to keep sessions instead of... well... sessions, did code everything in the pages event handlers (even LinQ stuff et al) and I was told to make it maintainable, efficient and functional in 2 months. There were files with +32k LoC.

After 1week of immense despair, I decided I will refactor all the code. Make nice classes, mapping layer, something close to a MVC... So I lost time and got scoled for not being able to make all the modifications as fast as in a cleanly designed code...

After 4 weeks, everything was refactored and I got to wait for the design sheets to change some crystal report views.

At this moment I began to understand were was the problem in this company.

My friend next door got asked to stop his modeling stuff for an emergency project. He had to make an XML converter for our clients to be able to send decentralized electrics bills, and if it was not completed within a week, they would no longer be able to pay until it is done.

This XML converter was a project scheduled 5 years before that. Nobody wanted to do it.

At the same time, I was waiting for the Com Department to give me the design views.

I never saw the design views. Spent one month implementing a golden ratio calculator with arbitrary precision because they ain't give me anything to do until the design were implemented.

Ended with a poor grade because "the work wasn't finished".

Just got my beta access for Framer X. They describe themselves as "Unity for design" bridging the gap between Sketch and React using code-based components. I think it has a lot of potential. Would love some non-designer perspectives. What do the front-end devs here think of it?

1. Read about software engineering/design patterns, tools etc.
2. Adopt information to my requirements
3. Write code
4. Delete my shitty code from point 3.
5. Goto point 3

The more you design, the less you code.

Oh boy. Gotta love having a team member (For a School project) be in charge of the Database functionality/design, who has almost no communication skills and basically no clue about how to store data in a data base.
Im talking dates stored as varchar(5), column sizes being way way to small, overall table design being rather terrible, no primary/foreign keys, pretty much... Actually no, everything was being stored as a varchar.
Not only that, but there was a hell lot of data that needed to be stored that wasn't even accounted for in the DB design. He made some code that could be used by our team members for queries, creating tables, inserting data (etc), almost 2,000 lines of it.... And basically nothing was fucking documented at all. I'm talking comments like "Insert data into cities table" and nothing else. More complicated functions had as much, or less documentation. Complete mess.

What do you need a boss if you can find the idea, analyze it, design the product, code it, test it, setup the cloud and even do the marketing.

Dear bosses,

I am a developer not a God!

Error Code: 1117. Too many columns

That must be one hell of a database design!

Ah.. the beauty of clean code.

I wrote a very cleanly written program two years ago. Proper variable names, not too many, right naming, right design pattern,.. Now I come back to it and I am able to instantly figure out the code again. It only took me half a minute.

The importance of clean code... that's something the industry needs to understand more. Well, then there's the money issue. lol

Hello World! First post here. I'm literally done with frontend stuff. I want to design code, not to code design. Unless it's Processing. I find it cute. So.. I have a somewhat handy grasp on C++ because of a class in electronics course, Python seems quite easy to catch. I'm totally new to programming. I'd like to get into software, game development and android development (but I would like to do things cross-platform).
Which paths, resources, languages, useful books, videos, or just anything would you recommend?

To be fair, I have no coding friends so mentorship or simply finding code buddies would be great. 💜

Just implemented a design from a UI/UX designer in code. Works perfectly on iOS, now to test on android.

Hey I have an idea ! Why not we developers normalise the IKEA way of delivering project to customers? Let me introduce the DO IT YOURSELF software .

Here's how it is done , we set up environment for the client , write manuals , design and pass it over to the customer , let them DIY it by code for themself!

So I'm a perfectionist, especially when with code, smells, solid, design patterns, naming conventions, etc and I be have this co-worker that blackmails me every time he doesn't want to do something saying "I don't know it so my code is gonna be ugly".

When the designer who can't code anything is on double your salary...

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

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

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

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

(Media width) {

~site code

}

(Other media) {

~same site code with diff sizes

}

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

.className {

(Media size) {

}

(Other media) {

}

}

Or a mixture of both?

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

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

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

I hate UI design. When you code functionality, you either make a thing work or crash, efficient or unefficient, reliable or unreliable, maintainable or unmaintainable; but in UI design there's by no means an established way to make something look pretty and that pisses the crap out of me. You cand spend countless hours working in UI design, using the latest CSS libraries and frameworks, but at the end, any client can easily say it's crap no matter how cool anyone else think it looks. UI design sucks.

Patterns 👏 are 👏 a 👏 language 👏 to 👏 talk 👏 about 👏 design 👏 not 👏 a 👏 comprehensive 👏 list 👏 of 👏 the 👏 only 👏 things 👏 you're 👏 allowed 👏 to 👏 do 👏 in 👏 code.

Feeling sick as fuck. Stayed home instead of going to work but I am already upstet about what is happening whilst I am not there.

The manager was gracious enough to task the other developers with creating the templates for one of our projects. I submitted a document before stating our design guidelines and how under no circumstances they should not use bootstrap for the design since none of them know how to manipulate the source code enough to deviate from the standard bootstrap design. The lead developer, even tho I love the dude, has an attitude against new tech. He is primarily and only a php developer still in love with just jquery and php with no real knowledge of proper design methods. He is the kind of dude that would tell you that pdo is a waste of time and that why should we create models and use oop to separate our code into manageable files.
Today I get "why should we not use bootstrap" and shit like that.

Sigh.....i really don't want to see the shitstorm waiting for me tomorrow.

Funny how our cms administrator is eager to learn the list of technologies i proposed. They both gor Programming Ruby, the pickaxe holy book of Ruby and the dude is already halfway through it while the other developer is still asking why should we even bother when we have php.

I get the idea of if it ain't broken don't fix it and being proficient with one stack and whatnot. But that idea of i dont want to learn something new is precisely what shuts down progress.

"I don't want to offend you but well clearly you're not an artist. "

From the client i tell repeatedly "Web design is not my strong point so if there is a design you want we should bring on a designer"

And actually i was an artist. But i didn't like all the subjective criticism. Criticise my code when it doesn't work. I didn't ever sell you Web design

Confused if I should use AngularJS or commit suicide 😕

Anyone else annoyed that they can code a really good website (as in PSD to HTML) but just aren't creative enough to come up with a design? I find myself on Dribbble a hell of a lot of the time coding designs that others have done out of boredom, but stunned by how amazing their designs are. I'm just not creative enough.

Literally whole dev world: DRY - Don't Repeat Yourself
My Company: DRY - Do Repeat Yourself

when you make your best at code writting,responsive design, and making everything smooth but the designer get the credit " coz' the design it's what matters" really? i can't imagine browsing a static image..

I started using GitHub for my codes lately, so instead of diving into the code, I make sure to mess with GitHub to have it available online, then I admire the design of GitHub, then I drift to YouTube, listen to music and can not concentrate. Then I open Facebook and tell everyone how hard my life is 😂

Only if people understood the amount of effort that goes behind building a simple app.
Even if it's a simple notes app, I've to design the UI (at least 2 different activities - 1 for the list and the other for editing notes), write the code which makes it run i.e. without which the app is just a piece of empty design, think about what data
structures to use (that notes you are saving need to be stored somehow) and then club everything together and hope nothing breaks (spoiler alert: something will definitely break).

People need to understand that it's not just putting some fancy buttons and boxes around. Also, I'm not just making the app for one device. I've to make sure it works on different screen sizes, different versions of the OS (a user can't imagine how many functions need to be re written because something got deprecated in the process and I'd to switch to something different).

Also I'm not just sitting at my computer and converting coffee to code. I've to think about the flow, structure, design, navigation, backend etc. Of the app; most of my time isn't spent writing code but thinking/studying how to write the code. I also need to wait while the project is compiling/building every time I want to test it.
A function which you think is hard to implement night be really easy while something you claim is easy might be a nightmare. Oh and I didn't even mention how I need to stick to some design guidelines to make the app look consistent with the rest of the OS.
If you're wondering why a developer is spending most of his time on a browser, he isn't playing internet games or browsing reddit ( at least you better hope not), he's probably looking at the docs/stack overflow to get something to work/fix something!

Wow! That was long. Thanks!

Why are people complaining about debugging?
Oooh it’s so hard.
It’s so boring.
Can someone do this for me?

I honestly enjoy debugging and you should too..
if it’s not your code, you’ll get to understand the code better than the actual author. You’ll notice design improvements and that some of the code is not even needed. YOU LEARN!

If it’s your own code (I especially enjoy debugging my own code): it forces you to look at the problem from a different perspective. It makes you aware of potential other bugs your current solution might cause. Again, it makes you aware of flaws in the design. YOU LEARN!

And in either case, if it’s a tricky case, you’ll most likely stop debugging at some point, refactor the shit out of some 50-100 line methods and modulize it because the original code was undebuggable (<- made up a new word there) and continue debugging after that.

So many things I know, I know only because I spend days, sometimes even weeks debugging a piece code to find the fucking problem.

My main language is java and i wouldn’t have believed anyone who told me there’s a memory leak in my code. I mean, it’s java, right? We refactored the code and everything worked fine again. But I debugged the old version anyway and found bugs in Java (java 6.xx I believe?) which made me aware of the fact that languages have flaws as well.. GC has its flaws as well. So does docker and any other software..

Stop complaining, get on your ass and debug the shit out of your bugs instead of just writing it in a different way and being glad that it fixed the issue..

My opinion.

Life cycle of code

1- See what sound code I have written! It's beautiful.

2 - Hey we missed something last time, just add this bit of tweak.

3 - We need to add some flags for some exception cases

4 - Hey there is a new requirement. Just add some more paths and more flags

5 - More flags!

6 - This shit runs now more on flags than on the design!

7 - Flagception!

Start-ups and corporations trying new things be like:
"Why should we pay a developer or a company to develop this and this for us when we can just:
- start a competition.
- get free design mockups and code.
- decide which is better.
- reward a small prize and maybe some freebies to the competitors.
- profit. FREE CHEAP CODE AND DESIGNS!!!"

It might be the reasonable and logical thing to do from a business standpoint if its about code you need to rarely maintain..

But from an independent developer viewpoint - FUCK YOU AND THE SLOW ENSLAVEMENT OF MY SPECIE!!!

I'm gonna cheat a little since i don't like alcohol 😁

School projet, designer sends me final design less than 24 hours before the deadline, i coded all night long. 17 hot chocolate bowl. I never got the luck to be in the same flow than that night. Each hot chocolate made me stronger, lines of code were running, CSS was perfectly good first try.

Once code was submitted, i slept for like 14 hours. I woke up hugging my pillow.

I'm pretty sure i was drunk with hot chocolate.

That moment when you win an app design competition by writing code instead of using Photoshop...

The design process.

Call me old fashioned - but clean-code/clean-architecture/SOLID is not as important as simplicity and coherence.

I JUST NEED FUNCTION THAT DOES STUFF! But noooooo better overly design EVERYTHING!

I can't believe this company has not hired a ux designer yet!

Team managers have no clear design principles to follow, they are coming up with design changes and ideas on the fly.

For fucks sake, at least provide a reference design or color sets to implement instead of complaining to me when i use hard colors like red / green / blue on first version of what you asked to do.

I hate doing minor style changes on code when you have no clear vision about the design.

I think the end product is gonna end up as a ux nightmare without a ux specialist.

Design. Code. Debug <- Repeat.

- Life of a Developer.

When you're too good to use the left hand side of the screen.

I started a project at high school 7 years ago, I had no idea what's clean code or design pattern, just learn while keep coding. I eventually stopped because my code is so terrible I cannot understand it anymore.

Now, after 1 year of working, I look back those dirty codes and think it is actually not that bad. Within hours I even fixed a bug with concurrency.

I start to think, instead of learning to how to write good code, maybe I should learn how to read bad code. That's just much more practical.

Am I the only one who can't cheat on my design/development stages? For example, if I am doing a favor for someone, I will do it my way even when I'm short on time. I simply can't just "take it from the internet and incorporate it into my project".

I just feel for comfort when it's mine. (no Im not referring to reusing code. Clarification in comments)

"Let the developers consider a conceptual design,” the King said, for about the twentieth time that day._

“No, no!” said the Queen. “Tests first—design afterwards.”

“Stuff and nonsense!” said Alice loudly. “The idea of writing the tests first!”

“Hold your tongue!” said the Queen, turning purple. “How much code have you written recently, anyway?” she sneered.

“I won’t,” said the plucky little Alice. “Tests shouldn’t drive design, design should drive testing. Tests should verify that your code works as it was designed, and that it meets the customer’s requirements, too,” she added, surprised by her own insight. “And when you drive your tests from a conceptual design, you can test smarter instead of harder.”

Kotlin support on Android:
i never liked Java, not because of the language but for the usual bad design implementations and Android is one of those.
Then Kotlin arrived, it looked very promising but it's when i looked at Coroutines that it simply blew my mind:
you just have to write your code and the Kotlin's compliler "magic" will do most of the boring/complex stuff for you and it's even great performance wise!
I even refactored inter-process calls to simple sync functions with few like of code and for a non-android developer like me it's just love at first sight!

When I realized my job isn't to code, it is to hack for hacks.

As smart developers our job is to be accountable to non-technical product management types who care nothing for elegant system design or DRY code. They expect features get done fast and "technically complete." They use terms like "minimum viable product (MVP)" to imply we'll go back and improve things like refactoring and tech debt later.

They will not. Most likely they won't even be around. Producers and scrumlords have the highest turnover rate of any role on a team. By design they get bored or frustrated easily and are constantly looking for greener pastures. Many people in self-proclaimed "non-technical" roles like this never had the patience and attention span to learn a real vocation, and they've discovered a career path that doesn't require one.

These are our masters. As developers, we will answer to them forever and always.

So before the Age of JavaScript, when programming was trying to be an engineering discipline, I felt like we were getting close to figuring out what worked and what didn't. We had rules of thumb (more general than Patterns) and code smells.
Then JavaScript came in and no one had time to think about "engineering" anymore. I'm fine with MVP and small iterations, but the disdain I see for making code clean and extendable and improvable is baffling (and annoying). First-time coders might never have had to fix someone else's code, but two weeks in a chair should have fixed that.
It's not that understanding code is so hard (although it can be); understanding the _intent_ is hard. This MVP is great, but when no one had time to document what is actually supposed to happen, programmers have to reverse-engineer the *design*.

I really like this book on the basis of the philosophy overall, no this doesn’t solve all problems but it’s a good baseline of “guidelines/rules” to program by. Good metrics or goals to architect and design software projects high and low level projects.

Fight Software Rot
Avoid duplicate code
Write Flexible, dynamic, adaptable code
Not cargo cult programming and programming by coincidence.
Make robust code, contracts/asserts/exceptions
Test, Test, and TEST again and Continue testing.. this is a big one.. not so much meaning TDD.. but just testing in general never stop trying to break your software.. FIND the bugs.. you should want to find your bugs. Even after releasing code the field continue testing.

Manager redesigned large parts of a website template that I have been working on.

now, this did not bother me one bit but I am pretty sure it has to do with the delivery of the message. She was so happy about the redesign and it really did look better. I could not find it in me heart to not comply and just be happy. Plus she always lets me come in super late :V and she really is pretty and very nice to us.

oh well.

Me sitting down to code for the first time in months after having an extended focus on design

Think twice code Once, if I had a cent for every time I've jump right into the code without a proper analysis or design just to notice that my whole implementation is not functional or scalable I'd be a millionare

I use a Mac that implements MAC using MAC and its got multiple hardware MACs along with a hardware MAC.... btw, I'm eating a Big Mac.

...

Media Access Control - Networking
Manditory Access Control - Security
Message Auth Code - Security
Mac - Apple
Multiply ACcumulate - Chip Design

Spent 4h+ debugging my code (it was late)...only to realise that my code was not buggy, but the fuckup in design was in the original part I didn't change..FML..

I had code waiting in review for ten days, blocking other work. On the eleventh day, the final reviewer (who was standing behind me as I wrote it) says "I'm not sure that I agree with the design, here."

I get you, man, I can re-write the algorithm, but I am so not in that context anymore and you've just delayed release of the feature by at least a week. Ugggh.

Does anyone get the feeling that as they become more senior, they care less about meeting "best practices" and more of just "good enough"?

Best practices being everything in those books about TDD, unit testing, design patterns, design artifacts.

Good enough: enough so it won't blow up in prod, some tests but not 80-90%, some docs. Basically not like those public docs, open source projects/frameworks where function is covered

When I first started professionally, I was all about efficiency, good design, reducing technical debt, clean code.

But now, I look at problems and instinctively I may make these decisions but I don't really think about it much. First goal is to just get something working, clean it up later... Maybe.

A Jargis, just the AI, someone that could write code I design and analyze my written code.

No-code web design tools are made for the sole purpose of lacking features in order to torture a developer after marketing or sales requests something that the tool cannot do, or can but requires a very roundabout way of doing things. Extra points for things that have a JS API instead of letting you inject the damn thing.

"Yeah. I don't only design, but I can also code, just like you."
"Cool, what programming language?"
"HTML and also CSS."

The reason why I can't sleep at night

dev: “I want to start working on [feature]”

Me: “I already started to work on it, sorry for not mentioning it, we need specs from design team before I can go on, but I’d suggest going for another task meanwhile”

Manager: “noooo design is very very busy, [dev] will take care of it.”

Me: “[dev] still needs specs from the design team... and I am half done with it so no real point in re-writing the same code I wrote”

Manager: “just trust me, we do this and [dev] takes care of it.”

*me and [dev] look at each other perplexed and just nod to the manager cause it’s Thursday and the fucks to give are over*

... am I actually a patient in an asylum? I question my sanity after this exchange of words.

"Don't go too crazy with the design, this is just quick to get it out, this is a one time deal" - management

Half a year later...

"Well if you would properly design components up front, it wouldn't be so hard to extend the code" - management

Well if there were some sort of god forsaken process in place, with assigned tasks, priorities, iterations, and conventions, maybe everything wouldn't be a last second shit show and there would actually be forward progress on a project instead of throwing shit over the wall and hoping everything lands in the correct places.

Einstein supposedly has a quote attributed to him: "Perfection isn't achieved when there is nothing left to add, but when there is nothing left to remove."

I find that I aggressively refactor code where I can to only what is absolutely required. It does also have the knock on effect of reducing scope of bugs, when the code is smaller there's only so many places bugs can be.

Tesla claimed to have the ability to create designs in his head and only built things once he was satisfied that it worked in theory first, now it's rare I can do that, but I will use a repl to prototype or test modules in isolation before just hacking on the actual code.

Jobs, I mean, I know he didn't code but he was always insisting on designs that looked good and was generally uncompromising in his design centric view.

My friend, she was my Starbucks barista for a while but I've slowly been teaching her code and she's taught me a lot about how to teach others to code, she also happens to be my favourite student.

But am still confused, is it ok in terms of good design.
Reusing existing code.

I was assigned to maintain the website as full stack dev but the code from backend is horrible previous devs didn't use SOLID principle, DRY, KISS, or Design patterns. I had to adjust from OOP mindset to Procedural its hard to debug in this state.

PM in sprint review, after some colleagues complained about having to develop requirements on their own:
you are software engineers, your main task is to design software systems. this is the tricky part. coding is easy... it's a stupid task, i could do it, my nine year old daughter could do it.

shall i feel a bit offended? also i think, he is wrong... i also design while i'm coding, i'm designing all the time.
also, i love coding :( this is the most satisfying aspect of my job.
but then again, i heard there are people who code without designing... even though i cannot imagine how to work like that at all.

I cannot believe its 2020 and I'm reading: Customize font size for navigation items & tabs as "New Features!"

From Apple:
With an all-new design that looks great on macOS Big Sur, Xcode 12 has customizable font sizes for the navigator, streamlined code completion, and new document tabs

Ah the classic "Grau Dunkel 70". I know exactly what hex code that is. Thanks, design team!

Fuck you.

So true.

When your non-programmer boss thinks after explaining a program design to you, his sitting by you and staring at your screen will help you code it faster...

I'm a junior dev less than 1 year into my first job out of college. I'm halfway done reading Clean Code (my first software book out of college) and I'm really enjoying it!

What should I read next? I was thinking something about design patterns. Should I go for the classic GoF book or continue with Robert C Martin and read "Agile Software Development, Principles, Patterns, and Practices"?

to the guys saying "oop is dumb" / "i don't need oop" / "i've never worked with oop"...

i have some questions:
- which language are you working with
- which problems are you solving
- how big is your code base
- how do you maintain readability of your code?

don't get me wrong, i don't believe that oop is always the answer. i'm just curious which fields these statements are coming from. if they all come from a low level (assembler, C, ..) or functional languages or "scripty" languages (python, JS), or if there are also people working with languages like C++ where oop is pretty much established. and if the latter, i'm curious how people design their code and what problems they solve... tell me your story :D

I talk to clients. I prepare the requirements. I design the database structure. I design prototype frontend. I do documentation. I code. I debug. I update change log.

I die.

Before internship, js code with semicolons looked stupid to me. Then jshint happened and here I am at 3AM in the morning, adding semicolons to a forgotten but not abandoned design project of mine!

So I got this new job as Java developer, the people are really great but is the kind of companies that only takes care for fast results and not for code quality.

Because this I have to deal with libraries updated 4 years ago, classes with 8000 lines, methods with 500 lines, a WHOLE lot of work arounds because there is no time to really fix the issue unless it affects directly the customer (something not working or being really slow) aaand we use fucking svn.

Some of this practice's they know and encourage it (+1000 lines classes for example) and every time I try to talk about good practices in the code everyone seems so interested but there is always no time.

Sooo I will stay here for at least two years, I hope I can make a change for good in their code smells.

A colleague of mine who doesn't know how to write simple conditions and sends button code from backend in loosely coupled design.

Worst of all she doesn't wants to get updated to the latest programming structure and no signs of learning on how to write clean code!

I'm curious..

When does programming suck for you, and when is it fun?

Like I hate programming, when I run into an obscure use case that opens up some serious errors with my some, or gasp, all, of my architecture and forces me to rethink everything - especially DB design, ugh.

I love programming when my architecture and DB design create naturally readable code and everything falls into place and I feel like a genius.

I guess, in short.... plan before you code?

And then, plan again.

But don't plan too much.

The love/hate of my programming life summed up right there I think.

How about you?

After being an active developer in the industry for about 5 years, I still have some bad dev habits on which I'm working on:
- Starting off with the code first without a proper design in mind/paper. (Trust me, I'll always regret of not having a proper design later)

- Writing long method bodies and not refactoring them later. (Because sometimes I turn out to be a lazy ass)

- Duplicating code in some places without reusing some.

Best part of working in Company:
Getting learning sessions from Seniors and sharing design aspects and their pros and cons.
Had an awesome session on how to focus on making a code testable.
With hands on coding too.
Never expected to have such a great experience.

So a week ago my boss asked me to design + build/write code for our new site from scratch.
Meanwhile the old website they have had for 5 years is still without SSL and looks pre-2000.
It's supposed to be finished and be mobile responsive by tomorrow.
                                                                                                                                                                            
                                                                   
  
       
I'm the digital marketer.

I'm looking at old code that I wrote around half a year ago, and noticed that my coding style changed over time (relying more on arguments to pass messages between commands and functions, rather than sourcing the result of a command). I feel like this old code isn't truly mine anymore. It's thousands upon thousands of lines of code though... Given that, would you rewrite it or just move along with the existing design? I mean in my opinion the current code really sucks.

Beings of Devrant - what makes a person a bad programmer?

So I'm about to finish The Design of Everyday things by Don Norman and I have Clean Code coming up next.

But what are some good programming books that are tech agnostic?

when your task is basically an open debate in design philosophy between 3 dev management levels and you just want someone to make the call so you could code

when your code is almost done and your project manager comes with last minute design changes.

It is easy to believe something is over-engineered as a junior. You open a solution and get slapped in the face with a wet fish of many classes, with strange names, doing very little, with everything coming together in ways you don't understand.

My advice is to learn about design patterns, clean code, clean architecture, and model driven design. Until that point I don't think you can make such a distinction. And indeed once knowledgeable of patterns and techniques as well as the domain, the same solution can look obvious, elegant and readable.

In a field where everyone is saying 'dont over-engineer', one must be able to tell if something is actually bad, or just uses techniques you don't recognise.

Telling your senior you think something is over done just because you don't understand it is not good. First learn techniques, understand the code, then form opinions that are at least relevant then.

From someone who committed that crime.

I learned how to program during my MSc at UC Santa Barbara in 1988. But the real thing happened during my first job as software engineer at Chorus Systems, in Paris, with the guidance of some of the world's best mentors, Russian engineers who taught me how to approach code design as if it was playing chess. These guys were brilliant!

I began exploring code and graphic design early on at about 6-7 years old. My Dad had a commodore 64 with a few games and a little handbook that had some awesome examples to go by. My Dad had at one time been a subscriber to a serial magazine for Commodore enthusiasts that featured a snippet of code in each issue. After getting into my Dad's old stash of magazines I was able to combine all the magazines and write the code from each issue to create a hangman game. This got me into computers and programming. Then we did some Logo/Turtle work as got into qbasic on our IBM machine.

Me, consulting for a huge entertainment company:
Why do you guys have a 500 line method? And why is half of it so nested that it's indented half way across the screen?

Them: Oh, that was written by the best dev on our team. He holds a PhD.

🙃 so thats what kind of skill a PhD gets you these days?

Question: is it a red flag if I'm "not supposed to" blog about tips and tricks I've found at work (not even code level, just organization and general design patterns)? Reason given to me: "we need to be careful about due diligence and intellectual property for our investors to be satisfied". Am I working with idiots?

Once again, I have to go with the guy that, after seeing my horrible (I can't highlight this enough) code, decided that even I wasn't hopeless, and went on teaching me the basics of software engineering, top-down design and unit testing. All of this in two days, but it gave me the motivation to work on it, and look at me now: I'm a devRanter :')

Any senior types out there find that you’re losing your coding “chops”? I’m involved in so many OS/Middleware upgrades, infrastructure upgrades, status meetings that I can’t code to save my life anymore. I can review and guide design, but I struggle to generate new code. I can get a new dev going really quickly though - is this just a natural progression or is it game over for me? I feel like if I had to get another job, I’d be very unsuccessful. They call me a leader, but I think I’m just a slave.

So opinions: should a software engineer get certifications? I mean, to me they seem like pointless wastes of money, but my coworkers don't seem to think so. I design and write code, why do I need MCSD or whatever? Follow up, if you feel they are useful: which ones and why?

I've spent a lot of time messing around with C, having struggled with object-oriented programming (due to not really knowing how best to structure things, not knowing when to apply certain design patterns).

When writing C code, I'd write OOP-esque code (pass around a struct to routines to do things with it) and enjoyed just making things happen without having to think too much about the overall design. But then I'd crave being able to use namespaces, and think about how the code would be tidier if I used exceptions instead of having every routine return an error code...

Working with Python and Node over the past couple of years has allowed me to easily get into OOP (no separate declaration/definition, loose typing etc.) and from that I've made some fairly good design decisions. I'd implemented a few design patterns without even realising which patterns they were - later reading up on them and thinking "hey, that's what I used earlier!"

I've also had a bit of an obsession with small executable files - using templates and other features of C++ add some bloat (on Windows at least) compared to C. There were other gripes I had with C++, mostly to do with making things modular (dynamic linking etc.) but really it's irrelevant/unreasonable.

And yes, for someone who doesn't like code bloat, working with Node is somewhat ironic... (hello, node_modules...)

So today I decided to revisit C++ and dust off my old copy of C++ in a Nutshell, and try to see if I could write some code to do things that I struggled with before. One nice thing is that this book was printed in 2003, yet all of its content is still relevant. Of course, there are newer C++ standards, but I can happily just hack away and avoid using anything that has been deprecated.

One thing I've always avoided is dynamic_cast because every time I read about it, I read that "it's slow". So I just tried to work around it when really if it's the right tool for the job, I might as well use it... It's really useful!

Anyway, now I've typed all this positivity about C++ I will probably find a little later on that I hit a wall with what I'm doing and give up again... :p

My dev Goals:
- Write better code commenting more.
- Create my first Open Source Project and publish it on GitHub.
- Improve my design skills.

You know how a normal developer will start writing a program, and then take the big pieces and split/refactor it; move hard coded things into functions that take arguments, and cleaning up along the way?

Our manager makes a tons of empty files, and empty directories, with how he thinks he wants to build something, and checks them all in. Tons of .gitkeep files in empty directories, blank Jenkinsfile, Dockerfile that doesn't build.

When he makes wiki documentation, there are tons of subsections, all of which are links to pages with "TODO" in them.

Dear god stop it you asshat! Stop making tons of empty files and pages. Write the thing in one chunk and then split it as needed like someone who actually knows how to engineer software!

Best advice so far: "KISS: Keep It Simple and Stupid"

That works every time because your design of the code will be understandable. Your code must seldom to be refactored. You aren't that asshole who never comment and document anything. And the most important part: The code works as designed without flaws!

all documentation points to an Invalid auth token being code 400 (ignore the fact that this is a code in the JSON response and not HTTP)

Me: here iz credential. Plz send datas
API: haha fock off and die mate, then credentials you got there aren’t workin’
API: code 998 invalid auth token
Me: *speechless* so that’s why it took me longer than it did to find that error, because YOUR CODE WAS MISSING ALL MY CHECKS FOR CODE 400.

Why can’t people design apis properly.

The more you design the less you code.

Same as we look at some old pages and see "oh this is unstyled table layout, that is xHTML inline style - it's from the 20th century"

People will look at pages of today in like 20 years and be like "Oh gosh, the material design phase. - oh the apple-blur-copy-cat-phase, oldish HTML5 code, that's from the 2010-20-ies"

are there some graphic designers here? 😎
Do you code?
Did you learn some stuff here on devRant? What did you learn?
What do you design mostly?
How do you deal with programmers who don't obey your design specs because they're lazzy fucks? muhaha 😆
how do you think this profession will evolve in the next 10 years?

and you devs, what do you think of us? what are your experiences with designers? good and bad ones?

exactly two years back I joined my current company, it is spanish company and I speak only english. each document that was there in the welcome kit was in spanish, including design and architecture documents. also coding guidelines. it was a night mare as comments in the code were also in spanish. it took me three days to come to terms with reality.

I think the worst thing I’ve seen from devs is lacking the curiosity to know how some software library works before using it which then almost always leads to bad design and code.

Fuck the design guidelines that change every fucking day. It makes Front-End an unbearable hell. I'm seriously tired of having to code stupid shit for exceptions exceptions exceptions.

Let's face it: I am and will always be a tinkerer. Yes, I know my ways around, I can sneak into legacy code bases easily and throw new stuff in there, I've seen software stacks. But scarcely sound design, really modular. Even from the cleverer, experienced ones. They can master more complexity, so they can handle more spaghetti. Some essay from the 80's had this grand idea to organically 'grow' software. That's how it looks like most of the times: cancerous, parasitic super fungi (armillaria). Yeah, we all know have to fight bit-rot and entropy, but it was all lost before already. We'll never get rid of legacy protocols, legacy code.
And even when we go green field, start a fresh. Yeah, take a great design, make everything new, after some months of throwing features and outer constraints at the thing, it's the same old mud again.
But we can still dream on: some day I will design great APIs, I will have great test coverage, documentation, UML design, autometed tests, fuzzing, memchecking, I'll work professionally, clean coder style.
Pfft forget it. Maybe change for consulting, because we'll continue to dream of the 'clean' code, so you can sell the next 'recipe', development method. It's like diets. As effective. For the one selling.

I'm starting to get bored at work. Every fucking day is the same. I receive a design. I code that design ( aka I'm modifying the framework developed by me ). I deliver the frontend. I think that anyone with no programming experience can do my work now.

Fuck you for asking for my advice and then just disregarding it because it doesn't dovetail with what you were hoping for. You continue to justify your shit code design as "the way it has to be". Bullshit, I just told you other ways to do it. You didn't want to hear it. Open your mind. Learn something new. Be a professional. Your code is ass and you should feel like an ass. Don't ask for my help anymore. Prick.

My reaction when I meet peopel that still don't use any Architecture/Design Pattern to code.

What is yours?

You told the design team this won't work on a large scale
Design team: Well we designed it, so, fuck you !
You: Does the implementation...
End Product: * Doesn't work *

Design Team: Why isn't it working, suggest a workaround

* Facepalm *
* Dead Inside *
* Give me Death Note plox *

That this one component being object orientated is necessary and good design.
We have uh interfaces, theyre contracts.

Spoiler: it wasn't, I could have written it in half the code and half the time. But no, we gotta have those patterns, can't miss on dependency injection!

I get really angry when my friend (has only ever taken a web design class in high school that taught only basic html) tries to preach to me that you shouldn't have to worry about writing readable code along with documenting it so long as it works the way you want it to.

I've been working for 6 months now, and the boss tells me he's not satisfied with my work compared to someone that has 15+ years experience. He clearly states that for him - it's more important lines of code, than planning and defining the architecture which he don't like because that doesn't provide anything...

Of course, I can just jump into the code if that is whats important. I've seen the code produced by the other guy, and its shit.

The guy is a talker, and knows how to talk. I'm more like, hey lets create a simple design prototype or do some UML diagrams to get a better visualization of what we need.

Anyway, its just annoying to be compared to someone with many years of experience, its not that I can achieve it overnight...

I wish companies stopped doing interviews n just stuck to "u have X days to finish this test-project" and judge me by the code/design/architecture

Im a deer to headlights when it comes to interviews -_- I'd even forget my own name on a bad day ffs

co worker edits front end to design, breaks code then files a bug ticket for you.

principle software developer who does not code, design, or architect,

instead, do random eslint fixes which create conflict with everyone's branches.

1 line of code "fix" per commit.

there goes 26 commits

I've been staring at the same section of code for about two hours now. I want to solve this puzzle and design it properly. I'm desperately trying to resist the urge to hack it. Not sure I can hold out much longer...

My worst experience has actually been trying to fix someone else's code. One of my friends is in a graphic design class, and right now they have to do a basic site in DreamWeaver (a small nightmare on its own, I've found that the previews they show are never quite correct). I decided I'd at least pop in to help out a bit, cause they kinda have no clue what they're doing. They are graphic design students, NOT developers, and it's very easy to see that.

One of the first things I noticed was EXTREMELY unorganized code, but that's forgivable. But...I once saw probably 5 </body> tags in someone's code, a JavaScript function inside of the <body> tag, and a bunch of CSS statements in the <script> tag that they had one if the JS functions in.

I remember seeing this stuff, and I thought "what the actual fuck?". The dude was like "yeah it's unorganized as hell, I know"

...That's not the problem. CSS goes in either a <style> tag or a separate file (THEY HAD A SEPARATE CSS FILE). JAVASCRIPT GOES IN A <script> TAG OR A SEPARATE FILE

But, I get it. They're graphic design students. They can outdo me in probably everything in the Adobe suite (except DW as I learned). I once watched a girl in there do a project in Illustrator. I had no fucking clue what was going on. And when I was talking to her about it, she said "that's what I was thinking when we were watching you fix our code"

Kinda got a little sidetracked there. Basically, worst experience is non developers writing code for an assignment.

On a three months project for a website, the "strategists" and project managers spent two months and a half discussing the "strategy". It left us (production team) two weeks to create the content, the design, and code everything.

Of course it ended being rushed and somehow shitty, but they still congratulte themselves because they "nailed" the "strategy".

</rant>

I'm in a senior level game design course, where me and two others have to create an actual game. I picked my teammates out bc I thought they've already taken classes in the subject(as they are both seniors and I'm a sophomore taking this as a final class for my minor). Turns out, they haven't taken any courses in game design and know nothing about the basics of making a game... FML, good thing they can code I guess lol.😅😓

I just saw that ARM released their design start IP for Cortex M0 for free to the masses , it’s obfuscated verilog code.
I worked on SoC design based on this in college but it took a lot of paper work to get these file but now they are free to download

This is exciting as this makes a open-source community based microcontroller design possible.

Only missing piece here is the verilog compiler they use is not open source .
Has anyone messed around with Cortex M0 DS + ghdl or iverilog. I am about to start a little side project will update more on this

Today the government from Costa Rica announced their solution to tax double any UBER charge registered to debit/credit cards.

Their logic is to pretty much do it for any commerce that includes the letters UBER. Like something out of your first Unity C++lesson

Does any developer here does design work as well as code. I got pulled into it. was expecting a only dev job, according to the job description" but the creative team start handing me InDesign task and Photoshop task with no experience in design. is that crazy or normal for front end developers?

At 1pm,The fucking boss told me to get UI design and code for a risk management system be ready on 5pm, i DID it!!! Requires no changes or edits!!! Its done!!!
Shit fuck shit!!!!

Yesterday I wanted to make a small infographic. I started with photoshop, switched to illustrator, then indesign, then back to illustrator. All of them have super shitty quirks when it comes to work like that.
Next time I will just build it as a website and screenshot it. Elegance of code-based design is just unmatched. It brings reusability, consistency and precision to another level.

That moment where you see code of someone who riddles their code with nested if-else and if-elseif statements.

I don't remember writing an else statement for years. It almost always can be avoided (and the rare cases where it makes sense I prefer the switch statement).

Yet I never grasp why people do:

```
if(someCondition) {
// huge nested code block
} else {
throw new Error();
}
```

Instead of

```
if (!someCondition) {
throw new Error();
}
// continue in the normal scope
```

And then we have experts that like doing:

```
if(someCondition) {
if (bar) {
$foo = 'narf';
} else {
$foo = 'poit';
}

// huge code block
if($foo == 'narf') {
if(yetAntherCondition) {
// huge code block
} else {
throw new Error();
}
// huge code block
} else {
throw new Error();
}
} else {
throw new Error();
}
```

Help!

If ever was to design a programming language, I'd forbid the `else` and `elseif` keywords. I have yet to find an instance where I could not replace some `else` by either a guard or an early return or introducing some polymorphism.

Devs these days, go all fancy with tech, cutting edge Uber cool shiny toys for designing a system.
Right tool for the right job is a passé. Now, the more you stuff bleeding tech buzz words, the design attracts admiration from bewildered management. [QUOTE] Again, nothing is true, everything is permitted.
Common sense is the craft and simplicity is the soul of efficiency.

When I started doing frontend development, I was quite shocked with how people managed to cowboy code their way into building fully functional products with a decent paying client base.

I am talking about fully function SaaS with payment gateway and all, but no version control beyond full backup copies, and spaghetti code everywhere you can literally bring the website down trying to change the homepage design.

... and the startups that managed to do better, some of them forgot the .git on production exposing their entire source code *facepalm*

Not drunk, still underage. I can share a wonderful story from when my wisdom teeth were pulled. My mom made me agree to not work on anything, especially code, when I came home. However, I had an awesome CPU architecture design project, and I was ready to make a few example programs in the assembly language. When I woke up the next morning with a clearer mind, I looked at the code again. ^A , ^X. Mom said "I told you so."

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???

API provider: include a signature based on these fields in this order. DO NOT ENCODE IT!

Implementation works a while, then..

*a wild apostrophe appears*

Signature no longer works.

API Provider: "oh, yeah we escape those."

Arrghhghghghhhghvhxmchsoxnsoxnwl

Not only is it a poor design for signing payloads, the documentation is shockingly poor in it.
Even the implementation example (which is supposedly from their code) doesn't account for any type of escaping or encoding.

Before anyone asks, I can't into details about the implementation.

The shit code I wrote before my cs degree is marginally better than the shit code I write now. The lack of of improvement is related to the shit job I got after my degree. Cs degree did teach me a lot of good oo concepts and design.... That I rarely use due to shit legacy code I maintain.

Sometimes I feel like I was born to code.
So I like making design, print and wear them.
Stay Safe Folks.
And Happy Coding

I just hate writing comments and the Software Design Document for the code and changes done my me.

the AI says the code I'm trying to design is very complex a problem, d'awww I'm not a failure 🥺

the solution seems to unironically be to delete half of it and make it far simpler / less features lol

why can't I make my code psychic to what I want, ragh! oh well

Customer has design review for big project I’m working on, have to sit with someone who isn’t a developer and explain my code.

Cunts, cunts, cunts.

If you don’t understand or know about code maybe you shouldn’t be a code reviewer.

The lack of one (no thinking about long term design and issues) leading to poorly designed systems that crumble when it needs to be scaled and has massive bus factor and code duplication.

I was a Windows user from the start had an old windows pc og and ever since that computer and my first HTML book I've wanted to code and design as a passion hobby and now work

My friend/partner told me on the first week that he "can code" and he will "do the front end of the web page" (its a web application design mod)

Needless to say I had to carry the whole work because he couldn't design nor write php.

Or write a report
He submitted the wrong report

He had one job
And now we arent friends anymore

"All the magic, be it in code or design, starts with a clear mind, pen and a blank paper." - Brian Wangila

so when someone in the office finds a funny design or absurd code on our sites we play a game we named roulette: we check the versioning system and find who did it... there is no price in this game, that shame is enough :)

I discovered the Source Making website a couple weeks ago, it's awesome.

It gives you clear tutorials on the essential design patterns and refactoring techniques complete with example situations and code. Love it!

You know

Sometimes I enjoy being in Facebook groups about UX/UI design and development.

Cause it's just. So. Wholesome.

((A little context: The post was about Steve Jobs not writing single line of code))

Performing code review for design quality.

So you return HTTP code 200 for 'ok'. So what do you return when things are not 'ok'?

Obviously something that's not 200. Like 300 (The message with the code was literally "not okay").

Learning New Design Patterns...

When all you've got is a hammer, everything looks like a nail. Arg.

Recently, my code in almost any controller is like so:

return (new MyFancyClass($param))->methodThatHandlesIt();

that can't be the solution to everything.... although it kind of is
how can I beef up on patterns and avoid crushing a screw into the wall without realizing it's not a nail

My class team picks me for a competition.
My team tells me to do everything and doesn't give me an outline of what they want for the code or design.
They have 7 members. + me, 8.
I have to design and code the whole app on android.
Furthermore it was my first time with library stuff.
I had to develop from 10pm to 6 am with short rests in between. Almost no sleep.
It's impossible sht. I continue with it.
When it was time for school, I just went to school as per usual.
When it was the interview someone just had to roast the judges.
Our idea was very sophisticated; was to help track down elderly or child with a gps tracker and the app.
Didnt got in the qualifiers because of the leader being an asshole to the interviewers.

I always thought wordpress was ok, not great not terrible, from a coding perspective. Now every new framework I have worked on makes me see why Wordpress is on 40% of the internet.

Now I love wordpress not because of what it did do, but because of all the really stupid things it managed to avoid doing including: over abstraction, trend chasing, using "new transformative technology" that disappears in 2 years, breaking plugin economy with updates and making devs start over, making everything OOP for the sake of making everything OOP, making adding on a bit of code take multiple files of multiple formats and boiler plate code, boiler plate code, compiling dependencies, composer, twig, laravel, one page applications, react, angular, vue, javascript only stacks (MEAN), not letting you control sql queries, protected/private scopes and design that doesn't let you fix or alter bad code others did, and the list goes on and on.

Wordpress did a lot right, and devs should try learning from it instead of making more problems to solve. Sure it's not elegant, but you known what it does do? Focus on a solving a problem. Then it does. Without inventing new ideas or concepts to inject into the code and create new problems.

And you know what else? Hooks are actually very well implemented in Wordpress. I've seen it done much worse.

Honestly my main gripe with the entire platform is a slow moving to OOP for no reason and the database design should separate post type into different tables, the current design makes it less scalable for large data sets for multiple reasons so I'd fix that.

Having a meeting to decide, when to have other meetings...
Scrum, scrum of scrums, workstream, planning, pm ,design review, architecture review, Sprint review on and on....on and on on...why can't i simply code:(

I’m working on a react codebase and company decided to add a new module.
Now im writing markup and css to ensure UX is smooth as designers thought of it.
Imagine my horror when I start to code and find out no matter what HTML tag i use, it’s been FUCKING OVERRIDDEN in the global stylesheet. AND STYLES HAVE BEEN OVERRIDDEN WITH !important

They’re also using Ant design as a component library. Guess what, default ant design classes have been overridden too. So i try to use ant design button or card, and bam, MAGICALLY SOME DESIGN FROM SOME SHITHOLE MODULE DECIDES TO FUCK WITH MY STYLES

On top of that, styles of parts of application has been written in SASS, some part of application uses bootstrap components some use third party components like tables and responsive grids to suit to their preferences. Some parts use handwritten css. Some parts use CSS IN JS and styled components. THE FUCK IS THIS GARBAGE!!!! THE FUCKING CODEBASE HAS A MIND OF ITS OWN!!!!!! YOU NAME A WAY TO ADD STYLES TO A COMPONENT, ITS THERE!!!
And the company’s management thought a “fractal” approach to maintain each individual view is “best” for SCALABILITY!!! HOW THE FUCK DID IT NOT CROSS YOUR DUMB MIND THAT FRACTAL APPROACH ALSO GUIDES TO HAVE ALL COMMON STUFF AT ONE PLACE!!!! THIS CODEBASE HAS DUPLICATE STYLES AND DUPLICATE CODE IN ALMOST EVERY MODULE!!!!

Not to mention every developer choosing to freely decide the way they should write their code without any guidelines.

HOW THE FUCK PEOPLE WRITE THEIR CODE WITHOUT THINKING ABOUT OTHER DEVS!!! SO BASICALLY I AM NOT ONLY CLEANING SOMEONE ELSE’S SHIT BUT ALSO TRY NOT TO SHIT IN THE PROCESS!! FML

I prefer it doing 2 tasks parallely during the initial phase of requirement gathering and design phase.(makes more sense if you are working extremely new system and framework)
1. Keep collecting requirements from clients and understand them.
2. Collect different designing aspects for the project and parallely, build a POC for 2 purpose: to get hands into the new Framework and also as a demo to clients. Working on POC helps in 3 ways: Improving understanding of requirement, improving framework knowledge, and playing around with code whenever bored of designing and reading tons of existing designs..
3. Once primary requirements are clear and fixed, analyse all different designs, if possible I setup meetings with senior devs, principal engineers (they help a lot when it comes to reviews on scalability and reliability of a design)
4. The above design is mostly architectural level. Once design is fixed, then I start taking each component and prepare a detailed implementation design. (Notice that whenever I am bored of designing, I spend sometime in building POC)
5. In detail design, I focus on modularity and flexibility. Anything defined should have getters and setters for example. This will help you reuse your code. Keep the interface between components in your design as generic as possible, so that in case your MySQL is change to Postgre or NoSQL, your design should be able to adapt new features..
6. Instead of building entire project, define feature targets and deliver small features.. this will help you to be in line with the requirements with minimum deviation.