API Guy.

He has a serious regex problem.
Regexes are never easy to read, but the ones he uses just take the cake. They're either blatantly wrong, or totally over-engineered garbage that somehow still lacks basic functionality. I think "garbage" here is a little too nice, since you can tell what garbage actually is/was without studying it for five minutes.

In lieu of an actual rant (mostly because I'm overworked), I'll just leave a few samples here. I recommend readying some bleach before you continue reading.

Not a valid url name regex:
VALID_URL_NAME_REGEX = /\A[\w\-]+\Z/

Semi-decent email regex: (by far the best of the four)
VALID_EMAIL_REGEX = /\A[\w+\-.]+@[a-z\d\-.]+\.[a-z]+\z/i

Over-engineered mess that only works for (most) US numbers:
VALID_PHONE_REGEX = /1?\s*\W?\s*([2-9][0-8][0-9])\s*\W?\s*([2-9][0-9]{2})\s*\W?\s*([0-9]{4})(\se?x?t?(\d*))?/

and for the grand finale:

ZIP_CODE_REGEX = /(^\d{5}(-\d{4})?$)|(^[ABCEGHJKLMNPRSTVXY]{1}\d{1}[A-Z]{1} *\d{1}[A-Z]{1}\d{1}$)|GIR[ ]?0AA|((AB|AL|B|BA|BB|BD|BH|BL|BN|BR|BS|BT|CA|CB|CF|CH|CM|CO|CR|CT|CV|CW|DA|DD|DE|DG|DH|DL|DN|DT|DY|E|EC|EH|EN|EX|FK|FY|G|GL|GY|GU|HA|HD|HG|HP|HR|HS|HU|HX|IG|IM|IP|IV|JE|KA|KT|KW|KY|L|LA|LD|LE|LL|LN|LS|LU|M|ME|MK|ML|N|NE|NG|NN|NP|NR|NW|OL|OX|PA|PE|PH|PL|PO|PR|RG|RH|RM|S|SA|SE|SG|SK|SL|SM|SN|SO|SP|SR|SS|ST|SW|SY|TA|TD|TF|TN|TQ|TR|TS|TW|UB|W|WA|WC|WD|WF|WN|WR|WS|WV|YO|ZE)(\d[\dA-Z]?[ ]?\d[ABD-HJLN-UW-Z]{2}))|BFPO[ ]?\d{1,4}/

^ which, by the way, doesn't match e.g. Australian zip codes. That cost us quite a few sales. And yes, that is 512 characters long.

Me: So i've cloned the iOS project, i've run carthage, but it won't build.. Have I done something wrong?

Devs: Oh read this doc on github, we do loads of custom stuff. The depenedncy manager can't do it all by itself. You need to run `./scripts/boostrap.sh`

Me (another day): I've switched branches and i'm getting all these errors. Any ideas?

Devs: Ah this happens when someone modifies xyz. Read this pinned slack message. Run `./scripts/bootstrap.sh` again.

Me (another day): I've switched branches again, getting different errors, re-running boostrap didn't fix it.

Devs: Ah yeah, this happens when someone modifies abc. You need to run `./scripts/nuke.sh` and then boostrap when this happens.

Me (another day): Guys When I try to run the prod app its not building any ideas?

Devs: Ah yes have a look at this confluence link. You need to run `./scripts/setup_debug_release.sh`, then nuke, then boostrap and you'll be good.

Me: .... ok

Devs: Oh btw very important! do not commit any changes from `./scripts/setup_debug_release.sh`. It will break everything!

Me: ... no i'm sorry we have a much bigger problem than that. We need to talk ... like right now

There once was a bright young engineer who was hired by a company to design their new light ship.
Like 50 seconds after getting inside the company, the engineer was approached by a douchebag in a business suite.
"Hey, can you make us a mock up of the ship's design in the next hour or so? Nothing fancy, it must be very simple! To not overcomplicate it! Just a simple mock up so we can all see what are we talking about in this project! Please do not overthink this!"
The engineer, young and naive, just folded some piece of paper and gave the douchebag a paper boat.
"Fantastic! That's all we need for the presentation for the investors!"
A couple hours later the suite was back screaming.
"YOUR FUCKING FARSE! YOUR SHITTY SHIP EMBARRASED US ALL! THE VERY MOMENT OUR CEO TRIED TO STEP ON IT IT SANK! YOU ARE FIRED AND WE WILL SUE YOU FOR INCOMPETENCE! I ASKED YOU SOMETHING SIMPLE AND YOU CAME UP WITH THIS OVER ENGINEERED PIECE OF CRAP, YOU SON OF A.. [many, maaany expletives suppressed for brevity sake]"

This is how I feel everytime someone asks for "a tiny change" or some "very simple solution".
If it was so simple that it could be done in such short notice, than why the fuck do it at all, instead of buying it? I heard people sell all sorts of things in the internet nowadays. Software fucking included.

Neural network based 3D indoor location tracking on a moving ship in the middle of the ocean with ar visualization for the crew to find guests.

You are on a cruise, you have an app on your phone to order stuff (drinks, meals etc)
Once you order an indoor location system calculates your position (based signal strength on training) on the ship(x, y, z)(deck, area etc) and sends it to the crew.

The crew wears an ar glass and once your order is ready they get a realtime ar navigation to you.

It was seriously over-engineered 😀
We used the phone’s bluetooth and beacons on the ship to calculate the position based on signal strength.

Ok you fucks that don't believe in documentation - me included.

Document your shit, because one day, one day some dumb fuck is going to have to recreate your over engineered bullshit of a system and scale it up.

What would fucking be useful right now is ANY god forsaken insight into what in the flying fuck your code is doing, or not doing, or why it makes queries to a database with no fucking records in it 🤦‍♂️ and then attempts to use that data... in case it did exist.

There's nothing like unpicking a mess of bullshit, and documenting it, and then have to remake it on a new platform.

Documention saves lives kids, maybe your own life one day😬

I'm editing the sidebar on one of our websites, and shuffling some entries. It involves moving some entries in/out of a dropdown and contextual sidebars, in/out of submenus, etc. It sounds a little tedious but overall pretty trivial, right?

This is day three.
I learned React+Redux from scratch (and rebuilt the latter for fun) in twice that long.

In my defense, I've been working on other tasks (see: Alerts), but mostly because I'd rather gouge my freaking eyes out than continue on this one.

Everything that could be wrong about this is. Everything that could be over-engineered is. Everything that could be written worse... can't, actually; it's awful.

Major grievances:
1) The sidebars (yes, there are several) are spread across a ridiculous number of folders. I stopped counting at 20.
2) Instead of icon fonts, this uses multiple images for entry states.
3) The image filenames don't match the menu entry names. at all. ("sb_gifts.png" -> orders); active filenames are e.g. "sb_giftsactive.png"
4) The actions don't match the menu entry names.
5) Menu state is handled within the root application controller, and doesn't use bools, but strings. (and these state flags never seem to get reset anywhere...)
6) These strings are used to construct the image filenames within the sidebar views/partials.
7) Sometimes access restrictions (employee, manager, etc.) are around the individual menu entries, sometimes they're around a partial include, meaning it's extremely difficult to determine which menu entries/sections/subsections are permission-locked without digging through everything.
8) Within different conditionals there are duplicate blocks markup, with duplicate includes, that end up render different partials/markup due to different state.
9) There are parent tags outside of includes, such as `<ul>#{render 'horrific-eye-stabbing'}</ul>`
10) The markup differs per location: sometimes it's a huge blob of non-semantic filthiness, sometimes it's a simple div+span. Example filth: section->p->a->(img,span) ... per menu entry.
11) In some places, the markup is broken, e.g. `<li><u>...</li></u>`
12) In other places, markup is used for layout adjustments, such as an single &nbsp; nested within several divs adorned with lots of styles/classes.
13) Per-device layouts are handled, not within separate views, but by conditionally enabling/disabling swaths of markup, e.g. (if is_cordova_session?).
14) `is_cordova_session` in particular is stored within a cookie that does not expire, and within your user session. disabling it is annoying and very non-obvious. It can get set whether or not you're using cordova.
15) There are virtually no stylesheets; almost everything is inline (but of course not actually everything), which makes for fun layout debugging.
16) Some of the markup (with inline styling, no less) is generated within a goddamn controller.
17) The markup does use css classes, but it's predominately not for actual styling: they're used to pick out elements within unit tests. An example class name: "hide-for-medium-down"; and no, I can't figure out what it means, even when looking at the tests that use it. There are no styles attached to that particular class.
18) The tests have not been updated for three years, and that last update was an rspec version bump.
19) Mixed tabs and spaces, with mixed indentation level (given spaces, it's sometimes 2, 4, 4, 5, or 6, and sometimes one of those levels consistently, plus an extra space thereafter.)
20) Intentional assignment within conditionals (`if var=possibly_nil_return_value()`)
21) hardcoded (and occasionally incorrect) values/urls.

... and last but not least:
22) Adding a new "menu sections unit" (I still haven't determined what the crap that means) requires changing two constants and writing a goddamn database migration.

I'm not even including minor annoyances like non-enclosed ternaries, poor naming conventions, commented out code, highly inefficient code, a 512-character regex (at least it's even, right?), etc.

just.

what the _fuck_

Who knew a sidebar could be so utterly convoluted?

Does anyone else feel Facebook is hell bent on attacking open source in order to gain a monopoly on it?

They are slowing replacing every industry standard tool with over engineered bullshit and it just gets lapped up like it's the best thing ever...EVERY SINGLE FUCKING TIME

Fuck you Facebook, i will never support you in your crusade against one of the things i hold closest to my heart.

[long]
When searching for internship via school I found this small startup with this cute project of building a teaching tool for programming. There were back then 2 programmers: the founder and the co-founder.

Then like 1 week before the internship started, the co-founder had a burnout and had to get off the project, while the company was so low on budget the founder, aka my new b0ss, had to work separate jobs to keep the company alive. (quite metal tbh)

It's funny because I'm a junior developer, 100%. I've been coding as a hobby for around 8 years now but I've never worked in a big company before. (No exception to this workplace either)

First project I get: rewrite the compiler. The Python compiler.
"But wait, why not just embed a real compiler from the first case?"
-nanananana it's never simple, as you probably know from your own projects.

The new compiler, as compared to existing embedded compiler solutions out there, needed these prime features:
- Walk through the code (debugger style), but programmatically.
- Show custom exceptions (ex: "A colon is needed at the end of an if-statement" instead of "Syntax error line 3")
- Have a "Did-you-mean this variable?" error for usage of unassigned variables.
- Be able to be embedded in Unity's WebGL build target

All for the use case of being a friendly compiler.
The last dash in the list is actually the biggest bottleneck which excluded all existing open-source projects (i could find). Compliant with WebAssembly I can't use threads among other things, IL2CPP has lots of restrictions, Unity has some as well...

Oh and it should of course be built using test-driven development.

"Good luck!" - said the founder, first day of work as she then traveled to USA for **3 weeks**, leaving me solo with the to-be-made codebase and humongous list of requirements.

---

I just finished the 6th week of internship, boss has been at "HQ" for 3 weeks now, and I just hit the biggest milestone yet for this project.

Yes I've been succeeding! This project has gone so well, and I'm surprising myself how much code I've been pumping out during these weeks.

I'm up now at almost 40'000 lines of source and 30'000 lines of code. ‼
( Biggest project I've ever worked on previously was at 8'000 lines of code )

The milestone (that I finished today) was for loops! As been trying to showcase in the GIF.

---

It's such a giant project and I can honestly say I've done some good work here. Self-five. Over-performing is a thing.

The things that makes me shiver though is that most that use this application will never know the intricates of it's insides, and the brain work put into it.

The project is probably over-engineered. A lot. Having a home-made compiler gives us a lot of flexibility for our product as we're trying to make more of a "pedagogic IDE". But no matter that I reinvented the wheel for the 105Gth time, it's still the most fun I've had with a project to date.

---

Also btw if anyone wants to see source code, please give me good reasons as I'm actively trying to convince my boss to make the compiler open-source.

Cheers!

So I'm a backend engineer and my boss keeps telling me I over engineer stuff. I'm never given a technical spec or architectural spec, just told what to do so I build. But apparently I over engineer? Admittedly I do tend to but recently I cba and done the most basic thing. Apparently its over engineered.
Would you agree that to say something is over engineered a technical requirements document is required in order to specify over engineered said request needs to be?

Ps: my boss is an inappropriate cunt. Finally got that out.
Feel like hes just making arguments with me to get rid of me because I didnt want to cuddle in bed with him after he gave me an uncalled for back rub..

Fuck me in the ass, but do it harder then this api just so I can feel some love 😖

it's one of those days where you have to migrate from soap to rest, only the rest api doesn't have the same structure or search parameters as the soap api, so there's this entire fucking application sending requests at a brick wall, and expecting a purple throbbing 12 inch cock of xml to be pushed into an multi dimensional array and pushed through to the views to derange the mess, only you have to create that fucking 12 inch cock from several 2 inch dipsticks that have a different hierarchy, different field names, and merge the shit together with a glue gun...

good thing it's only an unexpected prod problem... right? 🤷‍♂️

Ah, the woes of a Monday on the legacy app adventures.

I realized how overly complicated I wrote certain object oriented code a few months ago and now I have to work around it...

I over engineered it... I became the very developer I hate

Me and a fellow friend started working as a freelancer.

of 3 projects that we have:

One has a terrible code (like really nasty and over engineered to the maximum). albeit each new feature is a challenge to our sanity... they pay are are somewhat nice.

Another after we did the job they don't want to pay (thankfully we are on a platform that is like the middle man for work, they already have the money so should be "trivial") because they say we did not do what they asked. Brother, the 2 A.M. is not an hour to be called, and we did all the little shitty task they askend AND the original tasks...

And in the last one we hired a team to work with us because we don't have more hours in a day... and they only rename some vars, call it a day, ignoring the task on the sprint and they wanna get paid for the "job"

I just wanna drink a few pints of guinness...

So... Heard back from a recruiter today. Lovely lass.

I’d passed over a submission for her tech demo.

The brief was basically just to create a small simple module that calculates shit, nae effort.

But, when the recruiter had me on the phone she said “I know it’s a silly small module but try and run it up like you would a production ready app”.

The job spec and recruiter were keen on me demonstrating TDD, not specific on js version, final runtime, etc. The job was a senior spec at a higher salary range. So it warranted some effort, and demonstrating more than a simple module.

“Okay, cool, nae bother, let’s crack on.”

The feedback in the response from the dev today:
“He’s over-engineered tests, build...”

SUCK MY LEFT TESTICLE YOU FUCKWIT.

Talk to your recruiters, not me.

The feedback included a phrase I never hope to hear from a developer I work with:
“Tests are good but...” 😞

It was a standard 98% test suite from an RGR cycle, no more or less than I’d expect in prod.

The rest of the feedback was misguided or plain wrong. It was useful to see because I know now when they say they have “high standards” they mean: we listen to the dude who put the factory pattern in a JS brief.

Oh shit also: “someone’s done chmod 777” was in there as a sarcastic comment in the feedback. It was his fucking unarchive tool 😞

My response was brief and polite: “cheers for the consideration, all the best, James”

It’s honestly not worth warning them. Or, asking why they’d criticise something they’d asked me to do.

If you want a shitty js module, ask for a shitty js module and no more.

Everyone and their mother has a JavaScript framework and the NEWEST cool npm module you're an idiot for not using.

It's like musicians and gear acquisition syndrome, coders love to have new stuff even if it's over-engineered, already exists, or redundant.

Hate dealing with tech hipsters 🙄 is nothing tried and true anymore?

Regarding Article 13 (or 17 or wherever it moved to now)… Let's say that the UK politicians decide to be dicks and approve the law. After that, we need to get it engineered in, right? Let's talk a bit about how.. well, I'd maybe go over it. Been thinking about it a bit in the shower earlier, so.. yeah.

So, fancy image recognition or text recognition from articles scattered all over the internet, I think we can all agree.. that's infeasible. Even more so, during this lobby with GitHub and OpenForum Europe, guy from GitHub actually made a very valid point. Now for starters, copyright infringement isn't an issue on the platform GitHub that pretty much breathes collaboration. But in the case of I-Boot for example, that thing from Apple that got leaked earlier. If that would get preemptively blocked.. well there's no public source code for it to get compared against to begin with, right? So it's not just "scattered all over the internet, good luck crawling it", it's nowhere to be found *at all*.

So content filtering.. yeah. Nope, ain't gonna happen. Keep trying with that, EU politicians.

But let's say that I am a content creator who hates the cancer of joke/meme because more often than not it manifests itself as a clone of r/programmerhumor.. someone decides to freeboot my content. So I go out, look for it, find it. Facebook and the likes, make it easier to find it in the first place, you dicks. It's extremely hard to find your content there.

So Facebook implements a way to find that content a bit easier maybe. Me being the content creator finds it.. oh blimey! It can't be.. it's the king of freebooting on Facebook, SoFlo! Who would've thought?! So at that point.. I'd like to get it removed of course. Report it as copyright infringement? Of course. Again Facebook you dicks, don't make it so tedious to fill in that bloody report. And look into it quickly! The videos those SoFlo dicks post is only relevant in the first 48h or so. That's where they make the most money. So act more quickly.

So the report is filled, video's taken down.. what else? Maybe temporarily make them unable to post as a bit of a punishment so that they won't do it again? And put in a limit to the amount of reports they can receive. Finally, maybe reroute the revenue stream to the original content creator instead. That way stolen content suddenly becomes free exposure! Awesome!

*suddenly realizes that I've been talking about the YouTube copyright strike system all along*

… Well.. maybe something like that then? That shouldn't be too hard to implement, and on YouTube at least it seems to be quite effective. Just imagine SoFlo and the likes that are repeat offenders, every 3 posts they get their account and page shut down. Good luck growing an audience that way. And good luck making new accounts all the time to start with.. account verification technology is pretty good these days. Speaking of experience here, tried bypassing Facebook's signup hoops a fair bit and learned a bit about some of the things they have red flags on, hehe.

But yeah, something like that maybe for social media in general. And.. let's face it, the biggest one that would get hurt by something like this would be Facebook. And personally I think it's about time for that bastard company to get a couple of blows already.

What are your thoughts on this?

Received feedback on a task I made for a job interview (I didn't get a technical interview).

The task was easy with nothing special about it that made me think if that's what the job is like, I don't want to work there. It was a simple web page with search functionality. I did the task anyway.

The feedback I got was useless. It said that I made a complex and an over-engineered solution.
What I made, mind you, was a one endpoint API and a single Vue.js component instead of using jQuery to update the results. That's it. OVER-ENGINEERED!

Complete waste of time.

Before, when you bought $3k Cisco router you got the box that will run indefinitely as long as it has power in about any environment you can go to install it; with or without fans, it had more important business than to give a shit about such things.
Now, when you buy $500k Cisco box you get a over-engineered chassis with 5 separate fan modules with their own firmwares, self tests, watchdog timers and shitload of bugs. It's a fucking fan, it should spin, not do quantum chromodynamic simulations.

Pic related.

Next rant could probably be how Cisco's switch from monolithic to modular linux arhitecture (in order to reduce downtime) turned into having time bombs just waiting to do some crazy shit.

I've been working for the last 5 years on some large legacy code used in production, more than 100K LOC, poor comments (when existing) often outdated, huge parts of code that can no longer be reached, over-engineered class hierarchy, functions of thousands lines, huge parts of deprecated code that cannot be removed because "someone might still be using it". Statistically, every small change caused 3 new issues somewhere else and every bug fix or new feature required 10 times the time that would be necessary with a decent codebase. But after five years in hell I can finally say that... Oh wait, nothing changed, the code is still legacy and nobody is going to do anything about that.

I don't want to work on the project at my job anymore. It's an over engineered piece of shit.

I work on my pet project at home, but only for about 20 minutes at a time. After that, I feel the need to walk away and waste my time with other non-productive activities.

How do I get my love for development back? Has the corporate world killed it?

Data Scientists/Researchers

Stop building libraries.
You can't build libraries.
You're not software engineers.

Write your script as plainly as possible.

Why?

Cus for every fucking paper that has code associated with it, unless it's from Meta or Google, I'm having to edit to make shit work.

Stop over-engineering shit.

Write your model and fuck off.

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

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

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

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

From someone who committed that crime.

Anyone else think it's crazy how over engineered it's become to render a website? Why do we need to invent the world everytime??

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

! Rant
So this project manager from a start up contacted me about a few Jobs are they are looking to get done for their app. They asked for cost and I gave them a ballpark range depending upon the type of work. Anyway, after getting a tour of their over engineered app with 128 menu items for a users to go through to get something done, I gave them the hourly rate on the "higher" side of the ballpark which was $5/hr more than lower. Guess what, next I get an email with 4 huge paragraphs, explaining how I am trying to charge them so much extra and is way over the quote. I passed myself laughing and wished him good luck with their start up...

Can we please make a Over Engineered Section....

This happened a couple of weeks ago...
Hey platform engineer team, we need a environment spun up, it's a static site, THATS IT!

PE Team response.. okay give us a 2 weeks we need to write some terraform, update some terraform module, need you to sign your life away as the aws account owner, then use this internal application to spin up a static site, then customize the yml file to use nuxt, then we will need you to use this other internal tool to push to prod...

ME: ITS a static site... all I need is a s3 bucket, cloudfront, and circleci

Holy fucking shit, I can't stand this corporate framework they use for this banking app on which I've been working on for 2 months.

I’ve spent the last damn month just building three basic screens, and now my very first PR is buried under 50 fucking comments. Half of them exist purely because their shitty framework has multiple versions stacked and stitched together with so many workarounds that you need so much domain knowledge that intuition or actual dev experience goes out the window.

They’ve abstracted real app development into oblivion. It’s a CRUD app, but they've over-engineered it so much they’re now creating their own problems — just so they can specialize in solving them. It's become this self-sustaining nightmare where they make themselves irreplaceable... and simultaneously unemployable anywhere else.

I genuinely have no idea what I’m doing with my life anymore. The original plan was six months here, grab a mortgage, fuck off, and go back to contracting.

Now I’m stuck questioning my sanity every time I open this project or have to listen to another lecture from my 'buddy' about how everything that I'm doing is wrong.

The worst co worker I had is actually pretty recent. He joined a well integrated team on what was basically a legacy project. He sounded like a good developer and seemed to know his stuff but it took him ages to push out fixes/features. They were always massively over-engineered, poorly named, partially tested and what documentation he did write still managed to bitch about how poor the project was structured.

He spent most of his time bitching about the general shitty nature of the project (he wasn't wrong) and the lack of interest from other Devs.

He was so unpleasant in interpersonal communication that by the end no one would work with him.

In his last team meeting he basically said he was glad to be going and that we were all lazy, disinterested and shouldn't consider ourselves his peers. The equivalent of storming out of a party after setting the couch on fire and shitting in the sink.

We've since removed all his overcomplicated, not standard, unmaintainable code.

I was asked to make proof of concept small frontend app with some simplified requirements, they asked me because it should be written in the stack I done most of my career work with. I do it in 3 days instead of 5, using those 2 days to optimise the app and explore different approaches. I noted down my findings, what to avoid and reasons and also what is good to use and reasons and shared with everyone.

We waited for the project to start, I started working on another project in the meantime and there was a big rush to make project go live etc., so I was consumed 100% on that new project.

So they put in charge backend php developer to do frontend js work. I said ok, do you need help in starting out? Nah, my proof of concept repo is enough.

4 days before that small project goes live they asked me to do code review. All things I noted down to avoid are in the codebase, few bad practices but everything is over-engineered (in a very bad way), some parts should be more flexible as current setup is very rigid, having almost all kinds of CSS, I saw SASS, CSS variables, 2 different CSS-in-JS tools with some additional libraries that is used to toggle classes.

I don't know how to approach this as I am not asshole as a person and I don't want to say to my colleague that his codebase is completely trash, but it is.

The worst parts: They called me to help finish the app and budget is almost spent!

I would rewrite the whole app as the state of the current app is unusable and everything is glued with bad Chinese ducktape that barely holds.

Additional points because it won't bundle as everything is f**ked.

I am seriously thinking of duplicating master branch and refactor the whole fricking app but won't do that as I am burning midnight oil on other two projects. Don't worry overtimes are paid.

I hate those shitty situations, this project was supposed to be tiny, sweet and example of decent project in this company but it is instead big fat franken-app that will be example how smart it is to avoid putting backend dev to do frontend work (I also agree for vice versa)!

I need some opinions on Rx and MVVM. Its being done in iOS, but I think its fairly general programming question.

The small team I joined is using Rx (I've never used it before) and I'm trying to learn and catch up to them. Looking at the code, I think there are thousands of lines of over-engineered code that could be done so much simpler. From a non Rx point of view, I think we are following some bad practises, from an Rx point of view the guys are saying this is what Rx needs to be. I'm trying to discuss this with them, but they are shooting me down saying I just don't know enough about Rx. Maybe thats true, maybe I just don't get it, but they aren't exactly explaining it, just telling me i'm wrong and they are right. I need another set of eyes on this to see if it is just me.

One of the main points is that there are many places where network errors shouldn't complete the observable (i.e. can't call onError), I understand this concept. I read a response from the RxSwift maintainers that said the way to handle this was to wrap your response type in a class with a generic type (e.g. Result<T>) that contained a property to denote a success or error and maybe an error message. This way errors (such as incorrect password) won't cause it to complete, everything goes through onNext and users can retry / go again, makes sense.

The guys are saying that this breaks Rx principals and MVVM. Instead we need separate observables for every type of response. So we have viewModels that contain:

- isSuccessObservable
- isErrorObservable
- isLoadingObservable
- isRefreshingObservable
- etc. (some have close to 10 different observables)

To me this is overkill to have so many streams all frequently only ever delivering 1 or none messages. I would have aimed for 1 observable, that returns an object holding properties for each of these things, and sending several messages. Is that not what streams are suppose to do? Then the local code can use filters as part of the subscriptions. The major benefit of having 1 is that it becomes easier to make it generic and abstract away, which brings us to point 2.

Currently, due to each viewModel having different numbers of observables and methods of different names (but effectively doing the same thing) the guys create a new custom protocol (equivalent of a java interface) for each viewModel with its N observables. The viewModel creates local variables of PublishSubject, BehavorSubject, Driver etc. Then it implements the procotol / interface and casts all the local's back as observables. e.g.

protocol CarViewModelType {
isSuccessObservable: Observable<Car>
isErrorObservable: Observable<String>
isLoadingObservable: Observable<Void>
}

class CarViewModel {
isSuccessSubject: PublishSubject<Car>
isErrorSubject: PublishSubject<String>
isLoadingSubject: PublishSubject<Void>

// other stuff
}

extension CarViewModel: CarViewModelType {
isSuccessObservable {
return isSuccessSubject.asObservable()
}
isErrorObservable {
return isSuccessSubject.asObservable()
}
isLoadingObservable {
return isSuccessSubject.asObservable()
}
}

This has to be created by hand, for every viewModel, of which there is one for every screen and there is 40+ screens. This same structure is copy / pasted into every viewModel. As mentioned above I would like to make this all generic. Have a generic protocol for all viewModels to define 1 Observable, 1 local variable of generic type and handle the cast back automatically. The method to trigger all the business logic could also have its name standardised ("load", "fetch", "processData" etc.). Maybe we could also figure out a few other bits too. This would remove a lot of code, as well as making the code more readable (less messy), and make unit testing much easier. While it could never do everything automatically we could test the basic responses of each viewModel and have at least some testing done by default and not have everything be very boilerplate-y and copy / paste nature.

The guys think that subscribing to isSuccess and / or isError is perfect Rx + MVVM. But for some reason subscribing to status.filter(success) or status.filter(!success) is a sin of unimaginable proportions. Also the idea of multiple buttons and events all "reacting" to the same method named e.g. "load", is bad Rx (why if they all need to do the same thing?)

My thoughts on this are:

- To me its indentical in meaning and architecture, one way is just significantly less code.
- Lets say I agree its not textbook, is it not worth bending the rules to reduce code.
- We are already breaking the rules of MVVM to introduce coordinators (which I hate, as they are adding even more unnecessary code), so why is breaking it to reduce code such a no no.

Any thoughts on the above? Am I way off the mark or is this classic Rx?

I need to vent or I'm going to fucking explode like a car filled with bombs in motherfucking Iraq...

A couple of months ago I inherited a project in development from our team leader who was the sole developer on it and he was the one who designed every single thing in it.

I was told the project is clean, follows design patterns, and over all the code is readable and easy.

Those were all fucking lies.

See throughout the period he was working on it, I saw some of the code as it was going through some pull requests. I remember asking the dev why he doesn't comment his code? His response was the most fucking condescending shit I've ever heard: "My code is self-documenting"...

Now that I have full control over the code base I realize that he over engineered the shit out of it. If you can think of a software design pattern, it is fucking there. I'm basically looking at what amounts to a personal space given to that dev to experiment with all kind of shit.

Shit is way too over engineered that I'm not only struggling to understand what the hell is going on or how the data flows from the database to the UI and in reverse, I'm now asked to finish the remaining part and release it in 8 weeks.

Everything is done in the most complicated way possible and with no benefits added at all.

Never in my career have I ever had to drag my sorry ass out of bed to work because I always woke up excited to go to work... well except for the last 2 weeks. This project is now taking a mental toll and is borderline driving me crazy.

Oh, did i tell you that since he was the only dev with no accountability whatsoever, we DO NOT EVEN KNOW WHAT IS LEFT TO BE IMPLEMENTED?

The Project Manager is clueless.. the tickets board is not a source of truth because tickets set to resolved or complete were actually not even close to complete. FUCK THIS SHIT.

For the last week I've been working on 1 single fucking task. JUST 1. The whole code base is a mine field. Everything is done in the most complicated way and it is impossible for me to do anything without either breaking shit ton of other features (Loosely coupled my ass) or getting into fights with all the fucking libraries he decided to use and abuse.

1 whole week and I can't even get the task done. Everyday I have to tell the project manager, face to face, that I'm still struggling with this or that. It's true, but i think the project manager now thinks i am incompetent or just lazy and making excuses.

Maybe I'm not smart enough to understand the what and why behind every decision he made with this code. But I'm sick to my stomach now thinking that I have to deal with this tomorrow again.

I don't know if I'll make the deadline. But I'm really worried that when this is released, I'll be the one maintaining that nightmare of a code base.

From now on, if i hear a fucking developer say their code is "self-documenting" I will shove my dick + a dragon dildo + an entire razor gaming keyboard up their ass while I shoot their fucking knees off.

oh... and there are just a couple of pages of documentation... AND THEY ARE NOT COMPLETE.

As a vue fan who has to work with react - I don't understand the appeal of the latter. Everything seems just pointlessly dotted with boilerplate, grossly over-engineered (if that's what I should call solutions like the react approach to CSS-in-JS) but at the same time very clunky.

Honestly, the only convincing point for using React that I've heard is about it being backed by Facebook - but, on the other hand, After having to work with some facebook IT solutions and knowing the shit they could pull with their APIs and stuff, I wouldn't count it as too big of an upside.

Why didn't you switch from react to vue?

iOS 10 pulls this 3D Touch shit on me and they're dropping headphone jacks. What's next? Vegan iPhones? Gluten free home buttons? Over engineered shit. Nobody wants 3D Touch. It's stupid.

Holy fuck why is redux so over engineered. How did everyone let it get this far.

Which do you prefer over-engineered or under-engineered codes?

Frameworks piss me off... So many to out there that are over engineered and complicated... And achieve exactly the same fucking thing...

Just noticed a thread on r/programmerhumor about bank code intentionally adding delays with all these JavaScript code blocks of how it's adding sleep cycles in.

So I spent an hour reading the documentation and wrote up an over engineered solution in COBOL just to prove a point.

If only more devs would use short, yet concise, modern constructs instead of archaic ones.

For example in C#: using lambdas, extension methods, LinQ,.. much easier to read through if you know how these work, rather than having to spend all day scanning tedious for-loops and over-engineered classes your colleagues wrote who don't know any better.

Examples:

vs.foreach(v => console.write(v));

initialList = secondList.Where(p => initialList.Contains(p, valueComparer))
.Concat(initialList.Where(p => !secondList.Contains(p, valueComparer))).ToList();

So I've been using Duet on my iPad Pro for a couple years now (lets me use it as an external monitor via Lightning cable) and without issue. Shit, I've been quite happy with it. Then the other day, whilst hooked up to my work laptop, there was a power fluctuation that caused my laptop to stop sending power to connected devices. Which is fine - I have it plugged into a surge protector so these fluctuations shouldn't matter. After a few seconds the laptop resumed normal operation and my connected devices were up and running again.

But the iPad Pro, for some reason, went into an infinite boot loop sequence. It reboots, gets to the white Apple logo, then reboots again.

In the end, after putting the iPad into recovery mode and running Apple's update in iTunes (as they recommend), it proceeds to wipe all my data. Without warning. I lost more than a couple of years of notes, illustrations and photos. All in one fucking swoop.

To be clear, you get 2 options in iTunes when performing a device update:

1. UPDATE - will not mess with your data, will just update the OS (in this case iPadOS)
2. RESTORE - will delete everything, basically a factory reset

I clicked UPDATE. After the first attempt, it still kept bootlooping. So I did it again, I made sure I clicked UPDATE because I had not yet backed up my data. It then proceeds to do a RESTORE even though I clicked UPDATE.

Why, Apple? WHY.

After a solemn weekend lamenting my lost data, I've come a conclusion: fuck you Apple for designing very shitty software. I mean, why can't I access my device data over a cabled connection in the event I can't boot into the OS? If you need some form of authentication to keep out thieves, surely the mutltiple times you ask me to log in with my Apple ID on iTunes upon connecting the damn thing is more than sufficient?! You keep spouting that you have a secure boot chain and shit, surely it can verify a legitimate user using authenticated hardware without having to boot into the device OS?

And on the subject of backing up my data, you really only have 2 manual options here. Either (a) open iTunes, select your device, select the installed app, then selectively download the files onto my system; or (b) do a full device backup. Neither of those procedures is time-efficient nor straightforward. And if you want to do option b wirelessly, it can only be on iCloud. Which is bullshit. And you can't even access the files in the device backup - you can only get to them by restoring to your device. Even MORE bullshit.

Conversely, on my Android phone I can automate backups of individual apps, directories or files to my cloud provider of choice, or even to an external microSD card. I can schedule when the backups happen. I can access my files ANYTIME.

I got the iPad Pro because I wanted the best drawing experience, and Apple Pencil at the time was really the best you could get. But I see now it's not worth compromise of having shitty software. I mean, It's already 2021 but these dated piles of excrement that are iOS and iPadOS still act like it's 2011; they need to be seriously reviewed and re-engineered, because eventually they're going to end up as nothing but all UI fluff to hide these extremely glaring problems.

Mention one example of over engineered and overcomplicate framework ?

I start : Angularjs

Poorly built software is the other side of the coin of over-engineered software. They both exist because users carelessly use software products. By not exercising the code enough, or system failure not costing the business more penalties than they can bear, incompetent developers will continue to get away with building things haphazardly –not as relates to tech stack, but the nitty-gritty implementation details they gloss over without adequately thinking through

Because of this, there doesn't seem to be sufficient incentive for thorough planning –what could be referred to as over-engineering. Those fancy pedantry in code mostly goes unnoticed by the end user. Of course, this doesn't apply to big corporations in most cases. It's usually unexpected to see elementary bugs in them

Ranting (again) against the almighty marketing teams. So recently we started to build an amazing feature for our product but have been told to put the project on hold to help the "conversion team" which is focusing on trial, subscription and payment. But we are lagging behind the competitors regarding the features, for a huge price. But marketing wants that. Marketing wants an over engineered flow to be "fixed" for the 382948 time. Never had an impact on the conversation and will never have. So here is the truth : marketing stir the air because of their damn complex of inferiority and their inability to build anything.

Going to begin an intranet web application. Confused between choosing Angular, Vue or React.

I have worked with Angular but this application will be managed by some junior developers with me overlooking it. And Angular seems overkill regarding this, it is too over engineered and then there is TypeScript. So I am thinking from the perspective of those junior developers so that they don't face a huge learning curve and become productive very fast.

Then there is the bullshit that usually goes around in every corporate intranet application where management becomes too nosy. That's why I decided that back end API should be done with Laravel which is stable not some kiddie framework of Node.js

Damn, .NET devs are really and I mean really bad at writing documentation. It is either over-engineered (anything from Microsoft) to the point you can't find shit. Or it is almost non existent and you have to study the repo and read classes, etc. (ANY .net core nuget for writing CLI apps, heck I would argue almost any nuget in general)

4 pages on github WIKI + examples that cover 20% of use cases are not a bloody documentation mate!!!

I used to be linux + any of Python/Go/JS/Ruby/Elixir guy and almost never had problems with poor documentation.

Now living in Microsoft world with .net and powershell is terrifying.

In few months I went from working independently on a project while developing lots of vertical knowledge to being body rented to another company where I spend most of my time doing calls and continuously reworking a suite of over engineered micro services (after ages instead of progressing we’re rewriting for the nth time basic CRUD because the team keeps coming with new refactoring ideas and since budget/time limit aren’t tight nobody on the high management seems to care of the time we’re wasting). I miss being able to stay “in the zone” for hours without calls, being challenged and learning on the job so I’m considering to find another job.

I spent two hours to come up with an algorithm to detect a win and also one to derive the winning indices on any tic tac toe board as long as the size is provided

but i have spent more than twice that same amount of time trying to style component with the shiny toys provided my material ui.

I really just wanted to write less code, but now I have a headache

with my code looking like the death, thanks to the over engineered components provided by material ui

there has to be a way to manage medium to large react codebase

I've googled but everything I see is beginner level stuff, any tips will be appreciated at this moment

Why on earth would you create an entire new HTMLImageElement in the javascript file just to get the width and height of an image and never render it to the DOM. FFS use MS Paint, 3D Paint or ANY OTHER IMAGE EDITING SOFTWARE to get the size.

Seriously you over engineered the shit out of the easiest const you'll ever write in JavaScript.

And for the record, the width and height of the image used are only used in formulas which produce the actual width and height of the mock buttons that get drawn onto the canvas element. And don't worry, the click event handler for these mock buttons is actually the click event handler for the canvas...which checks the coordinates of where the click was made on the canvas. And if the click is over where the button is drawn in, congrats you clicked the button.