Asklemmy

43948 readers

489 users here now

A loosely moderated place to ask open-ended questions

Search asklemmy 🔍

If your post meets the following criteria, it's welcome here!

Open-ended question
Not offensive: at this point, we do not have the bandwidth to moderate overtly political discussions. Assume best intent and be excellent to each other.
Not regarding using or support for Lemmy: context, see the list of support communities and tools for finding communities below
Not ad nauseam inducing: please make sure it is a question that would be new to most members
An actual topic of discussion

Looking for support?

Looking for a community?

Lemmyverse: community search
sub.rehab: maps old subreddits to fediverse options, marks official as such
!lemmy411@lemmy.ca: a community for finding communities

~Icon~ ~by~ ~@Double_A@discuss.tchncs.de~

founded 5 years ago

MODERATORS

175

What is the worst IT setup you have seen at a company? (sh.itjust.works)

submitted 4 months ago* (last edited 4 months ago) by gnutard@sh.itjust.works to c/asklemmy@lemmy.ml

125 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] rekabis@lemmy.ca 5 points 4 months ago (1 children)

every bit of business logic was implemented in Stored Procedures and Triggers on a MSSQL database.

Provided the SP’s are managed in a CVS and pushed to the DB via migrations (similar to Entity Framework), this is simply laborious to the devs. Provided the business rules are simple to express in SQL, this can actually be more performant than doing it in code (although it rarely ever is that simple).

There were no frontend code either on the server, users have some ActiveX controls installed locally that accessed the DB.

This is the actual WTF for me.

[–] wintermute@discuss.tchncs.de 5 points 4 months ago

There was no version control at all. The company that provided the software was really shady, and the implementation was so bad that the (only) developer was there full time fixing the code and data directly in production when the users had any issue (which was several times a day).