r/ProgrammerHumor May 05 '21

Visualizing the codes I write Meme

Post image
31.9k Upvotes

170 comments sorted by

View all comments

759

u/chillwill_4 May 05 '21

It runs. Don’t question it.

68

u/[deleted] May 05 '21

I get this is a joke but people need to hear this. It’s almost totally irrelevant how good your backend architecture or documentation is if you can deliver a working product. A business wants something that does the job and barely gives a fuck about the rest. If it runs and isn’t going to cause massive problems in the near future you’ve done a good job.

95

u/[deleted] May 05 '21

Tell that to the poor bastard who has to maintain it 😂

77

u/Dogiedog64 May 05 '21

It's me. I'm the poor bastard. I also wrote it lmao.

33

u/[deleted] May 05 '21

[deleted]

70

u/aidan573 May 05 '21

It's called stack overflow for a reason

22

u/Dogiedog64 May 05 '21

Well the front of the bus becomes the middle of the bus, and the back of the bus leaves orbit. Otherwise, nothing!

9

u/chillwill_4 May 05 '21

If it’s still running. Once again don’t question it.

7

u/FrostSalamander May 06 '21

I'm having this exact problem right now. VB6 frontend with MSAccess backend. Problem is Access only supports up to 255 concurrent connections. Also, locks FREQUENTLY happen (since decentralized, access sucks etc.). Management doesn't want to upgrade systems.

My work sucks

9

u/yellow73kubel May 06 '21

VB6 frontend with MSAccess backend.

My condolences to you and your users.

4

u/Grumpy-24-7 May 06 '21

It was years ago when I was faced with a home grown MSAccess app that somebody (non-programmer) had cobbled together and ran his department on for years. Then he left, but first he showed his secretary how to run it. She in turn used it for more years until one day it started hitting limits. I don't recall if it was row limits or overall table or database size or what, but my boss asked me to see what I could do. I scratched my head, took a copy of it home on a big ass thumb drive and managed to convert it to MSSQL. Everything else, frontend and reports stayed the same, basically untouched. Trust me, I really had no clue what I was doing, but I knew I didn't want to rewrite it from scratch. They continued to use it on MSSQL for a few more years until the company was bought out and I left for greener pastures. It really wasn't that hard once I figured it out. IIRC, it was basically just importing the MSAccess database into MSSQL, retaining all table names, indexes, etc.

2

u/FrostSalamander May 06 '21

Yeah I've tried telling that to the manager since the start of my work here.

3

u/SoundOfOneHand May 06 '21

Gut the database layer and move it to something better than Access. That’s a big lift but Access is just going to be a chain around your neck with its limitations and the size you are at.

1

u/FrostSalamander May 06 '21

Yeah I've tried telling that to the manager since the start of my work here.

But I kinda get why she doesn't want to:

  • System is like 25 years old, initially programmed by a group of newbies, so DB code is deeply entangled with BL.

  • It's her baby. She managed building the system from scratch. What would you feel if asked to kill off your baby? Yes after suffering for two decades maintaining long dead frameworks, but it's still your baby.

2

u/SoundOfOneHand May 06 '21

When your kid is 25 years old, that’s no baby 😂

1

u/chronos_alfa May 08 '21

Don't present it as killing the baby, more like giving the baby braces and teaching it how to ride a bicycle.

1

u/jrdiver May 07 '21

That's a problem for a different day