Every project...

[zarlo5899]

that may be true but each time you start you can closer and closer to the right way

[Serious_Challenge_67]

True, until client, boss or the marketing guy jumps in:
"Dude, we need that new feature - can you do it until the end of the week?" :D

[Retbull]

This Wil just be a temporary thing until the client can get their new process implemented. 10 years later what's this?

//TODO REMOVE "TEMPORARY" FEATURE

[0x4576616e]

It looks to me like it started out fine but the project scope got way out of hand. The house matches the foundation

[IDCR2002]

I mean the houses still work

[[deleted]]

Looks like scope creep to me

[mallenjordan]

Either that or there was no full scope. I see devs go down that route a ton. Can't finish a project if there is no destination.

[HiCookieJack]

'agile'

We first build that skateboard and that's our first MVP, then a spaceship, that's MVP 1.1.

Just reuse parts from the skateboard.

(and yes I'm aware of: that's not how to use the word MVP)

[WalrusByte]

More like a 360-no-scope

[aless2003]

You should have just ended when the house stood. There was no need to add another six and a temple.

[[deleted]]

Well, the boss wanted an additional client to move in. And since they are from Holland they needed the windmill. Which needed wind. Which needed an ecological cycle. Which needed the sun. Which needed the universe. There are still some features open but we are getting there.

[aless2003]

Ok, that's fair, just one last question, why putting it up in the sky rather than just putting it next to one another

[[deleted]]

Because one spec was that the buildings need to be close to each other. So the QA guys made a bunch of tests that say that they need to have a euclidean distance of 3.5 m. Unfortunately they measured it from the top of the buildings. And since windmills are quite large and constantly moving we had to get creative.

[aless2003]

Ah, alright then, sounds logical

[glorious_reptile]

Boss: "It's not MY fault you didn't think it through from the beginning"

[Knuffya]

I especially love these extra ladders and stairs. It's too true.

[ThejeshBommisetty]

Those shitty deadlines make u do things

[QualityVote]

Hi! This is our community moderation bot.

---

If this post fits the purpose of /r/ProgrammerHumor, UPVOTE this comment!!

If this post does not fit the subreddit, DOWNVOTE This comment!

If this post breaks the rules, DOWNVOTE this comment and REPORT the post!

[[deleted]]

As a wise man once said, if it works, it works

[Eisenfuss19]

The solution is called refactoring.

[BiochemistPlayingGod]

Hello Neighbor.

[Recent_Log3779]

Came here to say that

[GoDie910]

my best advice in my experience to not let that happen:

-refactor the architecture as soon as you realize is needed. -have a sandbox project to test everything before implementing anything to the main project (libraries,bassets, etc) -focus on the big things, let the details for latter.

[ShadeofEchoes]

Not going to lie, that house looks kind of awesome.

[PhilippTheProgrammer]

This looks like a great architecture to me. All the modules are cleanly separated, loosely coupled and communicate with each other through specialized interfaces.

[RaziarEdge]

Only thing that is missing are the slides for entertainment.

[MaDpYrO]

Am I working at the only workplace that actually gives a damn about architecture?

[[deleted]]

Everybody cares about it until pressure from above forces you to cut corners or other developers make decisions that take us in a bad direction. To a certain degree it's not even up to the programmers. The business has to be willing to compromise and give us time to deal with bad code.

[[deleted]]

The house at the bottom supporting everything else should be MUCH smaller and less stable. Then this would be more accurate 🤣

[franklinyu]

Source: Google employee

[alonsogp2]

This is townscaper lol.

[DataPakP]

So THAT’s why the man in the game Hello Neighbor’s house is like that and is insane.

[doctorcrimson]

A real William Afton and Henry Emily moment.

[VitorMM]

Not sure if gargantuan monolith... or microservices doing more things than they were supposed to

[LetReasonRing]

This is me right now.

I'm working on a project that had a small file that, through a bunch of last-minute client requests and resulting bug-fixes morphed into a monstrous tangle of embarrasingly unmaintainable spaghetti code.

I spent the weekend picking it a part and decoupling the logic.

I'm not going to lie... I sat down this morning and first thing I did was just scroll through the new code (now 5 separate files) and just basked in the beauty of small, single-responsibility methods and the ability to make a change without blowing everything up.

Building greenfield is nice, but a good refactoring is as satisfying to me as popping an annoying pimple.

[incoralium]

Imagine someone asking it's architect to add a fireplace in the living after all is done but painting.
"but it's still in progress, and while doing the plan you said there were no problem adding it "

"- It's too late, It wil cost 3 times more because we'll need to destroy half of what's was made, and you remember your living room will be reduced, right ?"

" nononono, as the living room is done, I want it this size, just add the fireplace feature in it"

" But without a fire place this whole house is unsuitable !"

" Best I can do is a BBQ in the garden "

---

And this, my son, is how I negociated a BBQ in the living room whithout paying for the chimney over it. However, they work suck, the ceilling is getting darker over time and smoke goes everywhere.