*Builds a web component for a client website*

CLIENT: I don't like it, can I have it a tiny bit over to the right more

ME: Taps the arrow key a few times making it look like I'm doing something.(Which actually does nothing)

Client: 👌Perfect

😂😂😂 Wut 😂😂😂

This happened at my previous job where I worked for a dating app. It was at a time where the CEO was trying to turn the dating app into “more than a dating app” by adding tons of social features. We always had “interests” which allowed users to see what interests they had in common with another person, but he wanted to take the social component even further.

So with that, he decided we needed an “activity feed.” The activity feed would show what various Facebook connected users were liking on Facebook, posting on Facebook, etc. On a dating app. Where the majority of the audience was > 50 years old. The idea was absolutely ridiculous and everyone but the CEO knew it was destined for failure before we started building it.

But that’s not the best part. The best part was when we launched the activity feed component. We launched it late on day and went home shortly after. The next morning, we came in, and checked on the activity feed to see what was doing. It was literally all spammers liking porn/sex related stuff on Facebook. It was a complete disaster. All garbage but not just boring garbage - completely obscene garbage.

And just like that, the activity feature came and went in the course of a few days.

When they ask a newb to design a core component that was supposed to be the basis of the platform

After I submitted a code review:

Coworker: What did you mean with this comment?

Me: **translating the comment to Portuguese** Your Footer component isn't rendering any footer element.

Coworker: **blank stare** what?

Me: There is no footer tag here. **points to Footer component**

Coworker: **computing... found approximate result** I'm rendering the Footer here. **shows me where the Footer component is being rendered**

Me: **internal facepalm** Yes, I know, but I'm not talking about that. I'm saying that inside the Footer component you should be rendering a footer element.

Coworker: **segmentation fault** what?

And then I had to explain that there is an HTML footer element. To a mid level frontend developer (or so they say).

HTML is not only divs, for fuck sake.

Feeling bored? Just break a random component of your OS and spend a few minutes fixing it. If you're lucky these minutes will expand to hours. Problem solved!

New job
New project
Main React component file
20028 loc
Can’t make this shit up

Two mobile devs were talking for 10 minutes in this zoom meeting whether "the component on the bottom should be hidden, or made sticky".

I just could not contain my laughter any longer when they showed an animated mockup comparison, and the product manager yelled excitedly: "Oh yeah, I love the one where it's very visible and sticky! But could you make it bigger for me?"

Sorry HR. I will never become a grown up boy.

Me: Well, it's time to make a new app!
* opens up VS Code *
* opens folder selection dialog *
* creates a new folder called "notes app" *
* yarn inits that folder *
* installs react and react-dom *
* installs webpack, webpack-cli, babel-core, babel-loader, babel-preset-env, babel-preset-react, style-loader, css-loader, file-loader, html-webpack-plugin and clean-webpack-plugin as a dev dependency (install is pending) *
* copies a webpack config from some other project *
* creates a babelrc file *
* copies a yarn script called "build:dev" which would launch webpack *
* dev dependencies installed *
* tries to save *
* vscode doesn't save because files differ *
* tries to copy dev dependencies *
* fail *
* tries again *
* saves *
* writes bare-bones index.jsx *
* yarn build:dev *
* opens build/index.html in firefox *
* gets satisfaction *
* writes bare-bones App.jsx which is a react component but it's an entire app *
* yarn build:dev *
* opens build/index.html in firefox *
* gets satisfaction *
-- trim --
* walks out of his room to his mom's room where's sbc is located *
* grandma plays solitare on laptop *
* i ask grandma for a laptop *
* grandma gives me laptop *
* glues all components into App.jsx *
* yarn start:dev (magic of webpack-dev-server) *
* opens localhost:8080 in firefox *
* searches how to update a component prop *
* nothing found *
* registers on devrant and verifies his email *
* writes this rant *

All my unit tests work, all my component tests work, why the FUCK does it give me a 'Verification Failed' error?

1 hour later:
Oh wait this is the wrong public key

I currently have the best problem ever:

Our client applications and APIs are so fast, users are complaining they don't notice that the UI changed in between the time they clicked a button and their eye drifts to the adjacent component. So now we're having to build visual cues to account for that.

#KillingIt

Volunteered to fix a brittle component in our app. Turned out to be 26 classes of mostly copy pasted code that is riddled with todos and void of feedback for the user. Here's a pretty representative sample of this code's quality:

One component is used over 30,000 times. How many unit tests do you think we have for it? Zero. Fucking zero, Zip, Zilch, Nada, None.

WHAT THE QA FUCK!?

I asked collegue about status of component thru Skype (different countries, you know) and received answer he's leaving company in 8 days. FML.

Coworker: I give up! Please help me!

Me: What's up?

C: Take a look at this. I have this function here that gets the tab index and I'm passing it to the Tabs component over there. I'm logging the index and as you can see it's 3, but the Tabs component isn't working. However if I replace the function call with a 3 it works!

Coworker 2: While you were explaining all that, shellbug already thought about at least 3 reasons why that isn't working.

Me: **sighs** Of what type is the value that function is returning?

C: **stares at me for a few seconds** It's a number.

Me: Are you sure?

C: Well, it's returning 3.

Me: Please do a typeof.

It was string.

a stored XSS vuln in a banner-like component, visible in ALL the pages in the portal. Anyone can attack anyone.

HOWEVER this was not discovered by 3rd-party security specialists during latest security audit. I have escalated this to my manager and got replied that unless client actively requests this to be fixed should I do anything about it.

FFS.. it's only 2 lines of code.. And there's nothing I can do about it.

Eventualy I was transfered to another project. Now it's not my problem anymore.

Me at 11:00
"Ohh I need to split this component into two since too much has been put into this.. Seems like an easy task.. Will take me an hour max to do this.."

Me at 22:00
"Damnnn.. I think I have broken this code.. I am doomed.."
*Replaces all files with HEAD

Manager: Hi, here is component X with 200k lines of code. Can you go through the code and see if you can implement component Y using component X?

Me: What does component X do?

Manager: I don't know.

Me: Is there a design docs for it?

Manager: I don't know. Can you check? Let me know when it is done.

*Wondering if I should joke and say "Oh management, hard job huh?"*

*Remembering how life is fucked up unfair and I need food to survive and house to live in and follow the society's rules and work hard to make the rich richer and shove money into their fat belly of greed...*

Me: OK.

Article title: "Mastering React component composition using children"

<image of a couple holding a baby>

Image caption: "Parents with child."

**Reads the title again**

Wait what?

Software just destroyed half a year worth of work today. God bless developers. I'm getting myself a psychologist over a broken fucking server. Because software fucking killed it. And killed me with it. Do I really have to build everything from component to end product myself? Without even being a developer?

For a project day we had to write a game of our choice in Java.

"You should make this game using the JSwing library and make each component a JComponent"

Later I learned you can simply use a Bitmap as a canvas.

NEVER. EVER. BASE. YOUR. GAME. ON. SWING.
It inefficient to the top of my taskmanager. I had to wrap everything with something like a virtual playground where I had to manage everything myself to not roast my cpu.

I had alot more fun debugging hundred lines of C code with print statements than writing that shit

Enjoy this ultra⁻DRY piece of React-JSX-Redux-form component

Linux desktop fanboys: proprietary hardware support is a huge issue in all major Linux distros. It is the fault of the hardware companies.

Also Linux desktop fanboys: hardware issues are the fault of the beginner/novice end user.

Windows/mac users: *installs any component they want and has it work flawlessly without even having to read a single word from the manual*

“One of the biggest mistakes engineers make is spending time on optimising something (a component) that shouldn’t exist in the first place” - Elon

I’ve been guilty of this a few times 😅

i'm feeling so sick right now.

PM invited team for today to present his "vision": "<name of our component>: what it is and what it is not".
but it didn't make sense and showed that he hadn't understood the problem at all. the whole architecture made no sense given the problems that shall be solved. his architecture diagrams missed some essential parts that were actually the giant weak points of his concept. his pseudocode, that should exemplify interactions between components, didn't address the complexity of required interactions at all. it's like he expects some magic to happen and has no fucking clue about the requirements (but acts like it), even though he is the manager of this software project.
and when devs ask really interesting questions that fundamentally question his concept, discussions lead to nowhere and questions are not answered. at some point he literally said "there is no such thing as <name of our component>, i still have to find this out"
really!? after one and a half year, since you sold the idea for this component to upper management, and after half a year of development, you still can't tell what it is what we actually want to build? are you fucking serious?!

at some point in discussion he said that these questions need to be answered but that "there's no time left", and he ended the meeting. although there was still half an hour of meeting time left.

i'm so fucking sick of this, i hate everything right now. i can't listen to this bullshit any longer. in discussions, he contradicts himself all the time, it is so fucking surreal i'm starting to feel like i'm insane.

it makes me really sad and tired. i don't want to care about this shit any longer.

Saw a lot of posts on social media recently where people highlight a specific quote/sentence from a book/ebook and post it's picture online.
It only I could do the same with the killer ass functions I wrote, or the fifth degree nested ternary operator line of code I wrote that makes the whole component work and is the most beautiful thing I've ever seen.

Epic newb here. Like, can-barely-read-HTML new. But I'm curious and interested. I work in an office filled with very skilled developers, and I bring the human component to the operations. Not a day goes by when I don't learn something, or teach something. Sadly, that enriching experience accounts for maybe half an hour of my day. I wish it was more. Anyhoo, rant on, Wayne!

Never really used a UI framework for web development, always coded each component myself. Im using one now and I have to say it's not that bad!

I just wasted 20 minutes debugging a component that, when included in the parent template, caused an untraceable infinite loop.

Out of desperation, I finally just renamed component to "pants". It works.

...huh?

Renamed back to its original name. THAT works too.

...Huh??

Don't you feel confused if someone in your team declares variables like this?

TextArea textarea1, textarea2;
Component component1, component2, component3

textarea2.setText(textarea1);

It's an identifier for a reason, make yourself identified!

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 hell

React is a nice js framework, but I constantly find myself with 50 different files open because every component and related css file is spread across the world. I get why our frontend guy built it with so many modular components, but it makes me feel like back in the day when libraries were a thing and you had to flip through those giant Dewey decimal system drawers of cards to pull out the one little card you want to then hunt for that one little book you wanted to find that one little line from

Thanks to @sain2424, we found a really weird bug in devRantron.

One of the user that commented on or upvoted his rant has deleted that account. So when the notification component was trying to fetch the user's avatar to show the notification, it was failling and causing the app to crash.

@Cyanite the bugs you reported is fixed as well. Please update 🙃 🙃

When you're supposed to make a pcb for this SMD component, but when you etch you realize it's the wrong footprint.
Ended up soldering enamel wire tomthe chip.
hope it works

I had an interview where I had to demo rendering a video on my component. I had copilot on, so it suggested this url. The video didn't load, but the video component was rendered so it was enough.

Later, I got curious about what it suggested, and I thought about it, but didn't think it would be that.
So, I clicked on it and got rickrolled lol.

Me: I deprecate a react component, because it's bloated and no longer makes sense, and I let everyone on the team know that we're working to get rid of that component

Other Dev: Hmm, if I copy this component for every time that it is used, rename all of my copy's and delete the original, I got rid of the deprecated component...

Me: After hearing that deprecated component was removed... "Good job other Dev"

Me: A couple of weeks later after dev leaves company and I start adding some new features to the app "WTF"

What docker means:
Sorry pal, service names mustn't contain spaces

What docker says:
desc = name must be valid as a DNS component

I wonder whether this is a bug in Chrome, or if it's just Google drawing the conclusion from my northern geo-position, that we still haven't left the stage of building longships, raiding England and Scotland, burning monasteries and writing awesome poetry and literature in weird characters sets.

Well, I'm not Ragnarr f*cking Loðbrók or Egill Skallagrímsson, so I can't read electronic component data sheets the way those guys did.

I'll go grab my chisel, so I can carve a bug report into a suitably flat stone and shove it down the TCP/IP series of tubes leading to Google.

So a Developer not using a React-native component library because it is backed by Microsoft
This is next level shit

PS:- the library is actually pretty decent

Dear React Component,

Everyone else is fine.

Why is it when someone decides to enter some input in you, you freak out?

-N00bPancakes

Dear N00bPancakes,

I work in a contract position and reviewed the code of a senior engineer recently. Regretfully I can't provide context to preserve anonymity.

He wrote awful JavaScript;

- handled a single DOM element with 2 different frontend libraries
- used the logical operator && to 'chain' two methods (it didn't work) instead of returning a boolean value,
- broke everything down into minute detail (a comment box had 7 components!),
- API calls were made for every component update instead of maintaining local component state where it made sense, which meant UI updates were slow,
- animated EVERYTHING, which made my Firefox on Xubuntu i7 64bit with 16GB RAM beg for mercy.

I had a rough couple of months with interviews, with 2nd stage technical interviewers throwing impossible tasks at me.

Example:

1. Create an online Python code editor with Javascript which can compile Python bytecode,
2. Use Mesos and Kafka to create real time architecture for Tensorflow with a Javascript frontend in 1 day. (I asked, and wasn't allowed to use Kubernetes or serverless architecture),
3. Hack a website from the browser's address bar using parameters ( what?!! ),

Obviously, the next time I meet a 'senior', I'm going to tell him talk is cheap;

'SHOW ME YOUR CODE.'

A Vue application I'm tasked with fixing consists of one single huge component, wouldn't survive even the most liberal use of linting, and has a reloadPage() function.

How fucked am I?

Me and my team has been creating React components for the last two months. Today we realized that not a single component is done the Redux way (as pure functions), which means we have to refactor every component and the tests.

That's what you get for trying out new technology..

Past two days one of the senior devs has been complaining to anyone who will listen about a UI assembly containing 'hard-coded' references to a third party component causing several builds to break. The developer who added the telerik component probably had no idea the reference is pointing to his personal directory instead of a relative path. Easy fix? Uh...yea...but he just ranted to our boss for about 10 minutes about he has no idea how to fix the problem and the TFS build failure holding up his other projects.
WTF!? You fracking know what the relative path is!...just fracking change it and move the frack on.

The drama this drama-queen keeps spewing out is driving me out of my mind.

Why the fuck do managers think beacuse a component has been build by another developer a shit ton of time ago, we can still reuse that fucking code.

For fucks sake, I had to rebuild a whole fucking map component that needed contextual filter and the fuckers just add extra functionality without consulting me. And gave me a tight schedule bc the customer, who btw disappeared for 6 months, will be mad for wasting his precious fucking time.

Fuck these clients.

Last week's Android development time breakdown:

21.9% Managing state
17.7% Referring to lifecycle diagrams
15.1% Waiting for Gradle
8.5% Reading the official docs on how to use component x
8.4% Reordering auto-generated ConstraintLayout XML
7.5% Swearing
4.2% Googling “Stack overflow component x is deprecated”
3.9% Googling “Stack overflow implement component x on API 24 or lower”
3.7% Googling “Stack overflow implement component x on API 21 or lower”
3.2% Googling “Stack overflow implement component x on API 19 or lower”
2.9% Googling “Stack overflow callback y called twice”, realising its a feature and not a bug, swearing a lot
2.0% Checking if Flutter is mature yet
1.0% Implementing business logic

As usual, Friday is boring day. I made a React component to show an exclamation mark base on absolute value from a list. Took me 15 mins. The rest of 1 hour we discussed where and what color should I use. 🤦‍♂️ Someone nearly flip the table...

It's official. I'm making multiplayer Minesweeper.

There's a Trello board, Discord server, and GitHub repo.

Initial gamemodes will be singleplayer, public (like agar.io) and vs (2+ players, support for teams is planned).

My big idea besides that is to have interesting powerups you can buy or find, adding a component of luck and some exciting new rules to the game.

And I may even put ads on it and try to feed myself.

Shamless rant towards the shamless Cursey dude. 😫

So whole day I have been trying to pass a variable from laravel blade view to vue2 component file. All in seperate files. I know that I have successfully passed 1 or 0 in same flow before. So I was following the same steps to pass my string variable. It kept giving me undefined. No google helped and I had been doing all kinds of stupid useless trials. All failed.

Because it is supposed to fail. 😐
I only learned it at the end of the day.

I’ve come to the conclusion that developers who like react have never used it for anything even remotely complicated.

Because here’s reacts dirty little secret; it doesn’t scale. Not even a little. It’s flexible, but that leads to every developer writing their code in a different way.

It’s simple and easy for simple side projects, but as soon as you have to pass state to a child component, you’re fucked. And god help you if you’re modifying the state in said child component. You can try using redux, but that’s a bandaid solution to the real issue.

There are better alternatives, namely Vue. There’s no need to write unintelligible code that’s a mutated hybrid of html css and js. We as web developers realized mixing these technologies was a bad idea a long time ago.

React simply doesn’t scale. It’s flexibility, complexity, and the awful code quality it leads to makes it a nightmare for large projects with multiple developers

Some of its concepts are interesting and useful though. It’s functional concepts allow for easy code reuse, among the other benefits associated with functional programming

I sincerely hope that the hype around react dies out, and a new framework emerges that takes the best from react and fixes the glaring issues it currently has

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.

Why the fuck this moron thought it was a good idea to set a global onClick event in a react component and make it have the desired behavior for EVERYTHING instead of the only click he wanted to get?

7 places you can click were triggering redux dispatch and ajax calls that should only work on one place... Fucking hell...

Fucking people, why the hell are you reading into things instead of asking for clarification if something is unclear?

So much time, sweat and tears wasted on miscommunication.

When I said, "there might be a problem in the way component X method Y was implemented", i didnt mean go refactor the entire code of the component. Why waste 2 days of work on unnecessary refactor that nobody wanted and breaks changes + the bug is not fully fixed 😤

Of all the fuckups I love the ones with all the wrongs the most.

Like one junior: restarted a wrong app component in a wrong environment on a wrong agreed time after updating a wrong property in the config file.

Like today one of my teammates: updated a wrong script to add a wrong step in a wrong spot in the sequence... At least got the environment right I guess..

I can’t stand how designers insist on over designing <select> elements. No, 50 divs with aria attrs will not make this component as usable as the native elements

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.

*Send 2 mockup options for new component*

Them: Nice! I'm torn, which one do you like?

Me: I like the first.

Them: Great, lets go with the second!

-.-

“hi all, we are cancelling the last two releases this year due to instability that we can’t fix by the cut off. If the server returns an error, every react-native built component crashes and stops working until a relaunch”

I enjoy coding Android, but what the hell did Google smoke when creating the "Spinner" component?!

Today I had a client raise a high defect directly with my boss’s boss. I got called into a meeting and was told
I needed to fix it immediately.

I looked and realized it was in their code and not our component. I told them as much. They asked me if I would still fix it. I refused. Told them it’s not my component. Fix your own problems.

Sat their as my boss’s boss asked them how they functioned if they didn’t even understand their own component. Feels good man. All I could do is smile at them trying not to laugh.

There was this motherfucker searching a dev to build a vue component on freelancer.

I applied. 🙄

Then he started to ask me out about Upwork. How he wants to use my account through TeamViewer. And how he will pay me for this monthly.

Why am I magnetic to idiots and scammers? Can some one please Avada Kedavra all idiots? I will pay you monthly. I swear.

me: Hey. This looks like a cool component that will save me lots of time and effort in the project I'm kicking off next week.

/* Two months later */

me: WTF was the name of that component that did that thing?

======================

I really should write things down more often.

Q: What did the proud React component say to its child?

A: I've got to give you props

@AlexDeLarge and any other React guys, which do you prefer? Traditional css files, whether that be vanilla or with a preprocessor, or style objects for each component.

There are some pretty clear pros i can identify for both sides, but I'm pretty sure I'm missing somethings and I'd like to hear from you guys your opinions and experiences with either

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 frustration

PR comment: You don't need this useCallback and this useMemo, it's premature optimization, this component will not have a lot of rerenders anyway.

*remove it and merge it*

Few weeks later...
Slack message: why the app is so slow???

*opens a PR putting back all "premature" optimizations*

PR comment: Hum... I don't think that's it, but let's try it.

*merge it*

*slowness is gone*

Slack message: wow! How did you figured out so quickly???

Me: I was lucky, I guess ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

React devtools in Firefox is such a pile of shit! It's slow, it hangs when selecting and it doesn't fucking show the whole component tree when it's too deep. I'm forced to switch to Chrome when I need to debug.

Anyone here has problems with it too?

After reading some rants abut stupid project managers I remembered this situation that happened to me a decade ago.
One of the tasks was to move some html component to different place on the page. The whole page was a mix trs and tds and to achieve that I had to rewrite the whole page structure. I estimated around half a day to complete that task. It was my first job and I was not great back then, but still it was reasonable amount for this task.

Now lets introduce my PM : the guy was a complete tool. He was a former hardware store manager ( ͡° ͜ʖ ͡°) and had no idea what we were doing.
He started ranting how on earth such simple task can takes so much time. I started explaining myself, but he wasn't listening. Instead he started sharing his screen, he made a screenshot of the page, pasted it to the ms paint, cut the component, and moved it to desired place. Then he said : It took me like 10 sec to complete the task and I have no experience, maybe I will replace you?
I was speechless. I had no words and I just kept silence.
Then he said he would reassign this task to X, because he is competent.
X spend more then 4 hours and I heard no apologies.

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.

That feeling when you were so happy about react-native, and was pretty sure at the beggining about the achitecture of your app and js libs you are about to use.

Im here sitting with redux, reselect and still dont know why I cant just do a REST call and format data in the container component.
Why react is so hard, or am I dumb?

Why on earth is machine learning left so obscure! Only 100 different ways to talk about the same component.

Sprint 0: This design is the appropriate amount of engineering abstraction.

Sprint 2: This is over-engineered, too much work

Sprint 5: This is under-engineered, too many edge cases

Sprint 10: This is over-engineered, component Foo could be replaced by a bash script

Sprint 42: Foo is now the cornerstone of half our business logic

Worst of an job in IT? Coming home and having to fix computer still.

I fucking hate it. I fucking hate computers. There might be great stuff like nifty algorithms, grand theoretical theorems about formal languages, Lisps,... BUT that's so far away from the mundane atrocities we have to put up with when it comes to sth like installing a printer.

Newest release of driver won't install a plugin without helpful error. Older release works.. for printing some pages... Then some component (cups-filter) keeps on segfaulting.

My boss: Write unit tests for this angular app
Also my boss: what do you mean it will take months to write the necessary mocks for our 177 specs
Also also my boss: why would you need to mock anything for a unit test
Also also also my boss: Just let each component import all the other real components, nevermind that that's an integration test and not a unit test

Recently I have lots of very unproductive days. I m just very tired and even coffee puts me to sleep at work. What's interesting is that as soon as I open something interesting on the web or start working on some new component it all goes away for an hour or so.

So I just wanted to ask you if you have weeks like this.

How can I get myself fixed :(

Oh no...

A <FlatList> as a DIRECT child of a <ScrollView>... I mean, I'll give you the benefit of the doubt if you forgot or it was buried in a nested component... but... it's just sitting right in front of you on the same exact component... it's like, did you even test this once and see the warnings?

God these 'affordable' devs truly aren't actually worth it.

They really aren't.

You spend just as much time fixing their clownish mess as you get for "saving money" with their cheap rates.

Another day, another clown dollar in clowntown...

SHEESH

Taking a 4 month Software Engineering course in University. Spent the last 2 months making Traceability Matrix, Component Diagrams, Deployment Diagrams, Sequence Diagram and not a single line of code was written.

Is this how it works in Industry as well? Lol.

This type of post might be good for a weekly rant (if it has not been done yet) "Most Bizarre bug"

So I am working with laravel and vuejs and I use phpstorm as my IDE and today I had the MOST bizarre bug. I'm working on a cryptocurrency website and I'm making a vue component that is going to be a stratum generator for miners and I wanted to make it a component in vue so it can be used anywhere in the site. So I wanted to call the component "StratumGenerator.vue" and i didnt think that this would be an issue. Oh boy was I wrong. So immediately my syntax highlighting did not work nor did emmet autocomplete which is something I can't work without. So i go on for about an hour to fucking figure out how to fix jetbrains vuejs syntax plugins and a very long story short it was because THE FUCKING NAME WAS "StratumGenerator.vue" LITERALLY ANY OTHER NAME WORKS

I've checked its not a blacklisted keyword Stratum and Generator work fine on there own its also not a length thing so right now I have not a fucking clue on why it does not work but i'm glad I figured out.

JSF: Yeah, we make it so can focus on what's important and you never have to write HTML or CSS like those lowly web developers.

Also JSF: You can't nest <h:form> components because nested forms are invalid HTML. Oh, that breaks the composite component you were trying to use? Ha, fuck off.

Primefaces: You know how you can just provide an ID and OverlayPanel will open on its own? Well, for a Dialog, the API is completely different. Here's a glob of JavaScript in an onclick event.

I swear this entire thing was regurgitated by a murder of seagulls.

Me: *holy shit there's a lot of code in this template file, I should probably break it up I to components*

*goes through the effort to break everything up into component parts*

Me: *i should quit being lazy and actually register all my templates the way magento wants me to*

*5 hrs later*

Me: fuck this! *<?php include ...?>*

WordPress uses 25+ MySQL connections per person. MySQL limit is set to 100. 4 people can bring down a critical component of the company. Only fix is to write custom MySQL connector using PDO and persistence connections. Added a Resistor cache just for good measure.

If you use ID selectors in a stylesheet for a component you reuse in the page multiple times you should be shot.

Oh, as a noob dev my team was using a dropdown library for our filters in the website. The code was messed up cause they kept changing the design halfway through dev and after releases and then finally after some releases, the client wanted multilevel options as a new requirement.
So I scrapped the whole thing and made my own multilevel dropdown component (there were no decent libraries then) and we used that from then on. It has many issues now that I look back (who cares about keyboard interaction right?). But that is a refactor for another day.

Is it just me or is systemd 240 royally fucked up?

My containers running Arch don't get connected to the network and systemd-networkd fails to start. On my laptop, the network is also unable to connect sometimes. And it consistently fails to complete shutdown without hard poweroff. The only viable temporary solution was rolling back to a snapshot in ALA that still has 239. Is that really supposed to be how a critical system component like the init is supposed to behave and get taken care of its issues?

Fuck QA, amirite 🤪.. seriously, that's even worse than Windows' "features" 😒

ECS-Concept - a Entity Component System library in C++17/C++20, for learning purposes.

The best way to describe what I had to do today is I "Channeled Macgyver"... now production is working.

⚪Data wasn't flowing as expected.
⚪Component written by our team was blamed.
⚪Boss asked me to bypass the component so data can flow.

Sure, I can fix that... Give me a car battery, a roll of duck tape and a butter knife. Data will be flowing in production shortly.

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

Number of lines on ONE of the javascript files in the project I'm tasked to convert to a modern, modular, component-based web app: 3022.

There are 6 of these.

I see a lot of talk about complex numbers, and yet
for all they are worth, I have not once been
able to find an explaination on how to calculate
them by hand, namely the real component.
For example
(-5)**0.5
(1.3691967456605067e-16+2.23606797749979j)

2.23606 is obviously just the square root of 5, but where the hell did 1.369 come from?

Apparently no one fucking knows, and no site I've found gives a simple explanation for someone new to math in general.

"use a calculator", "hit a button",

How about no.

Adobe labs released one new component, I played with it after two days. Went to an interview with huge company after two weeks for a developer position, the interviewers was from different departments, they asked about one technical challenge they have, then I suggest the new component as solution, they gave me small task to implement using the component, I delivered it next day... Then they hired me in R&D department. It was great days.

Me:how about this one ui component boss. I think we must fix it.
Boss:just drop it out, do another job. wait customer to complain, after we got one complain then you fix that.

We're using Angular in the shittiest possible way.

It's wrapped in .NET, the code follows no standards and we lack any sort of component hotload functionality with _fat_ data.

When I change a SCSS style, the whole page reloads and it takes me 15 minutes to get back to the state I was in to say "Hmm, more to the left."

I hope this place burns to the ground.

Can you fucking imagine this tiny fragment of a large complex software built in nextjs?

How many page.tsx and layout.tsx of that exact file names is gonna be there?

How can you track in this folder hierarchy which page.tsx is for which component etc?

How is this clutterfuck of a structure good and loved and approved by developers?

Nextjs is a fucking double edged sword. As much as how good it is it is also bad as bullshit

Forked a project of GH, which will remain nameless, and ran into this beauty...

// Not actual code, just respresientative...

{true ? <Component /> : null}

This is the LAST TIME a critical PC component will fail me in the middle of a project. Wtf is up with hardware makers these days? Why can't you make a video card that will last for more than a year, AMD?? FFS!

Desktop for gaming, laptop for code. Now to redo my workstation AGAIN. 😭

This is embarrassing, but the first days of learning about AngularJS I had to implement functionality about a new component of the WebApp I was building.

I did a good templating, I build the component along with its controller and services, I verified there wasn’t any memory leak and that everything was in an isolated scope. Yet nothing at all appeared on the app. It took me more than 30 minutes until I realized...

I didn’t put the source code on the index.html file 😅

For people who know more about compiled languages such as C or Java... that’s like not putting your source code file in the makefile. 😅

I felt literally like the dumbest person in the planet at that moment. 😀🔫

Sifting through a React class component that is over 1000 lines long.

When was this written? Not in the 1950s like you might think. Just over 3 months ago.

Kill me.

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

Oops accidentally created this Angular component in the wrong directory. Better run the Ng command to remove the component so I don't need to remove the files and references in app.module.ts otherwise it would take an annoying amount of time to track down the right lines there and it also opens the door to human error!

......shit

Company started automated testing recently, and the devs need to review the test scripts.

The tester assigned to my component writes script to trigger button click and nothing else to verify the result.

I couldn't​ even. I just left work for the day.

A legacy custom made WordPress Theme.

Old developer made main styling sheet with 8000+ lines of code with no component separation.

Here is a little story about why I do not like to have to purchase developer tools and libraries..

Long story short it has taken at least 10 people more than 3 months to purchase two licenses of this component library which we still do not yet have licenses for.

It all starts with this guy who works here and has the job title 'solution architect'. He saw an ad on a website about some html component library. Then he asks me and the other developer here to look at it. He is super excited saying things like if we save only x days of time the cost is nothing in comparison to developer time..

The other developer and I both spend a few days reading the docs and trying some sample code. It offers some things we can use but I suggest not bothering with it.

Despite my suggestion he goes to the technical manager and they write up a business case. After about a month our receptionist cc me on an email chain from the it commercial manager who is asking for the licensing information so they can add the component creator as a vendor in the purchasing system. I send them a link to the component website which lists all that.

Jump forward two more months to last week and I got a spam email from the component company saying they have some new version out. I am wondering what has happened so I ask our receptionist she says it is with accounts payable and waiting payment - but it is marked urgent and she will find out.

Today I am cc in an email saying they have paid for it two weeks ago. So where is the license info? Nobody knows.

Why do front end developers like to write their HTML/Component markup like this:

<div
id="test"
class="test"
>
Test
</div>

That lone > bracket absolutely irks me! Looks ugly! I prefer the Android style:

<div
id="test"
class="test">

<span>Test</span>
</div>

👌clean

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!

How to fuck a web developer:
1- Introduce a shiny new shitty web component that is nearly impossible to figure out how to change it’s fucking background color, yeah.
Welcome everyone to 2019 why even it was so easy to change and customize your own shit, let’s just introduce thaaa faaacking web components and fuck everyone else. Let everyone learn again how to do the simplest shit ever.
Yes fuck everyone that is used to change and customize in an easy way.
“yUo wAnT uS nOt tO UsE SoC anD cLEan koOde?”
No no no. We will fuck you instead.

- Searched for a cascader component for React
- Installed it
- Lost 2 hours trying to load dynamic options
- Turns out that there is a parameter named "isLeaf" to identify when a node have no children, which is also used to allow the loading of dynamic options
...

isLeaf...
isLeaf......
isLeaf.........

*chills*

Uninstalling Visual Studio is a mess. It'll leave behind hundreds of silly component, which is funny because the main reason I started the process was to clean up a possibly corrupt installation. It also left behind a Docker tool component, which I can't uninstall cause that installer needs VS itself :D

wow... the regular react community sucks...

where with react-native 3rd party libraries/components have very clear and detailed docs, the normal react libs out there are like:

20K starred component
"here is a .txt file with some props, TS? yea we use it, but everything is just set to ?: any"

quite the shame :/

The beginning of my small app. Just a small question to the devRant community. As I am relatively new in Android app development I was wondering which layout is okay to work with?
The reason behind this question is that I have found that sometimes I'd move a component(e.g., button, text field) by a small fraction and boom! everything else is messed up.

Happy days, yesterday we updated form 16.3 to 16.4 and thanks to them fixing the bug in 'getDerivedStateFromProps' my broken code is now breaking.

Don't you just love it when features inadvertently depend on bugs. The entire component ONLY worked properly because of a react bug.

saw this girl's post LinkedIn. a typical influencer like format post which had nothing of value and instead was a post asking for help with a question (basically it consisted of a android doc link for an android component followed by some hashtags like #6969daysofcode #day69 #xyz and "has anyone used it before?share resources")

then i noticed 2 things:
1. she works in my previous company in the same position that i did , and started a month after i left. so basically she is my replacement.
2. i and my senior (who also has left that org) had created the exact same component that she mentioned in the post, and we had created that component as an awesome plug and play component that would handle multiple usecases with decent documentation

now am having this urge to dm her the exact classname in the code to see and learn 😂😂

or i can play this uno reverse card and write a blog on that component writing another influencer like post: "in my previous company, we created this awesome component and here is how it works..." her boss (our TL) also follows me and what i know of him, he will be tagging her, pinging on slack, and discussing it in the DSA the next morning 😂

I learned today I can "npm install" directly from a GitHub repo. This allowed me to create a React component (viewer of gLTF files) for a 3D game and share it with my team. I know I could've published it to npm registry, but I didn't want that since it's a very specific component for our project, and private npm packages are very pricy.

Hope this random !rant will be useful for someone wanting something similar.

Today I finally proved that a pre-existing component was overwriting the output of my component. It only took 3 months to find out the proof of it.

If you write a blog post on how to build “some-component” and the first step in your article is to run “npm install framework-some-component”…

I hope you die in a fire.

Today I spent hours trying to figure out how the hell to add a Material-UI tooltip onto the ClearIndicator for a react-select multi-select component to warn the user that it would clear _all_ of their selections. Followed the examples in the react-select docs on how to make use of replaceable components, but all of their examples used a different library for the tooltip component, and there was no way I was going to bring in _another_ library that was going to add even more dependencies to the application.

In the end, my problem was that all of the examples were with components that could carry a ref and the component _I_ was targeting was a <path> element, which apparently can’t.

Solution? Add a div between the tooltip and the component I was replacing.

*facepalm*

I get pissy when people don't use linters, then I just spent ages super confused why the data wasn't loading in my component, then realised I hadn't decorated my class and I've been ignoring the red underline for the past half hour.

Seriously need to follow my own advice.

Trying to review the architecture of an internal boilerplate... After having explained Atomic design principles, and the "component approach" to my colleague, he still managed to come back to me with:

- plugin/
- module/
- components/ ....

in his architecture... I don't know what to do. I'm depressed. FML. I'm quitting.

Can you make me this page please.
Me: its done its 100% like the psd you send me
She: yes but this component is bigger then this one
Me: its the same here the css proof
She: can you change it ?
Me: ( this will change the hole component and douin the same shit ) yes i will do it for you.

She: again this is not the same size

Me: ( what the fuck i said to shut is mouths ) ............. Fml

At last, after a year and a half working with legacy codebase, I got the greenlight from the seniors to refactor my team's app to modern front end technologies. You know, webpack, unit tests, component based architecture and shit.. I really love it!

My PM doesn't look as enthusiastic though...

Bad leaders are simple - they give someone a job - simply to return an eon later unhappy with the progress - without seeking to understand a single component of the events that transpired during their absence. Place this mentality at the top of the hierarchy, and it will cascade throughout an entire organisation.

Being blamed for and written up by your manager for a late deliverable on a ui component that the same manager failed to provide the APIs for in a timely manor.

Group assignment: writing a own Java logger component in a group of four, using nothing else than Java SE libraries, Maven and Jenkins. The software must be able to substitute the logger component without recompilation, just by editing the config.xml (setting jar file path and fully qualified class name of the logger).
I asked around on Slack which group is ready for a component exchange, so that we could test the switch. I found another group and I started doing some testing.

Then I got a `java.lang.NoClassDefFoundError: org/apache/log4j/Logger`. I got in touch with my peer from the other group and asked him, if they've been using log4j. Apparently they did, so I told him that the assignment was to write a logger of one's own, not just using log4j. Then he told me: "Uh, ok, I'm going to tell the guy responsible for the logger part about that..."

X-D

"Exception has been thrown by the target of an invocation"

This error message pisses me off. I know the SSIS Script component is capable of catching exceptions, you can wrap all your code in a try/catch (please don't) and get an exception. So would it be so hard that if the Script Component throws an exception that it tells me what it is instead of sending me on a goddamn scavenger hunt?

The whole bullshit system of errors is why I hate SSIS. Just tell me what went wrong.

I did what I wasn't supposed to do, wrapped it in a try catch and it gave me a stack trace and an error message and all sorts of actionable shit. But why the hell can't it just do that on its own?

There is literally nothing worse, except maybe Hitler, than a goddamn vague error message.

First rant after coming on this website.
Took me 5 seconds to find the search component, GUYS? VISUAL DESCRIPTIONS?

its two years since ive told a story here but lets go.

we got a new client, who is revamping their infrastructure. i gave some tasks to 2 dev ops guys (i am not devops). they were primarily bash scripts that needed to be altered. (ofc i can write scripts it takes a moment, its their jd)

after a week of chasing them around, getting no result from them, i end up doing it myself because client needs it and the company needs this client. for one task, they told me it does not apply to the component we were working on. (it did, and i did it)

we have a meeting with higher management, they asked me how did i implement it, i show my entire working, my backtracing etc (everyone knows this is how you approach huge system, component focused strict deadline task). it was infuriating how they approached it by trying to understand complete system in one week. i asked them why they hadn't taken component specific approach. they said they tried but failed because..

[this because is the whole reason for the rant, because i believe this because should be a fire-able offense]

..because we were not using VS code to find things in files

HOW IS WHAT TEXT EDITOR YOU USE OR DON'T USE AN EXCUSE

ARE YOU GUYS GETTING THIS?

I had an interesting mystery the other day. I work in the UK, but I'm working remotely from the US for a while. First day, I made some changes, ran the tests and they failed. Weird part was the failing test was for a component I hadn't touched. I took a closer look, and realized it was a date off by several hours. The test was checking that a passed in date appears in the output. But it was creating the date by parsing a string. The library I was using defaults to local time, but the component uses UTC. So, I had inadvertently created a unit test that only passes when run from UTC. But I had never noticed before because my work is in that timezone. Yikes!

When you join a project that has no testing, no component policy, a lot of css mixins, that has to work simultaneously as a pwa, android and ios app.

Oh, yes, obviously no documentation at all *flips table*

I was in dependency hell for two days.
Im a junior working in a team creating an ember app. Suddenly a main component refuses to work since an addon threw "EmberObject undefined"... Nobody could reproduce it and we where out of ideas, so I tried fixing it for 2days (7h total). I finally got it working after updating yarn :D
It never felt so good working again :)

If I have to write that web component again just because “well I think this technology will be better” I’m going freak out...

"Warning: Functions are not valid as a React child. This may happen if you return a Component instead of <Component /> from render. Or maybe you meant to call this function rather than return it."

WHERE. TELL ME WHERE THE FUCK THE PROBLEM IS HAPPENING. OR SHUT THE FUCK UP.

The code is under "GNU General public license as published by the Free Software Foundation, either version 3 or any later version" and I used it as a reference.
Should I redistribute the my new code under the same licence and make the source open? Should I make just the component open source or the entire app?

Glad that I've worked about 2½ days on an angular component, with all the struggles, brainstorming and meticulous care for "good" and "readable" code, just to find out that I misunderstood the requirements. Had to completely rewrite it...

Sometimes angular can be really damn annoying with it's "Error handling".

When just one component has an error (For example using an non-existent form-control) it'll not only crash the component like it should, but the entire app.

whyyyyy do you do this to me

To use Unity with VS you have to get Unity Build Tools as a plugin.

Alright, I'll download that.

Oh but now there's an error with connecting to unity, I need to get a newer VS and switch to the 2018 version of the engine.

Ok fine that's annoying but I guess I might as well upgrade.

Oh now there's no Intellisense? I guess I need to reload my project.

Oh what's this? Some major build error due to a missing component from Vs 2015?

This is getting stupid, fine let me install it.

Oh but to install the component you need to rerun the installer for VS, fine I'll redownload that.

Oh but apparently the installer _I JUST DOWNLOADED A FEW SECONDS AGO_ is outdated and needs to be upgraded. I can't _not_ update the installer and still install the components because that would be stupid, why would we let the developer decide what versions to use obviously they don't know what they're doing I mean it's not like they know how to use computers?

To get simple code completion, let's force developers to download an installer that then needs to be updated to install a component for this giant IDE that also requires the 2015 version of the IDE to be installed alongside a special plugin and patch designed for a specific game engine.

All this. For fucking code completion. I can't even get Intellisense to work in VSCode without fixing the issue since the C# extension in VSCode just binds to Visual Studio tools and runs the same shit with a different GUI.

To the reactjs-centered fucks who develop the popular web component viewing software called storybook: have you ever heard about semver?
89 alpha/beta/rc releases for a minor update 6.3 -> 6.4 with "100's of fixes and enhancements" "in preparation of the HUGE 7.0 release". Gee I wonder will it have 1000's of bugfixes? How bug-ridden is this software?
Every minor upgrade since 5.x is backwards-incompatible and requires a day of frustration finding out in how many more fucking NPM packages you split your codebase just because it's cool. I know move fast and break things, but some of us have other things to do than resolving node_modules incompatibilities you know. "No just hit 'npx sb upgrade' you say". I did, I really did! And the browser showed a blank screen of death with tons of cryptic React errors, it really did! Thank God you abstracted away all your dependencies in that sb command, now you can't even read the docs about what could have gone wrong with a specific sub-package. You have @storybook/html but the docs redirect to React pages, so good luck if you use something else

This is so sad... like.. the IDEA of storybook is great. But why did faith put the capacity to develop such a tool into the hands of people who think the world centers around React and JSX.. HTML should have been the default, and then you build on top of that for your fav framework, not the other way around

I can now appreciate some design decisions behind react-redux after witnessing some angular OOP clusterfuck.

I am sure there is some clean/correct way to code in angular, but everyone is treating angular as java.

Some angular application (the one I have to work with) is littered with network calls. It's difficult to spot duplicates. People usually resolve promises everywhere. In services, in a top-level component, or in for loops. In react, people use apollo/redux-query or redux-saga to handle network calls. Since these libraries prevent duplicate network calls internally and reassigning apollo network call function or redux action function is always useless, it's easy to spot all network calls in a component tree.

In angular, it's difficult to trace data mutations when data can be updated everywhere. In react, you can easily find UI state updates by tracing state hooks/dispatch/apollo usages.

In angular, it's difficult to trace data pipeline. Since everything is imperative by default, people need to add update functions in data subscriptions. With all the littered mutations. Soon you will lose track of what the fuck is going on.

I hope angular get the agonizing death it deserves and fuck everyone who codes JS OOP clusterfuck UI.

Android stu. make you feel you're not up to date anymore with all the frequent download component.

Always nice when you discover that your hardware has an *ELABORATE* HARDWARE OFFLOADING ENGINE with full protocol implementation for something you spent two months writing software for...

Well, at least the current solution works like it is supposed to. Don't know that yet of the hardware implementation.
It would save 4 euro component cost though if we switch to the offloading engine

First day at Jetpack Compose: Wow, how cool!
One week of Jetpack Compose: This preview never works right!
One month of Jetpack Compose: Damn! There's no mature component to this shit!
Two months of Jetpack Compose: There's no going back and start using embedded applications as intent.

Don't get into it.

The other day I wrote a bit of code using a new component. I spent three hours trying to find why it wasn't working - how was I using the component wrong? It was rendering its source html directly in the browser.

I had forgotten to import the file defining it.

Just curious on whether or not to open source something or not...

As some would have seen I'm working on a game engine/framework and putting a lot of effort into the development terminal (lumber camp) and had a fair few people show interest in it so thought I might chuck it on GitHub as I go but I don't want to allow for merging until the main component is at version 1 and stable...

Should I release as I go and not do merging or wait till it is at version 1?

!rant

I've tried Ionic in the past, and put off development with it because I couldn't get it to be performant without crosswalk.

In 2015, React Native put an end to the 'Are hybrid apps viable?' argument. It had a much smaller compile size, large component library, and is very reactive.

Ionic recently released news on scaling back their tools to focus on core offerings. I can't help but feel they're flogging a dead horse.

I'm sure the Ionic team has very smart people on board. Can't they see they're about to be 'Parse-ed'?

Finished && deployed a big release yesterday (like the main component, only changed in 4-5 times over the years).

You know the mental state of "ahh it's done"
I couldn't even savour it and theres needless work given to me just-because. It ain't urgent, it ain't high-priority, and IT'S A FRIDAY TODAY? :v

No wonder the smarter-than-me predecessors left this job. One can't even get a sense of satisfaction after putting that amount of thought and work.

i fucking hate react and don't understand react

Is it cleaner to have useContext to pipe in override test data for storybook and write an outer context for that code only? Real production code can ignore and not set this.

Can child component onHover update parent's stateful variable to unpause the urql/graphql datafetch in parent data wrapper component. Parent pipes queried data to child component to properly display on hover that kicked process off.

Frontend devs who mindlessly use bootstrap because everyone does and end up using only the responsive grid component, which they mess up completely in the end as well

Not a rant.

But, who loves to run gource on your project's directory and gets excited staring at the awesome animation created based on the git logs.

+1 If the whole team stares at it and yell "Look, thats me adding the .... component"

Started writing a blog post about a simple React project I created. Several hours later and I've finally gotten to the part where I'm creating the first component.

...this going to be one long-ass blog post. :P

Working on a bugfix which has surfaced after 2 years, I hate the way that nobody thought of perhaps tidying up a component before leaving it gathering dust. Basically found dozens sections of identical code with minimal changes both for production code and testing :/

My Frontend team lead came to me today to show me some "amazing" React component he wrote.

It was a pile of overengineered shit.

Ok the ionic datetime component horror ended. I got it working good enough but I'm not proud of my code. The whole thing is a giant hack parsing dates to and from strings, switching locales, setting months and days and using the month as a daypicker as this fucking component does not allow me display day names in it, only month names. Such a mess... at least now I can work on the stuff that matters.
Actually though about making this open source... I reconsidered.

Wrote an entire complex React component in about an hour. I'm talking it fetches data, manipulates state, renders child components, has some CSS-in-JS, and even uses the React componentWillUnmount method

I'm tired now

You ever look back on a piece of code and think 'damn, did I really write that?'

Spent one hour looking for an error in my PCB only to find that the symbol and the actual component of a part in the parts library differ in terms of pin numbers. The colleague who created the part is already retired.

1) Had to fix severe bugs in a dynamic UI (configuration-driven forms) component.

Recognized undocumented Copy/Paste/Modify/FuckUp driven variations of the same component all over the project. Unsurprisingly, the implementations covered 99% of the antipattern catalog on wiki.c2.com and could compete with brainfuck in regard to human-readable code.

Escalated the issue, proposed a redesign using a new approach, got it approved.

Designed, Implemented, tested and verified the new shared and generic component. Integrated into the main product in the experimental branch. Presented to tech lead/management. Everyone was happy and my solution opened even more possibilities.

Now the WTF moment: the product with the updated dynamic UI solution never has been completely tested by a QA engineer despite my multiple requests and reminders.

It never got merged into baseline.
New initiatives to fix the dynamic UI issues have been made by other developers. Basically looking up my implementation. Removing parts they do not understand and wondering why the data validation does not work. And of course taking the credit.

2) back in 2013, boss wanted me to optimize batch processing performance in the product I developed. Profiling proved that the bottleneck ist not my code, but the "core" I had to use and which I must never ever touch. Reported back to him. He said he does not care and the processing has to get faster. And I must not touch the "core".

(FYI: the "core" was auto-generated from VB6 to VB.Net. Stored in SourceSafe. Unmaintainable, distributed about a bunch of 5000+ LoC files, eye-cancer inducing singlethreaded something, which had naive raw database queries causing the low performance.)

Cool project, cool people, but everything-just-works™ code makes it hard.

Every component has its own logic for the things that are already made, every table has its own filters and those filters are the same piece of code in every component.

I'll complain about this shit tomorrow as today I spent my day making a fucking table work, can't even copy the shit as it has its own intertangled logic that doesn't make any fucking sense.

Yesterday I ate Bolognese, today I'm working in one.

Lol the funniest thing Iis that dude who wrote this piece of shit is gonna review my code, can't wait for that call.

And yeah useMemo() on every fucking function. Functions pulling shit directly from state and returning it straight away...

Literally this:

const filteredData = useMemo(() => { return stateData }, [stateData])

Ok, what the actual fuck.

The weirdest wtf was that typescript is used as it should, like every case covered correctly. Not sure if gpt or just dumbasses working on this pos.

I love the React and Sails docs. The contents are human-readable. Perfect for idiots like me since most docs are $h!+5%&* (hint: Git).

For fucks sake we enforce monolithic design these days (even putting 5 different languages in one component-file) but not a single fucking tutorial, idea, design hint or article about how to put the fucken backend in that project, too.
The data structures used by front- and backend will be the same, do I really need to setup another oversized webpack buildchain, containing 90% the same sources to have my backend development in a different repo?

what the fuck.

So, I got a task to modify a component from another team in another country.

Me: Ask the team for the repo link and explained what I was going to do.

idiot: You don't have access to our repo, I can do the fix next week and upload the code to confluence....

What the actual fuck. How can you even go there?!?

Linux.

Guys, I need some inspiration. How are you dealing with memory leaks, i. .e identifying which component of the system is leaking memory?

Regular method of dumping ps aux sorted by virtual memory usage is not working as all the processes are using the same amount of memory all the time. This is XEN dom0 memory leak, and I have no more ideas what to do.
Is it possible that guests could be eating the dom0 memory?

$ ng generate component gofuckyourself

I am having a fun time learning Angular. It’s way different from React.

I do like the css scoping a lot. Also it’s strange to not have to deal with state.

I am learning it because I see the job market requiring it as opposed to React.

Any React peeps feel me?

Substantive post / question time!

So I'm working on this project that isn't a disaster but very much suffered from a lack of planning (both on my part and others).

This is a feature that involves all sorts of ways to view and manipulate some records and various records and so forth... I mean what isn't that really?

I think everyone tried but we didn't realize how many details there would be and how much we would need to (well I demand we do) share code across pieces and how that would slow us up when we realize feature A needs to do X, Y, Z and ... well obviously that means feature B has to also...

I'm not really upset about this, it's progressing and I'm learning. I'm writing it all now so it's under control, but...

I want to be able to display, visually where we are as far as each component of this project

- Component A
- Description:
- Component A does things you don't want to.
- Has features:
- Can blow up things in a good way.
- Produces flowers and honey on demand
- Missing features:
- Doesn't take out the trash.

And so on for component B, C, D, Z.

Right now I'm just using a plain old document file to write up a status / progress type thing now.

We use Teamwork to manage tasks, but I kinda hate it. It's similar to the above example in being able to bust out lists... but they're not connected in any way. All the details are lost on these bullet items as they're limited to one line when you look at everything ....

It's the classic case of a tool that shows lists ... but doesn't promote or allow for showing any connections between them...

And really the problem with this project is that we built little bits and features here, and little bits there from the outside in and ... really we should have built it from the top down where we had to face a lot of questions earlier.

Anyway does anyone know of anything that has project type management / status / progress stuff that is VISUALLY helpful .. not just a bunch of lists and progress bars?

I know I didn't word this well but I'm open to even wrong answers....

ANGULAR 5 HELP REQUEST
Does someone know why tf router.navigate doesnt initalize the given component in Angular 5?
Stackoverflow doesnt provide the required answer...
The component is called (and works) if i reload the page on the correct url. Even the URL in the adressbar changes on router.navigate.
pls no h8

I'm so frustrated right now.
I put a lot of effort in a (voluntary) web project where its main component is based on a html table. Everything tested in dev (Chrome, FF), demo deployed and now I open it in Safari (macOS) just to discover that the rendering is broken. A Google search revealed some people with similar problems and many unanswered StackOverflow questions. It's unfixable.
Why Apple? Even MS got its sh** together.
It's unpaid work... I just wanted to something good.

Today I had to fix a bug and it took me about 2 hours to find out that it related to a bug in a component which doesn't belong to the bugs component. In development everything where fine. But after deployment the bug occured. Found out that when running Vue webpack projects in dev it handles errors different, kind of a global try catch block. After deployment the application breaks.
This teached me again that we should not ignore any red error line in console.

Fuck you Spring and your stupid cryptic, useless, no relevant information error messages.

"Oh I am crashing violently because some of my internal component cannot automagically talk to another my internal component" says spring.

Well shit, why do I let you manage your own dependencies if I still need to hunt down what garbage transitive dependency you bring in 5 time.

YOU HAD ONE JOB!!!

I fucking hate the person that created the ionic timepicker its such a fucking mess if you want to do anything advanced and it's so poorly documented that most of the time you just have to guess what you should do. Best part: this fucking component doesn't even use a Date Object it uses A FUCKING STRING that it parses, so I have to parse, unparse, parse, unparse. Who in their right mind thought this would be a good idea?!

What frustrated me the most was when I tried to use their min, max functionality. I used the component as a timepicker, so I ignored most of the Date Object and just initliazed them at 0. Afterwards set the hr, min, sec and did the same for the max value. Doesn't work... It just bugs out and I can only pick midnight of that day... Okay. I kid you not: tried for two hours to fix this shit. Console logged the crap out of that thing. Everything seemed right. Out of frustration I then just initlialized the max value like normal, so the date is the current date. AND SUDDENLY IT FUCKING WORKED. WHY?! FUCKING NOBODY KNOWS. WHO, WHY, WHAT?!

God DAMN IT!!!!

I swear, every single time I get close to a Spring project I'm elbows deep in shit.

Like this case... I have to explicitly specify @DependsOn for my @Component, so Spring could autowire constructor parameters. If I don't, sometimes the app starts fine (if I start it through IDE) and sometimes it fails, saying bean could not be created (apparently, there's some functionality gap causing PostProcessors not to be called if the bean is first touched by a constructor autowirer)

when they say frameworks are good and fast, I say "LOOK AT MY LIFETIME SPENT WORKAROUNDING THEIR ERRORS!!!"

I'm moving some frontend views to a new layout. It involves lifting some state to increase performance (not load the same data 10 times). All fine and dandy - until I reach my colleagues code. Sure, they've not done a lot of frontend, but they don't ask for help either. So let me tell you - their code is crap. Really crappy. Better of, it's a bit more of a complicated component because it relies on some external constraints from another company, and that combined with the shitty code results in me having to rewrite the whole damn thing. Nice. Really fucking nice.

Spot a mistake in the code.. Should i:

1. live with it and continue to build on top of it.. Do a special validation just for this special case.. Which is a quick solution

2. or rebuild that component.. But have to rewrite the 4 controllers that is using that component.. Which is a long solution

The daily dilemma of taking over someone elses project.. 。・゜・(ノД`)・゜・。

Why are hooks so awful?

What justifies having everyone using React relearn how to do things when hooks do not bring any new features to React?

Why does getting setInterval to work with hooks require a ~3000 word blog post by a maintainer which constantly assures you this IS a step forward?

Is scrolling up and down a class component really so hard that this clusterfuck is worth it?

>:(

No, extending PureComponent in EVERY DAMN COMPONENT IN THE APP does not improve performance

Lead developer likes premature optimization. Always forces me to remove a if here and there because "bad for the performance".

Now her optimization caused a base component to fail, ppl will have to spend the night debugging.

Best of all, it's my last day ;)

I have a solution in mind and it’s really not that complex but my brain just doesn’t want to connect all the pieces..

When I think about component a and b, then c and a don’t work together. So I come up with a solution for a and a but then b is loose again..

I think I’m getting old🤕

Can somebody explain to me why developers (especially web) have to micromanage every single thing into it's own f*ing component.

Story time: I have an input form with some tabs. I discovered that the UI Library (Devextreme) has a nice little component that handles forms, (including tabs, groups, etc.). So I make a page, configure tabs, inputs and whatnot.

Now, I already knew that my coworkers can't handle html that is bigger than a page. So instead of putting the configs in the frontend, I made nice files where I store those, to keep them nicely clean and seperated.

Me feeling very good, went off to have a nice lunch break.

I come back read the message from my coworker, asking me to make every tab it's own component and form and load them into a separate Tab-Component, instead of using the built in configuration

......

WHAT?

Like seriously. I have a f*ing library that handles that, why the f*ck do I need to reinvent the wheel here!?

Supposedly it's to make it more maintainable, easier to find bugs, flatten the hierarchy.

Here's a little wake up call you morons: Nesting hundreds of components into each other does *not* help you with that.
It just creates a rabbit-hole of confusing containers that you have to navigate and dissect every time you try to find something.

"Can I fix the bug in the detail Page? Sure I'll tell you tomorrow when I find out which fucking component the bug results from".

Components are there to be *reused*. It's using inheritance for reusing code all over again, but worse.

But maybe I'm just old fashioned, and conservative. Maybe I'm just a really bad software engineer, because nowadays everything seems to result in architectures spreading hundreds of folders, thousands of files with nothing but arbitrary cut-offs with no real benefit, that I don't see the value in.

Im making my first opensource project, it's a web component library, but I find the naming part so difficult..

How do you Guys find good project names? And anything i should consider regarding copyrights/e.t.c ?

Suggestions/you naming methods are welcome 🤌

If somebody wants to become famous for the work they do fast. Join DIY projects such as React-Native.
You can become so famous for developing a highly demanded component, since there arent many well maintained this days.
I guess it is the case for many new and fresh projects.

React is awesome and react-native is the beast for cross platform development! You gonna love it guys! Jump in!

RIP my fucking dog laptop. And FUCK Asus. The solution to fixing the fucking laptop is to get a new MB and display. But the motherboard is so God same expensive because you obviously have to solder every fucking component on it so that it's much more of a PITA.

PS yes I'm fucking angry but I hope y'all having a nice day.