A client called me today saying their custom website I built for them is down. It just shows a 403 error now. They said they just wanted to update the prices. I asked what changes they made before it crashed. She said, "I couldn't figure out how to change the prices, so I just installed Wordpress, and now it doesn't work!" They completely deleted the entire website using cPanel and replaced it with a partially installed Wordpress.🤦

"Hey, Root, someone screwed up and now all of our prod servers are running this useless query constantly. I know I already changed your priorities six times in the past three weeks, but: Go fix it! This is higher priority! We already took some guesses at how and supplied the necessary code changes in the ticket, so this shouldn't take you long. Remember, HIGH PRIORITY!"

1. I have no idea how to reproduce it.
2. They have no idea how to reproduce it.
3. The server log doesn't include queries.
4. The application log doesn't include queries.
5. The tooling intercepts and strips out some log entries the legendary devs considered useless. (Tangent: It also now requires a tool to read the logs because log entries are now long json blobs instead of plain text.)
6. The codebase uses different loggers like everywhere, uses a custom logger by default, and often overwrites that custom logger with the default logger some levels in. gg
7. The fixes shown in the ticket are pretty lame. (I've fixed these already, and added one they missed.)
8. I'm sick and tired and burned out and just can't bring myself to care. I'm only doing this so i don't get fired.
9. Why not have the person who screwed this up fix it? Did they quit? I mean, I wouldn't blame them.

Why must everything this company does be so infuriatingly complicated?

Manager: What’s taking so long on that PR?? It’s just some small styling adjustments

Dev: No it’s not you added an entire new calendar module that doesn’t work

Manager: Ok but besides that it’s just a small couple of css edits

Dev: You made styling changes in 50 files, half of which break our mobile responsiveness

Manager: Well then STOP talking to me and FIX IT if you’re so smart.

Dev: You also added a series of filters on a table in this same PR that cause th—

Manager: OK SO I GOT A BIT DISTRACTED THE FACT IS IT ALL NEEDS TO GET DONE SO IT DOESN’T MATTER IF IT’S ALL ON ONE PR SPLITTING THINGS UP INTO SMALL UPDATES IS JUST UNNECESSARY BUREAUCRACY AND IF YOU LIKE THAT THEN GO. WORK. FOR. THE GOVERNMENT!!!

Dev: …

I left a company once. Was there with one colleague and we had this kind of code review habit that we looked at each other changes befor merging them to the deploy branch. On my last day I made a dancing cat dance in front of our app as a tiny joke for him. He instead of reviewing just pulled this time and deployed the new version on the companies dev server without a look. So the fist time the cat showed up was appareantly in the first meeting after I left and everyone went completely crazy because they thought they got hacked.

I think they never found the hidden rock roll in the app.

During a company wide status meeting where all product managers, architects and directors assemble:

Me: *A product architect leading a team of devs*

Directors: So are there any issues or risks you see in delivering the next build in target time for Client 1?

Me: There are too many changes in feature requirements. First they said we can use a shared NFS for storage. Now they are asking to switch over to SFTP pull mode.. blah blah..

Directors: Oh I see.. well we can support both solutions then.

Me: But the deadlin..

Directors: *ignores what I say* Will be a good marketing point for future.

Me: But there are too many regressions in integra..

Directors: *ignores what I say* We should also meet deadlines. That is the most important thing.

Me: Its not as easy as 1+1=2.. The team needs more time to..

Directors: *ignores what I say* Ok lets move on to the next point. What about Client 2?

Me:

I am officially a retard.

I was DOing hard refresh multiple time and making changes on the code.

nothing seems to happen.

after quite a while, I realized I was refreshing the deployed site and not the local one.

kill me.

First I wanna say how grateful I am that devRant exists, because my friends either don’t understand this vocab or don’t care lol.

Last week I worked on a pretty large ticket, opened a PR with 54 file changes. Just to follow standards I set the PR milestone to a future release version, but the truth is I didn’t care which version this work ended up in— I just needed it to go into the develop branch asap.

Since it was a large PR there was some expected discussion that prolonged its merging, but in the meantime I started a second branch that depended on some of the work from this branch. I set the new branch’s upstream to develop, fully expecting my PR to merge into develop, since that’s what I set the PR base to.

I completed all the work I could in the new branch, and got two colleagues to approve the initial PR so it would be merged into develop, I could add the finishing touch and get this work done seamlessly before the week was over. They approved, it got merged, I pulled develop, and… my work wasn’t there. I went to look at my PR and someone had changed the base branch to a release branch. It was my boss, who thought he was helping. (Our bosses don’t actually work on the same team as us, so he didn’t know. it’s weird. We have leads that keep track of our work instead.)

I messaged him and told him I really needed this in develop, knowing our release branch won’t be in develop for probably another week. I was very annoyed but didn’t wanna make him feel too bad so I said I’d just merge the release branch into my new branch. So many conflicts I couldn’t see straight. His response was “yeah and you’ll probably have a bunch of package manager conflicts too because that’s in that release.” He was right— I have so many package manager conflicts that I can’t even see how many compiler conflicts there are. I considered cherry picking my changes, but the whole reason I set develop as my upstream was to avoid having any conflicts since I’m working in the same functions, and this would create more.

So I could spend the next (?) days making educated guesses on possibly a thousand conflict resolutions, or I can revert my release branch merge and quietly step back and wait for the release branch to be merged into develop.

I’m sure cherry picking is the best option here but I’m genuinely too annoyed lol, and fortunately my team does not care to notice if I step back and work on something else to kill time until it’s fixed automatically. But I’m still in dire need of a rant because my entire plan was ruined by a well-meaning person who messed with my PR without asking, so here is that rant and I thank you for your time.

Designers designed a component with a "doubleDigits" property, that changes the text size if there's two digits.

After I implement it, I get "hey it doesn't look good if I type three digits".

Fuck you.

Once upon a time, there were a restaurant called "iEat.tech.com".
It was a small single-location place, where the sufficient number of patrons could be served by the cozy number of employees.
In fact, headcount was so lean that the cook was also the one who washed all the dishes.

But then came the suits and their "VC"(daddy) money and scaled shit up.
Soon, there were so many patrons that the dishes started to pile up the sink, never washed.
"We need someone to wash the dishes!" said the cook
"Fuck you, you wash the dishes!" said the s*its
Naturally, the cook left soon after.

The s*its had a problem now. They could not replace the cook fast enough - all other cooks were either young, inexperienced and mediocre (but did clean the dishes), or refused to waste their time on the sink.
So the suits did what $*its always do - they got a fucking consultant. Who told them to get a fucking dishwashing machine and billed them the GDP of Ireland.

The s*is, of course, did not want to buy a dishwashing machine. "Our fucking process is too fucking disruptive for us to use a fucking store-bought mass-produced metal servant!" (s*its don't know what "machines" are. For them, it's all in terms of "servants", employees and machines alike).

So the s*its hired an engineer to "solve the fucking dish problem, once and for all".
The engineer quickly started measuring and drawing and calculating. The engineer was about to prepare a budget when the s*its came screaming "What the fuck are you doing? There is a fucking pile of dishes in the sink!"
The engineer replied that "I'm designing the machine!", to what the s*its responded "don't bring me fucking problems, bring me solutions!" (or some other s*it blabber)

So the engineer quickly designed an efficient dishwashing assembly line to be done in half the time most people would. And then went back to designing the machine.
But the s*its were having none of it. They kept expanding and expanding and doing what they could so that the engineer never had a moment to work on the machine. They dit it so surreptitiously that no one barely even noticed, but one day they were paying a team of engineers to be fucking human dishwashers.

Now replace "dishes" with "Jira tickets" or "quick fixes" or "tiny changes" and fix other terms accordingly.
Fucking s*its.

## 4 years ago:
- Principal Architect: We are using IO1 storage type. What if we used GP2?
- Perf team: IDK, let's test it!
*we run tests*
- Perf team: results are OK, but we're exhausting Burst IO capacity, effectively hard-limiting number of tests we can run per day
- PArch: ahhh, I see. Then Gp2 is a no-go.

## 3 years ago
*PArch quits. New one is hired*
- PArch2: We are using IO1 storage type. What if we used GP2?
- Perf team: We've already tested that a while ago, results were THIS and THAT
- PArch2: I see. Let's test it again anyway
- Perf team: *wtf???*
*we run the same tests, we get the same results*
- PArch2: I see, so GP2 is a no-go.
- Perf team: *you think....? How did that thought never cross our minds, we wonder...*

## 2 years ago
*new DBA is hired*
- DBA2: We are using IO1 storage type. What if we used GP2?
- Perf team: We've already tested that a while ago, results were THIS and THAT
- PArch2: We've already tested that a while ago, results were THIS and THAT
- DBA2: I see. Let's test it anyways. I've read somewhere that GP2 might be a better bet
- PArch2: you might be right, let's do that
- Perf team: *wtf???*
*we run the same tests, we get the same results*
- DBA2: I see, so GP2 is a no-go.
- Perf team: *you think....? How did that thought never cross our minds, we wonder...*

## 1 year ago
*DBA manager left; new one was hired*
- MGMT_dba2: We are using IO1 storage type. What if we used GP2?
- ........

Should we even bother bringing up the history.....?

My dev colleagues, the ceo, a external designer and me (dev) are sitting in the meeting room
and we discuss the result from the designer. He designed a complete relaunch of a
small CRM for the logistics sector.

The designer is a designer as you know him, big beart, small macbook, chai late
and he designed nothing, he hired a freelancer from romania.

My boss studied software development in the 80s but didn't really developed a software
for about 20 years, but he thinks he knows all and everything.

My boss is constantly complaining about the colors in the design and he would like
a iOS approach. Our system should complete copy the styles from iOS.

The really funny thing happend in just 1 minute. My boss is complaining again about the
colors and told the blue color is way to dark and the designer meant thats not possible the
blue color very bright. My boss sat next to the designer and looked not on the wall where
the picture was thrown from a projector, instead he looks from the side in the macbook screen
of the macbook which was in front of the designer. Then the designer says "Oh my god, the color
changes if I look from the side or from the top of the macbook." The Designer was blown away. My
boss couldn't believe it and did the same movements with his head and said. "Wow, you are right
the color changes".

We all other people couldn't believe that they are so dumb and thought this must be a joke. But
that wasn't a joke. After the meetin my boss told everyone in our company his results regarding the screen.

I wrote every story in a document, and I'm planning to create a book with dumb shit like this.

Never be egoisitc about your code. Its good to feel proud on your code that you did it. but sharing is caring.. don;t be like only I can do this.. ego is not for dev community.. be adaptable for changes whether you learn from junior or senior :)

We work with about 7 developers at this company with 80 somewhat websites in production.

We edit changes directly trough FTP and we use ctrl+z as version control...

(yes since i started working here I've been demanding git, I'm spearheading it and we are getting there slowly)

Worst collaboration experience story?

I was not directly involved, it was a Delphi -> C# conversion of our customer returns application.

The dev manager was out to prove waterfall was the only development methodology that could make convert the monolith app to a lean, multi-tier, enterprise-worthy application.

Starting out with a team of 7 (3 devs, 2 dbas, team mgr, and the dev department mgr), they spent around 3 months designing, meetings, and more meetings. Armed with 50+ page specification Word document (not counting the countless Visio workflow diagrams and Microsoft Project timeline/ghantt charts), the team was ready to start coding.
The database design, workflow, and UI design (using Visio), was well done/thought out, but problems started on day one.
- Team mgr and Dev mgr split up the 3 devs, 1 dev wrote the database access library tier, 1 wrote the service tier, the other dev wrote the UI (I'll add this was the dev's first experience with WPF).
- Per the specification, all the layers wouldn't be integrated until all of them met the standards (unit tested, free from errors from VS's code analyzer, etc)
- By the time the devs where ready to code, the DBAs were already tasked with other projects, so the Returns app was prioritized to "when we get around to it"

Fast forward 6 months later, all the devs were 'done' coding, having very little/no communication with one another, then the integration. The service and database layers assumed different design patterns and different database relationships and the UI layer required functionality neither layers anticipated (ex. multi-users and the service maintaining some sort of state between them).

Those issues took about a month to work out, then the app began beta testing with real end users. App didn't make it 10 minutes before users gave up. Numerous UI logic errors, runtime errors, and overall app stability. Because the UI was so bad, the dev mgr brought in one of the web developers (she was pretty good at UI design). You might guess how useful someone is being dropped in on complex project , months after-the-fact and being told "Fix it!".

Couple of months of UI re-design and many other changes, the app was ready for beta testing.

In the mean time, the company hired a new customer service manager. When he saw the application, he rejected the app because he re-designed the entire returns process to be more efficient. The application UI was written to the exact step-by-step old returns process with little/no deviation.

With a tremendous amount of push-back (TL;DR), the dev mgr promised to change the app, but only after it was deployed into production (using "we can fix it later" excuse).

Still plagued with numerous bugs, the app was finally deployed. In attempts to save face, there was a company-wide party to celebrate the 'death' of the "old Delphi returns app" and the birth of the new. Cake, drinks, certificates of achievements for the devs, etc.

By the end of the project, the devs hated each other. Finger pointing, petty squabbles, out-right "FU!"s across the cube walls, etc. All the team members were re-assigned to other teams to separate them, leaving a single new hire to fix all the issues.

Worked for a friend of mine in the early 2000s. Had to implement a booking system into PHP for some private customer. This was PHP 4.something, the CMS was some alpha release of an open source project that my friend was sure was the future (it wasn't), and the specs were one A4 page of pencil scribbles that he took while talking to the customer.
Deadline was insane, nothing worked. I worked from getting up to laying down to get shit done, not being able to sleep, feeling stressed all the time. One week before roll-out I actually managed to get it running and we showed it to the customer. He was like "nope, that's not what I meant" and demanded lots of changes but accepted only one or two weeks of roll-out delay.
I did finish the job, made some good money, but then quit as soon as it was done.
This experience broke me so much that I worked in a workshop for 2 years to get away from programming as far as I possibly could.

So today, again, I discovered the importance of unitests.
I was solving this performance issue, in which we had a few update actions for multiple entities in mongo, but it took FOREVER to complete, even when I unified it into one bulkWrite command.
Since the unified write did improve performance slightly, and we wanted to move on, we decided to let this bug go.
So there I was committing my changes when I got a rejection from the pre-commit hook since I didn't have enough unitests coverage.
Ok, let's start writing some unitests.
Some unitests also needed to test the bulk write. So there I was comparing expected with actual result, and suddenly I got a huge facepalm.
Apparently some rogue for loop iterated all entities again for each entity that needed update. So instead of getting one update per entity, I got N identical update commands per each of the N entities 🤦‍♂️
Needless to say, fixing this fixed the performance bug entirely.
Thank you unitests and pre-commit hooks!

boss: “I’m conceiving a new policy for engineering. What do you think about these changes?”

me: “Looks good”

boss: “You hardly looked at it”

me: *looks for one second longer than I did last time* “Looks good”

boss: “Do you actually care about this?”

me: “Am I going to have to enforce this policy or interact with any aspect of what happens when it becomes official?”

boss: “No”

me: “Honestlly, man….I really don’t”.

boss: :( “Ok”.

🤷‍♀️

When you are overconfident about your changes and don't test them...

that one legendary guy who cranks out code and builds insane features. PMs (product management) love him because he builds features in several months which 10 devs together couldn't have built in the same time (so they say), features that are loved by customers as well, become their new standard and that have saved our company's asses in the past.
features are really awesome, performant and have very few bugs (compared to the rest of the software シ).
but this guy seems to live for this job. he also works at weekends, at unholy times of day and night and even in his holidays (he doesn't care that this is actually illegal, in terms of employee's rights, and he wouldn't listen to his superiors, no matter what they tell him)
so far, so good - except that he will probably die of some stroke or something very soon due to this lifestyle.
but it must be an absolute pain in the ass to work with him, as long as you're a developer (or his superior).
he lives in his own world and within the software, his features are also his own world. since the different modules interact with each other, sometimes you would be assigned a bug that might have its cause in some interaction of your and his module. talk with him about it? forget it. he wouldn't answer most devs who contacted him for some reason. ever. fix it in his module yourself? might happen that he just reverts your changes to his module without comments. so some bugs would lie on your desk forever because theoretically you know what would need to be done but if you cannot reach out into HIS world, there's no way to fix it. also - his code might be good in terms of performance and low bug numbers. but it seems to be hard to work on that code for everybody else but him.
furthermore, he is said to be really rude. he is no team player, but works on a software that is worked on by a huge team.
PMs think he's a genius, just a great dev, but they don't understand that other devs need to clean up the mess behind or around him.
everyone who's been his superior so far recommends to get him fired, but the company wouldn't fire him because they don't want to lose his talent. he can just do what he wants. he can even refuse to work on certain things because he thinks they are boring and he is not interested in them. devs seem to hate him, but my boss said, they are probably also a bit jealous because of his talent. i think, he's not wrong. :)
i haven't actually met him so far or was actually "forced" to deal with him, but i've never heard so many contrastive things about one person, the reputation of his, let's say vibrant personality really hurries ahead. he must be a real genius, after all i've heard so far, like he lives in the code. i must say i'm a bit curious but also somewhat afraid of meeting him one day.
do you also have such a guy at your company?

Me: “here’s a demo of the backend functionality you requested. We’ve got more work to do to make this production ready. Let me know your thoughts or if we need to make any changes, otherwise I’ll hand this off to the UX team, we’ll be ready to go live next month after other they deliver the front end”

PM: *telling stakeholders* “The new thing is done and ready for go live”

Me: *privately to PM* “who told you that the thing was ready for go live?”

PM: “You did”

Me: “I suggest you go read what I wrote a little more closely”

I love getting a fucking email for every fucking change, instead of getting a list of desired changes.

You know what? Fuck this, I'm tired of being the nice guy, I'm not even getting paid for this, and you expect me to do it expediently on a Sunday. I'm done, you can find someone else to piss off for free.

I'm managed by idiots who don't fully realize the nightmare they're creating.

They're making small operational changes, but hundreds of them with zero evidence to back their claims up.

When I bring up how it actually works, and how operations actually work I'm told I don't use the tools as much as management does and that my feedback is limited to how I use the tool.

So now I'm just gambling that they won't fuck up too bad before I get that sweet sweet sellout money and just letting them fuck everything up they want without any warnings from me.

I'm quickly learning that the phrase of the year is, "Fuck em".

I feel like resigning from a company that i joined 3 weeks back.

I don't like to code in PHP and the manager wants to stick on to that , no new developers joining the company and php is one of the reason. The code is a mess. Every now and then some other team come running for a change like one button to do some shit and then for a fix after 15mins of release.

So many database operations are happening manually. No innovation in the team. Developers are very boring , women being senior developers and team leads brings stability but there is no innovation , excitement or any enthusiasm. All my team members are very happy doing mediocre shit. Manager talks about agile development and they are following that at a level where every half a day some requirement changes.

I m tired of being a developer that fixes the same mediocre shit.

Its too boring.

My coworker became super restless and incompetent during the initial 2020 Covid lockdown. Like playing hours of video games during work hours restless.

For one project, my coworker was working on the backend and I was working frontend. Coworker also wanted to be overlord of the epic branch.

My coworker merges the epic to our test branch and our code is broken. Coworker didn’t pull my FE changes before merging. Dude, I shouldn’t have needed to tell you to pull. You changed the api response that your BE code delivers so of course I had to update my FE code so it could work with this change.

I had to resolve the conflicts because coworker left work early to “rescue/pickup” their girlfriend from work.

You bet I leave this person on read when they try to text me on Signal

Manager’s PR Description: I made changes relating to a ticket which should work as expected. I also made various other changes as I saw fit, test whatever else I changed too.

Dev: …

I have nothing to play recently so I started playing old games.

Today I launched gta vice city on my old pc. Got more than 200 hours in that game during my childhood. Game from 2002 and I laughed when driving a car. It was so natural and fun. Michael Jackson singing Billy Jean and police chasing my ass when I’m trying to find a bribe in the city. That was fun.

For me most of today’s games can’t compete in gameplay mechanics with that game from 20 years ago.
Maybe we have better graphics but gaming fun got worse.

I think it’s cause most of games are made on commercial engines to save money and game studios focus on graphics cause it’s cheaper than paying software developer.

They focus on games to be competitive between players so ai got worse.

Big studio games became generic like movies, they don’t want you to have fun but they want to give you a story around by delivering lots of content in game, achievements, stars but the gameplay itself is bugged and meh.

They don’t focus on things people want to do but they focus on target groups. Most today’s big title games are meh cause they’re made by people who don’t play them.

They don’t play them cause they don’t have time cause of management that changes requirements cause they asked target groups and that would sell. Well if I play a game I’m not interested in story despite some basic stuff to keep the progress forward, if I wanted a big story I would watch a movie or tv show. I play games to explore, feel the world and have fun. I don’t need a linear deep story for that cause I’m in game so give me good gameplay so I can feel the world.

Most of classic game hits didn’t had tons of text and tons of stuff to do but they somehow wanted you to play more. Cause they were competitive between player and computer, the controls felt natural and while progressing you was eaten by the game mechanics more and more not by the story but by amount of stuff you could do as you progress or difficulty increase or enemies behavior change.

Now we’re getting all at once, mostly pointed and with detailed tutorial what you can do. There’s no explanation there’s no discovery what you can and what you can’t do at start. You get all and you decide to throw game away because the moment you launched it you got everything so you spent money just to get stuff you won’t play cause it’s meh and you go back to cs or other looter shooter to kill people cause you’re pissed off that the game was meh.

Well I’m glad I was a kid in 90s and 2000s cause I could enjoy gaming before it was targeted to broader public and become another shallow mass media industry that don’t give a fuck about gameplay cause they want to tell you so many things, they want you to know them cause they’re so important that they forgot that I can read a book and I came to play game to get a different feeling then reading book.

Modern games are like books filled with small stories and nice graphics where you can open it on every page and read a little piece of shitty crap.

Just take this piece and go to toilet so you can wipe your ass with that story and begin other one, look around, puke and go to toilet to take a dump again. I lost my hope to get something fresh or filled with nice gameplay from gaming industry. It’s dead.

Everything about the company is a mess. The only thing that is decent is the people. And by that I mean they aren't shit.
Workflows are fucked.
Clients are fucked. You're pressuring me to get this shit production ready before new year's eve and you still don't know what the text should say and want to make changes to the UI? The fuck?!
Design is a complete shit show. There is a design team. They only make a fucking psd to show clients how an interface would look like. No mobile version (but it's still expected to work!), no markup. Resolution is fucking inconsistent and whenever a change is requested, they are nowhere to be seen so I have to actually do designing on top of having to use this worthless fucking framework I hate it so much.
Codebases are turbo-fucked because of said framework.
Databases are an inconsistent, fucked up mess. No foreign key constraints because every single fucking table is using the MyISAM engine.

And the thing that really makes me incredibly angry is all the "custom systems" look the fucking same at the database level. Like 30 fucking useless tables made for stupid HR workflows that make no fucking sense.

this is mostly how i feel today. we're all aware not much actually changes, but y'know, we survived this year, we get to celebrate a new cycle and hope for new and better things

A long long time ago ( 2007 I think ) I worked for a company that made landing sites, so basically an email campaign would go out, users would be sent to a 1 page website with a form to capture their data, ready to be spammed even more. You know how it was back then.

So I worked with a guy who we had just hired, I didn't do the hiring but his CV checked out, so I gave him one of my tasks. Now most pages were made with js and html, with a PHP backend ( called with Ajax). Now this guy didn't know PHP so I was like all good, ASP works too at the end of the day we don't judge, we do like 2 or 3 of these a day and never look at them again. So he goes of and does is thing.

3 weeks later, the customer calls up to me they still haven't received their landing page. Ok so he probably forgot to email the customer np, I tell him to double check he has emailed the customer. Another week goes by end the customer calls back, same problem. At this point I'm getting worried, because we're days away from the deadline and it was originally my task.

So I go back to the guy and I tell him I want that landing page so I can send it myself, half thinking to myself that we had a freeloader, that guy that comes in to companies for 3 weeks, doesn't work, but still cashes his pay. But no, this was much worse.

So he tells me he has finished yet. I ask him why, what's the blocker ? You had 4 weeks to tell me you were blocked and couldn't progress. And his answer was simply, because I wasn't blocked I have been working on it this whole time. So I tell him to zip his project up and email it to me. We didn't do SVN or git back then, simply wasn't worth it. So he comes back to me and says the email server is telling him attachments can't be bigger then 50mb. At this point I'm thinking he didn't properly sized the art or something, so I give him a flash drive to put it on.

When I then open the flash drive, the archive is 300mb, thinking to myself, the images weren't even that big to begin with.
So I open it up, and I don't even find any images, just a single asp page. About 500mb. When I opened that up and it finally loaded, I saw the most horrendous things ever.

The first 500 lines was just initializing empty vars. Then there was some code that created an empty form with an onChange event that submits the form. After that.. it was just non stop nested if's. No loops, no while, for, foreach, NO elseif's, just nested if's, for every possible combination of the state the form could be in. Abou 5000 of them, in a single file. To make matters worse, all the form ( and page ) layout was hardcoded in the if's. Includes inline css, base64 encoded images, nothing but as dynamic, based on the length of the form he changes the layout, added more background etc. He cut the images up for every possible size of the page and included them in the code.

I showed it to my boss, he fired the guy on the spot. I redid the work from scratch, in under 4 hours. Send it to the client. they had no ammends to make, happy as Larry. Whish I kept the code somewhere.

Morale of the story, allways do a coding test on interviews, even if small things just to sanity check.

i hate how so many places change UI just because

google obviously. but other places too. gitlab just did and just...why? made something take more space by default but maybe less if you have a lot going on. ok sure. did you not have any actual changes so you just made UI changes? wtf is up with this? why do ppl feel the need to change meaningless or confusing crap between versions? if it aint broke mf

Had to change password on computer for administrative reasons (sysadmins and infosec make us change our pass every quarter). Changes didn't sync to everything so now I can't even log into my computer.
Need to go to the office tomorrow so some guy can type in an admin password on my pc and do stuff to it. If that doesn't work I will just be given a new laptop.

Seriously fuck this week

Why on gods green earth, would anybody look at a file with 20k lines, which clearly was made by something called WEBPACK and decide it's the right place to implement their changes for the next few years?!?

Anyone reading these emails we are sending?

I work at a small place. A few users are using an application at our place that I develop and maintain. We all work remotely.

I announce by email to these few users a new version release of said application because of low level changes in the database, send the timeline for the upgrade, I include the new executable, with an easy illustrated 2 minutes *howto* to update painlessly.

Yet, past the date of the upgrade, 100% of the application users emailed me because they were not able to use the software anymore.

----------------

Or I have this issue where we identified a vulnerability in our systems - and I send out an email asking (as soon as possible) for which client version users are using to access the database, so that I patch everything swiftly right. Else everything may crash. Like a clean summary, 2 lines. Easy. A 30 second thing.

A week pass, no answer, I send again.

Then a second week pass, one user answers, saying:

> well I am busy, I will have time to check this out in February.

----------------

Then I am asking myself:
* Why sending email at all in the first place?

* Who wrote these 'best practices textbooks about warning users on schedule/expected downtime?'

*How about I just patch and release first and then expect the emails from the users *after* because 'something is broken', right? Whatever I do, they don't read it.

Oh and before anyone suggest that I should talk to my boss about this behavior from the users, my boss is included in the aforementioned 'users'.

Catch-22 much ? Haha thanks for reading

/rant

Font Awesome. Stop changing the format. 10 changes/page refreshes and I still don't have the fucking icon. what is it? fa fas or fa-solid or fucking what now?... make your fucking mind up!

What is it with companies that get super popular through crowd funding and then just end up annoying?

Your tagging system sucks too. Finding relevant icons could be much better with underlying tags.

Okay, wait, is it a common practice to push changes to master that you KNOW break some other features? I always assumed that that's what branches are for and master should be the "to the best of our knowledge it should be production ready"? But apparently in this company you need to hunt for the right revision, interrogating people why suddenly nothing works on your end and half the time it's "oh, this guy has been working on something and it broke half of the stuff others have been working on and isn't covered in tests yet. Use revision 21xkcd7a"

That feeling when you’ve got a reputation of preciseness etc, and the code you just submitted for review has so many silly little mistakes you just want to do that ostrich thing. Gosh, how can I suddenly suck at my job this bad?

Okay, the changes affect EVERYTHING in our codebase (a major change in core business logic), and there is no way I could’ve tested every possible case by myself without a decent coverage of automated tests - which we obviously don’t have. So yet another argument for it (damn management, won’t you listen?!)… but still, some of the mistakes found during code review make me seem like a complete idiot.

I got a contract with this schools to build a student portal,

I do all the needful and the project whatever guy insists that I use their current shared hosting to host this MERN stack application.

first of all, cPanel is my least favorite place when it comes to deploying, I actually dont do deploying I just hand it over to whoever is the IT guy there.

I discovered there's no provision for nodejs in their current plan, I go through all the stress of contacting the shitty customer support and the process of squeezing out useful information from them.

I'm only doing this because the project whatever has refused to pay me until their site is deployed. throughout the process of creating this project I had setup continous deployment on heroku and netlify and I had to beg this guy to look at the changes and review them.

well, today I asked the former guy that built the current site for the login details to the schools dashboard on the hosting providers site and he says he used his personal details for it, according to him projects from other organizations are there too.

I swear I'm going to loose my shit, freelancing sucks

My project manager just asked me if we need to do a release in order for the changes we have done to be seen in prod.

Yes… what do you think a release means?

debug hell

senior: i'm going to read the code changes of the PR that caused this bug, many files , lots of lines of code to see if i can suss out this issue

me: skimmed the PR, i give up, unga bunga time, time to compare the variables in the debugger between the different implementations, found the difference

due credit, the unga bunga approach worked this time, might nto always work

i was having a really hard time because there was no record of changes in code, the boys would communicate changes in private and I'd spend hours trying to figure out why i couldn't compile. when i asked my boss that they put that info somewhere, he said it was unnecessary and that it always worked that way before i came. ofc it worked, it was 2 guys coding. i couldn't work properly and everything took forever to sort, no one tried to help. i went to hr and they just told me i was right and that i had to be patient. i quit soon after

Intern - adds commit message like "added two files"

Me - Hey Intern, I've added commit lint, please don't disable precommit hooks.. so let's follow standard commit message format

Intern - commits like "feat(app): fix changes"

*later*

Me - Hey Intern, please commit with short meaningful messages like what actual changes were made

Intern - commits like feat(app): whole long story of what he couldn't do and some changes..

Me - 🤦

I love when devs bitch about the size of PRs on a very standard sized one. They're all related changes that can't be broken up. Do you want the app to be broken between PRs? He spent more time bitching about the size of the diff and telling me how he does it better instead of just reviewing the code. A tip or an ask is one thing, this was a wall of text.

Oh and he still didn't approve the PR, which I know he looked at, and didn't leave any blocking comments.

!RANT
Web Devs - I need your opinions.

To make a long story short, when my fiancé and I first moved in together I changed cities. One day at the grocery store we ran in to one of his old buddies, whom I had never met. His buddy works as a counselor at a non profit organization for mental illness. His friend asked me some questions to get to know me and found out I was a web developer. He instantly got exited and told us they needed a new website for their non profit, and asked me what I charged. Being shy, put on the spot, newer to the industry (uncomfortable talking $ due to inexperience) and seeing the guy was paralyzed I felt I HAD to say yes. I also said I would consider donating the site to them, as I knew my other web dev friends had done that for other non profits.

They were easy to work with and the build went smooth. We chose Wordpress so that they could go in and update the site on their own. I was under the assumption that I would create the site for them, but that they would take care of changes on their own, that I wouldn't be "supporting it". I even trained the friend 2-3xs on how to use Wordpress and make changes, but they ALWAYS have changes every month, including slides and content creation. Being a noob at the time, I KNOW it's my fault for not being more clear on the I'll build it but not make changes thing, and I've tried to kind of get them to see that I'm too busy, politely.

We'll, 3+ years later I've now found success in a different career path that takes up ALL of my free time after my 9-5 corporate web dev position, and am no longer interested nor able to do freelance work, including supporting existing sites. Since we don't have a contract in place, and they've never given me a cent, i was thinking of giving them a notice at the end of this month saying as of 2018 I will no longer be able to take care of their website, and that they'll have to find someone else by that time? I feel bad because it's a non profit and they don't have a lot of money. I'm afraid they won't find someone else nor be able to afford it. The situation is a little more sticky since this is my fiancés friend and I don't want them to feel like I'm leaving them high and dry, cuz I know they're very thankful for the site. I just wish they understood that I never promised to do changes for them every month. Even if they offered me money, I just don't have the time. I'm 100% fine if they want to keep the site and my code, although they really could use a redesign anyways cuz my code back then was terrible. What are your thoughts on this? Is 5 months fair? Am I doing the right thing?

f it ain't broke, don't fix it!
I feared my Android phone's touchscreen suffered severe damage from using it in the rain, until I discovered that the 3-button navigation stopped working after an Android 12 security update (both in Nova launcher as well as in official Google Pixel launcher). Wasted time drying the unplugged phone and googling for repair options before finally wasting more time changing system settings back and forth, rebooting, changing system settings, rebooting, etc.
Remember those happy times before mobile phones have been invented, which of course I don't really want back either. I just want developers to stop breaking features that used to work. Regression testing outside the happy path, anyone? I mean, it's not a hacked maker project, it's a commercial phone that I bought and intend to use with the latest official software. Don't want to think about the next breaking changes that Android 13 might bring.

Yesterday, my boss asked me to solve a certain problem the company has with my code.
I tried reproducing it for a very long time but still couldn't manage to do it.
Ultimately (after my boss has been no help at all), I changed some stuff and sent the revised version with this message:
"I couldn't reproduce the problem, so here is a revised version with some changes that **could potentially** solve the problem you're facing."
She immediately decided that the entire company was switching to this version and thanked me. There is no way she tested it that fast. She just saw this might be a fix and didn't bother with the details. I have no idea if the update fixes the problem or even if it won't break anything else. I tried to explain the situation to her but she asked, "Are you saying this works on your computer?" and I was like "Yes, but..." and she didn't care about anything after the Yes, and I just know that when the problem will occur the complaint will be directed at me, and I'm sick of it.

Impossible changes become possible.

open file in eclipse while server is running

i haven't made any code changes or saved anything

ECLIPSE: I GOTTA REBUILD

Definition of code reviews in our company:

"Part of work that requires you to scroll to the bottom of the page and click accept button. Looking the changes is optional."

Why, for the love of all that is good, does anyone still code for absolute placements in css?!

I've spent 90%+ of my time lately making some changes, which is about 20x harder than it needed to be because this app (written in the last 1-3 years) has all of the styling set explicitly. How does anyone justify that?

Why the fuck is gradle so horrible.

I literally have no idea why anyone would ever use this thing (other than being forced too because somehow the rest of the world is using it).

Every plugin has an arbitrary DSL that you have to magically know by piecing together enough snippets. At that point, no one is actually intuiting anything based on the beauty of the DSL, every build is a frankenstein of different snippets that were pasted from different versions of gradle blog posts or SO posts.

And if you do get it o work then the DSL changes, or it isn't compatible with another plugin.

I just want to write a fucking integration test in Kotlin. Can I just add an `integrationTest` task in `tasks` right next to `tasks.test`? No, obviously it goes in the `kotlin jvm() compilations` section, DUH.

The first thing anyone in the universe should have asked is "how is this better than literally hand writing a makefile"? At least then I would be able to see the commands that it ran.

Now I'm googling how to make the new jvm-test-suite plugin work when you're using the Kotlin plugin but every single result on Google for `jvm-test-suite kotlin` just returns the docs for jvm-test-suite (whose snippets obviously didn't work in my project) because those doc pages have "Kotlin" written above each of the gradle snippets.

Please just end this.

Oh and dev rant sucks too. It thinks anything separated by dots in a url.

"Hey, we've made these deprecating changes for the whole company"... "but no migration guide, deal with it"

happy new year everyone! not that anything ever changes, but hope is free 😅

i wish all of you a year with very little reason to rant ✨

So I made an update to my React Native app. I changed UI of a couple of screen, added a few animations here and there, refactored how my graphQL resolvers work in the backend(no breaking changes), changed how data gets loaded into the database etc.

It worked in dev so I figured hey let's deploy it. Today is(was because it's now 3am but more on that later) a national holiday so no one goes to work so no one will use my app so I have an entire day to deploy.

I started at 15:00(because i woke up at 13:00 lol). I tested the update once again in dev and proceeded to deploy it to prod. I merged backend to master, built docker images, did migrations on the db, restarted docker-compose with new images. And now for the app. I run ./gradlew assembleRelease and it starts complaining that react-native-gesture-handler is not installed. Ugh, rm -rf node_modules && yarn install. It worked. But now gradlew crashes and logs don't tell me anything. Google tells me to change a bunch of gradle settings but none of them work. Fast forward 5h, it's around 20:00 and I isolated the issue to, again, react-native-gesture-handler. They updated from 2.2.4 to 2.3.0 which didn't fucking compile. 2 more hours passed (now 22:00) and I got v2.3.1 working which fixed the problem in 2.3.0 but made my app crash on startup. YOUR FUCKING LIBRARY GETS 250K WEEKLY DOWNLOADS AND YOU DONT EVEN BOTHER CHECKING IF IT COMPILES IN PROD ON ANDROID?! WHAT THE FUCK software-mansion?

After I solved that, my app didn't crash. Now it threw an error "Type errors: Network Request Failed" every time I fetch my legacy REST API(older parts use rest and newer use graphql. I'll refactor that in the next update). I'll spare you the debugging hell i went through but another 5h passed. Its 3am. My config had misspelled url to prod but good for dev... I hate myself and even more so react-native-gesture-handler.

Small chaotic startup that never grew up (15 years atm).
Hosts/maintains a number of apps/sites for various customers.

At some point, someone decides that a CMS would be usefull to maintain the content across all products. Forgoing all sense, reason and the very notion of "additional maintenance and dev" it is decided that one should be built in-house.

Fast forward a number of years.

Ops performs routine maintenance on prod-servers. A java-patch accidently knocks out one of the pillars a 3rd party lib the CMS uses for storing images. CMS basically burst in to flames causing a.... significant incident.

Enter yours truly to fix the mess.
Spend a few days replacing the affected 3rd party lib. Run tests on CMS in test and staging environments. Apply java-patch. All seems fine.

When speaking to frontenders and app-devs, a significant hurdle present itself:
All test/staging instances of all websites/apps/etc ALL USE PRODUCTION CMS. Hardcoded. No way around.

There is -no- way to properly test and verify the functionality of any changes made to the home-brewed CMS.
My patch did indeed work in the end.

But did the company learn anything? Did they listen to my reasoning, pleading or even anguished screams for sanity?

No.

*laughing maniacally*

Okidoky you lil fucker where you've been hiding...

*streaming tcpdump via SSH to other box, feeding tshark with input filters*

Finally finding a request with an ominous dissector warning about headers...

Not finding anything with silversearcher / ag in the project...

*getting even more pissed causr I've been looking for lil fucker since 2 days*

*generating possible splits of the header name, piping to silversearcher*

*I/O looks like clusterfuck*

Common, it are just dozen gigabytes of text, don't choke just because you have to suck on all the sucking projects this company owns... Don't drown now, lil bukkake princess.

*half an hour later*

Oh... Interesting. Bukkake princess survived and even spilled the tea.

Someone was trying to be overly "eager" to avoid magic numbers...

They concatenated a header name out of several const vars which stem from a static class with like... 300? 400? vars of which I can make no fucking sense at all.

Class literally looks like the most braindamaged thing one could imagine.

And yes... Coming back to the network error I'm debugging since 2 days as it is occuring at erratic intervals and noone knew of course why...

One of the devs changed the const value of one of the variables to have UTF 8 characters. For "cleaner meaning".

Sometimes I just want to electrocute people ...

The reason this didn't pop up all the time was because the test system triggered one call with the header - whenever said dev pushed changes...

And yeah. Test failures can be ignored.
Why bother? Just continue meddling in shit.

I'm glad for the dev that I'm in home office... :@

TLDR: Dev changed const value without thinking, ignoring test failures and I had the fun of debunking for 2 days a mysterious HAProxy failure due to HTTP header validation...

We have a new team member in our team. So I was giving her one to one KT. After KT

She: so are there new changes coming soon?

Me: Yes there will. Now you here I could really use a hand.

She: that's what he said

I ran out of milk halfway a chocolate milk.
With no options left, I skeptically decided to add some water.
I had half a cup of milk, added 1/4 of water. Y'know, enough to look filled, not enough to ruin it in case it goes wrong.
Microwave it.
No, freaking, difference. Loved it.
I added some more water to see how much it changes, and it's just slightly less thick and 70% milk flavour. Sure it's a change but now I know the limit.
Recommended.

I went down a rabbit hole of code changes to try and delete a stupid for loop with a break in it.

It was super stupid and I gave up and submitted to the fact that some battles are not worth the time and stress.

OK... But seriously, It was returning multiple entities from the database, but we only always want the first one. My logic is that we should just go in there and fix the LINQ so we are explicitly getting one entity out.

But fuck that logic. No I'll have to change fucking everything that's tied to that method and expects a list from it. Every fucking thing. That includes error handling, parsing, for loops..... Nevermind...

You can have your foreach and your break. I'm taking mine, now.

I did not think that making a serverless Discord bot would be such a learning experience. The code itself was easy. The hard part was the infrastructure, because I decided to automate it all with Terraform and deploy it on AWS.

Before this project, I had no idea how API Gateways worked. Now I still have very little idea how they work but I managed to build one anyway. Eventually. And then I had to figure out how to automate the deployment of a lambda layer and function that would both still be managed in the Terraform state, with any code changes triggering a rebuild and update for the resource.

And then I had to untangle a dependency mess because API Gateways have some weird issues where two resources that have no explicit dependencies on each other will throw an error if they don't deploy in the right order.

And then I went the wrong way with Github actions trying to conditionally chain multiple workflows together before I realized I could just put multiple jobs with conditions in a single workflow.

And now after all that work over the course of 2 days, I have a bot that does this:

I gave backend dev my frontend code and he had no idea about SCSS.

So he copied the compiled AND minified CSS, prettified/formatted it and put his own changes by searching the class names.

And he had made lots of design changes arbitrarily so when new changes were to be made I had to cope with it.

As a hack I kept his css as it is and compiled another file with new changes. And now there's two css files all huge, like 800kb multiply by two huge.

It covers about 33+ custom pages with all the bells and whistles.

#let me do the frontend
#I wont bother you either

ComputerToucher: *opens Jira ticket* Dev team needs tokens for the APM for a new app with multiple tenants. Ezpz. Hey, developer. Do you want one golden token for all of your app tenants or would you like us to generate one token for each?

Developer: Let’s have a meeting to discuss it.

CT: It’s…an exceedingly simple question. One token or 4? Which does your app support?

Dev: Yeah I think we should discuss with this with the platform team, can you set up the call?

CT: (Internally) I am the platform team? Do you not know how your applica-never mind I’ll just ask the PM directly.

CT (in chat): I’ll ask PM to schedule the call.

*Goes back to Jira ticket, changes priority to 4, removes ticket from sprint entirely, picks something else to work on*

So i wanna get my hands dirty in tech hardware. i have learned the abc of computers only 7 years ago, and i still consider myself a very noob in computers since my first computer was a laptop and even today ita still the laptop.

i got 0 experience with assembling, 0 experience setting up my network cards, cpu disks , ram in slots and what not.

but this changes in next few weeks. i am fed up with ugly jamf limitations on my office laptop, fed up with the 20-mins-to-run emulators on my personal laptop , and overall fedup with this capitalist mindset that goes into making these "4 years until shit is weak" laptops.

the only exception i find in laptops are the mac laptops which are delightful to be used , especially there hardware. however they too seem to be made with $$$ in mind and i am not going to spend $4k on a piece of beautiful metal which can't run emulators properly.

so my dear seasoned professionals, can you guide me with how to build a PC? the only requirement is smooth experience with android studio emulators and a possibility to upgrade processor, ram , ssd, etc whenever the tech grows (which i guess is a possibility with PCs, right?)

When you bust your ass developing a site for a client, bend over backwards with changes - pushing the rest of your extremely large queue further and further behind, just to come in to a cancellation request from someone else at said company. 😡 We had really good rapport and the site looked amazing, and all they give me is "we're going in another direction". 😡 Why do people so this when the site is already finished?!? So rude! Before you comment telling me to charge upfront next time or whatever I work for a huge company so none of that is in my control.

I don't know what the fuck is happening rn I created repo on gitlab and tried to make changes from terminal it refused. Tried every fucking combination as I thought I must be doing something wrong .
Got fed up made a new account , made a new repo but gitlab doesn't allow me to upload files from there fucking website too.
Now I am getting error 500 from terminal because I can't clone my repo as it says this repo doesn't exist.
Now I can only imagine that there might be some problem with gitlab it's 4 in the morning, I should probably sleep.

Had to add some functionality to another guys GUI code.
He gave me a "template" file (copy of another module), pointed at several places and said: "Make your changes here, here, and here. Do not ask why, do not even think about it. Just do it."

Dear Windows, we have to talk. I love you, you know that, and I know that your market share has been shrinking in recent years and you're shit scared of becoming irrelevant but for the love of god:

- STOP asking me every god damn few weeks if I want to change my browser settings - NO I FUCKING DONT WANT TO USE BING, FUCK OFF

- STOP trying to be like an app and add pointless new "features" that nobody cares about and just do your fucking job, which is to be a PLATFORM which is stable, never changes and that gets out of my fucking way

- STOP reinstalling apps I uninstall, Im NOT FUCKING INTERESTED IN PAINT 3D, FUCK OFF

FUCK, ME,

Recruiter: We are looking for a full-stack expert. You have taken multiple apps from conception to deployment, and have experience and opinions on the best technologies to use and why. You should be comfortable implementing new features from scratch, making changes to existing features and writing complex migrations on production data.

Dev: lol

I wanted to make some changes to one project on GitHub. Forked, changed things ( in new branch), make PR, waited.

My PR got positive feedback, but was closed without merging.

Upon me asking why, I was banned from all their repos.

Inclusivity anyone?

This is more of an advice seeking rant. I've recently been promoted to Team Leader of my team but mostly because of circumstances. The previous team leader left for a start-up and I've been somehow the acting Scrum Master of the team for the past months (although our company sucks at Scrum generally speaking) and also having the most time in the company. However I'm still the youngest I'm my team so managing the actual team feels a bit weird and also I do not consider myself experienced enough to be a Technical lead but we don't have a different position for that.

Below actions happen in the course of 2-3 months.

With all the things above considered I find myself in a dire situation, a couple of months ago there were several Blocker bugs opened from the Clients side / production env related to one feature, however after spending about a month or so on trying to investigate the issues we've come to the conclusion that it needs to be refactorised as it's way too bad and it can't be solved (as a side note this issue has also been raised by a former dev who left the company). Although it was not part of the initial upcoming version release it was "forcefully" introduced in the plan and we took out of the scope other things but was still flagged as a potential risk. But wait..there's more, this feature was part of a Java microservice (the whole microservice basically) and our team is mostly made of JS, just one guy who actually works as a Java dev (I've only done one Java course during uni but never felt attracted to it). I've not been involved in the initial planning of this EPIC, my former TL was an the Java guy. Now during this the company decides that me and my TL were needed for a side project, so both of us got "pulled out" of the team and move there but we've also had to "manage" the team at the same time. In the end it's decided that since my TL will leave and I will take leadership of the team, I get "released" from the side project to manage the team. I'm left with about 3 weeks to slam dunk the feature.. but, I'm not a great leader for my team nor do I have the knowledge to help me teammate into fixing this Java MS, I do go about the normal schedule about asking him in the daily what is he working on and if he needs any help, but I don't really get into much details as I'm neither too much in sync with the feature nor with the technical part of Java. And here we are now in the last week, I've had several calls with PSO from the clients trying to push me into giving them a deadline on when will it be fixed that it's very important for the client to get this working in the next release and so on, however I do not hold an answer to that. I've been trying to explain to them that this was flagged as a risk and I can't guarantee them anything but that didn't seem to make them any happier. On the other side I feel like this team member has been slacking it a lot, his work this week would barely sum up a couple of hours from my point of view as I've asked him to push the branch he's been working on and checked his code changes. I'm a bit anxious to confront him however as I feel I haven't been on top of his situation either, not saying I was uninvolved but I definetly could have been a better manager for him and go into more details about his daily work and so on.

All in all there has been mistakes on all levels(maybe not on PSO as they can't really be held accountable for R&D inability to deliver stuff, but they should be a little more understandable at the very least) and it got us into a shitty situation which stresses me out and makes me feel like I've started my new position with a wrong step.

I'm just wondering if anyone has been in similar situations and has any tips or words of wisdom to share. Or how do you guys feel about the whole situation, am I just over stressing it? Did I get a good analysis, was there anything I could have done better? I'm open for any kind of feedback.

Was working on a high priority security feature. We had an unreasonable timeline to get all of the work done. If we didn’t get the changes onto production before our deadline we faced the possibility of our entire suit being taken offline. Other parts of the company had already been shut down until the remediations could be made -so we knew the company execs weren’t bluffing.

I was the sole developer on the project. I designed it, implemented it, and organized the efforts to get it through the rest of the dev cycle. After about 3 month of work it was all up and bug free (after a few bugs had been found and squashed). I was exhausted, and ended up taking about a week and a half off to recharge.

The project consisted of restructuring our customized frontend control binding (asp.net -custom content controls), integrations with several services to replace portions of our data consumption and storage logic, and an enormous lift and shift that touched over 6k files.

When you touch this much code in such a short period of time it’s difficult to code review, to not introduce bugs, and _to not stop thinking about what potential problems your changes may be causing in the background_.

I have a ton of nostalgia for ROBLOX, but everything seems to get broken over time. As ROBLOX updates, something changes about the way the code works. Enough to the point where things that usually work stop working. I mean, look at literally all of the old gear; Many of them are completely broken. I've seen many old, fun games completely die because the devs stopped fixing the problems the ROBLOX devs were causing by constantly revising the engine. I'm afraid to make something too big and complicated because then it'll eventually stop working, and it will be a nightmare to figure out what I need to revise.

Unclogging a workflow that stretches > dozen porjects, from building to analysis of build (static / lint check etc.)… Deployment.

It's frustrating.

Touching one thing and everything falls apart.

Thus small changes, fixing the rest of workflow, testing ...

Repeat .

Going now since 1 1/2 weeks. Possibly another or two weeks more.

It is soooooooo boring tedious annoyingly frustrating slowmotion shit

-.-

get a high priority bug , look at code changes, a variable name getting refactored apparently created a class cast exception

something about this hypothesis doesn't seem right

i hate my job, welcome back from vacation

How to Fix Sidebar Below Content Error in WordPress?

Fixing The Sidebar Below The Content Error in WordPress
Undo recent changes to your WordPress theme.
Rule out WordPress plugins.
Find the HTML breaking the layout.
Find the CSS moving the sidebar below the content.
Clear WordPress cache.

I don't know how any company can keep on top of crazy npm package changes. I work in a REALLY SMALL team. We are still using bunch of deprecated packages and we keep building on top of those packages. Updating packages is always a nightmare. It's impossible to Google solution when no one is using the particular combination of deprecated packages. Fuck me

It's a shame that people don't want to use F# but prise C# for how cool it became and continue becoming. At the same time, little do they know that many of the features were simply drawn from F#.

It's just rediculous how far this OO and C-Style syntax crap has progressed. They keep copying things from functional langugages, making the initial language to be a monstrocity like C++ is now, insted of just using languages like C#. I mean, it was right there before C#: async/task, immutablility, records, indexes, lambdas, non-null by default, who the hell knows what else.
Besides, many people (in my company at least) are just blindly overengineering with patterns and shit, where a simple function would be just enogh.

Watch some some NDC talks about F#, in particular those of Scott Wlaschin. It's just better in so many ways: less noice (I'm looking at you, brackets, commas and semicolons), the whole LOT of type inference and less duplication (just look at the C# signatures of linq methods - it's difficult to read them), immutability by default, non-nullable by default, ADTs and pattern matching, some neat features like type providers (how many times have used "paste special" or an online tool to create C# classes from a JSON/XML file, and how many times have your regenrated it because of schema changes?) and units of measure.

Of course, in some cases it's not optimal, in some cases mutable datastructures of C# are better for performance. But dude, how many performance critical systems have you wrote in C#? I mean, if it comes to performance you should use Rust or C++ or C after all.

*sighs*

first job after uni some months in... had just about enough today at work, it should not take me a whole day to almost figure out 1 bug cause nothing is documented or the code for 1 thing is mixed with 17 other things, we have no docs, no comments, we have no requirements... boss just says what he wants and everyone goes to write code, no planning , no design, next day boss changes his mind and so on ...what a day.... getting depressed

The tech lead is doing most of the changes without even notifiying the rest of us.. How normal is it?

Its most enjoyable when you are working on a codebase that was cleary planned and thought out beforehand. Bugs are easy to fix, features are easy to make because you already have a blueprint of how its supposed to look, modifying features is easy because you already know where to look to make the changes. You can work with plain jquery or fucking visual basic and youll still have a better time then with any modern framework if you have that.

Clock: Friday, 15:45 PM - just go home now, idiot!
My stupid ass: Makes substantial changes to the code I have been working on and breaks it.

Since the 3rd day, I have been telling y'all but none of you listened to me.

I kept repeating that I am the dumbest person I know. Why didn't you believe me when I said it?

Remember, Booking feedback? They sent me another official rejection with additional feedback. Mind blown.

That feedback really helped me understand what was going wrong. And now today in an interview, I was asked a question and the interviewer said, "I am looking for a specific details like xyz for why you should be a Sr PM".

That's when it clicked me, that I have done stuff and I know things. It's just that I didn't understand the question and wasn't able to articulate and communicate well.

My dumbass just needs constant feedback to learn. How much I love feedback more than ever.

The feedback cycle is interesting too. When I was new, I hated it. Then started to realise the value of it.

Then it did felt bad in the very instance whenever I got one, but quickly I used to incorporate the changes.

And now, I am crave and desperately seek feedback. It only helps me improve.

Funnily, everyone gave inputs when I didn't want it. And now when I am hunting for it, no one is giving inputs. This is how life is.

Nonetheless, I am pretty impressed with Booking. Good people, nice vibes, and kickass culture for sure.

I want to share one of my recent interview experience..

so first round was telephonic and technical guy seems cool as he did not emphasis on syntax, function name etc.. but just took the info of my tech on which I am working on and discuss some approaches to find a solution towards the problem.. ( I guess thats pretty well for experienced dev)

Second round was assignment and its a hell of assignment :( atleast for me.. Like I work in CI 3 and I did assignment on CI 4. almost everything is changes in CI 4 ( I mean its structure writing the way of routes,models and controllers).. But I took the challenge personally and finished 95% of assignment ..

Overall this interview experience was pleasant one.. :)

Sometimes, using git feels like performing a particle experiment in physics.

When I have some added lines staged for a commit, then remove those lines and stage it too, the changes annihilate into no changes at all.

Lines add and lines remove is like particle and antiparticle.
The energy that is released upon annihilation is equivalent to the joy of having a clean commit with few changes.

My fucking lazy-ass coworkers haven’t made meaningful progress on anything for months. I’m brought in as the tech lead and these stupid fucks didn’t work on any meaningful shit for literal months. Their manager was asleep at the wheel and their old tech leads apparently need months to make a couple of minor database changes.

So I’m brought in to fix it, and… surprise! They’re still lazy pedantic assholes. And they’re shocked - shocked - that people expect them to start completing a project or two per quarter. Like these dense motherfuckers thought that they could be the most annoying pedants this world has ever seen, and also do no work.

I could have done their whole 5 month project myself in a month. No joke. It’s incredibly simple. But somehow the overhead of coordinating people who A. don’t work very hard and B. assume that every ticket needs special attention and 6 hours of ponderous thought has eaten into the time we have.

I don’t respect them in the slightest. They’re such shitty developers. Whoever signed off on their hire was fucking high.

Somebody: (whinwy) we need something to log into nonprivileged technical accounts without our rootssh proxy. We want this pammodule pam_X.so
me: this stuff is old (-2013) and i can't find any source for it. How about using SSSD with libsss_sudo? Its an modern solution which would allow this with an advantage of using the existing infrastructure.
somebody: NO I WANT THIS MODULE.
me: ok i have it packaged under this name. Could you please test it by manipulating the pam config?
Somebody: WHAT WHY DO I NEED TO MANIPULATE THE PAMCONFIG?
me: because another package on our servers already manipulates the config and i don't want to create trouble by manipulate it.
Somebody: why are we discussing this. I said clearly what we need and we need it NOW.

we have an package that changes the pam config to our needs, we are starting to roll out the config via ansible, but we still use configuration packages on many servers
For authentication as root we use cyberark for logging the ssh sessions.
The older solution allowed additionally the login into non-rootaccounts, but it is shut down in the next few weeks after over half an year of both systems active and over half an year with the information that the login into non-privileged accounts will be no more.

Does anyone have a better way to implement throttle on value changes in c# ?

I'm using this right now and I find it a bit "too much lines"

@highlight
searchThrottle.Throttle(TimeSpan.FromMilliseconds(200))
.Select(e => ((string)e.Value)?.Trim())
.DistinctUntilChanged()
.Subscribe((x) =>
{
quisckSearch = x;
InvokeAsync(async () => await LoadFirstPage());
});

The joys of finding out two days after going live with your new site, that somehow you used a backup table of the old site, from 6 fucking months before, to serve as a base for migration.

So you have to write hundreds of lines of queries by hand, to ensure that the old data still fits into your migrated data, and also keep the changes made in these two days.

you know, i sometimes feel that whenever i think of a great idea, i start with such a bang, but end up losing motivation and therby delivering a very small scale personal project.

i have made some good apps in the past, some of which have so loyal users that they even mail me to this date. , and i then release an update for them.

those apps were made on an idea that would solve my problem, but i stopped using them. but somehow a few people had similar problem. somehow my app solved for them and somehow they are using it.

i wish i could not burst all my crackers during the development phase only. comparing this to my office work, the office work is still better.
In there, am responsible for delivering a specific output in specific timeframe (say a jira sprint) and if i complete something early, then no one wants me to pick future stuff.

instead i got this limited, exploration period where i can experiment with the codebase, add changes to my liking, get them reviewed / merged if they look good and that's it . once that exploration period is over, i have to pick the task of that weekend/sprint.
I am timed to deliver some stuff in some timeframe. in personal project, i want to put in everything "until its over" .the dev would be made in 3-7 days, with sometimes more than 24 hours per day being on the project, and the poosh! i will deploy it to playstore, market it on social media , and forget about it.

don't know what can be improved in here to make myself more happy with my personal projects? getting feedback/recognition keeps me on my toes

anyone has any tips for this kind of mind-blockage?

The project needs to make bigger changes to a module. A guy starts doing the changes. It turns out that the task is bigger than we though originally. Team lead has a brilliant idea: you need help. So he'll assign couple of more guys to do the same change.

What's the catch? The catch is that we are now all changing the same files. The code is a mess and tweaks and hacks are needed all over the place. So basically one guy changes the files and others just watch YouTube and wait for him to commit. The it's your turn to change the files and the first guy watches PornHub.

You could all just try to edit the same files at the same time, but we all know how GIT feels about that. You change random lines, he changes random lines, someone else changes random lines, all merges go to shit, nothing works and we spend 2x more time on just trying to get it compiling again.

Who inside BitTitan is doing live testing on production? Would you kindly revert the changes and do testing on a test environment? I've seen the 4 changes so far and they clearly not working.
Please we need to finish this migration

Question for devs:
How are y’all handling copy changes in your app? What’s ur process? Do you put up a PR for every small copy change or do you use a special tool or something?

I was supposed to just review the PR. But I couldn't stop myself from making minor changes.

It has been 4 hours now. I'm thinking if I should raise a PR for the PR.

My current assignment is to refactor a React app and get it up to speed. All dependencies have been updated and necessary changes made. Currently I’m working to get class components moved to functional components when React hooks can replace the lifecycle methods used. Additionally I am updating it with ESLint to follow the Google JavaScript Style Guide because the code quality is questionable. What are some of the things you’d do to refactor a React application?

I try to delete a partition from my sundisk Pendrive using GParted but when I do this I got the error that is shown in the image.

And If I try to use "fdisk" which run `sudo fdisk /dev/sda` following command it gives me ```welcome to fdisk (util-linux 2.34).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.

fdisk: cannot open /dev/sda: Read-only file system```

following error does that mean my pendrive permanently broke can anybody help me!