this post was submitted on 08 Oct 2023
179 points (96.9% liked)

Programming

17508 readers
9 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago
MODERATORS
snowe
Ategon
[email protected]
179
What's the dumbest thing you've shipped? (lemmy.world)
submitted 1 year ago by [email protected] to c/programming
59 comments fedilink hide all child comments
 

18 month project is winding down. I suspect it will have 1 use in the next 4 years we are supporting it.

The tool is basically a copy of the S3 browser, only shittier. The license for the S3 browser is only 20 bucks btw.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 22 points 1 year ago (1 children)

This was a series of decisions with good intentions that went poorly in the long run.

Our customer wanted us to setup a system so their users could track their products from their site from a variety of carriers; but their backend was very old and difficult to work with, and their network very locked down.

We were struggling to setup a single carrier, so we eventually decided to setup a new server with modern tooling on our own network so we could develop this and other “complicated” features with less pain, and they would only have to make a single exception to their firewall.

Fast forward a year and:

  • They didn’t request any more “difficult” features, so the server was serving a single API
  • One of our carrier’s API keys had expired and nobody noticed because they weren’t using it, and they didn’t request support for additional carriers either
  • Somebody on their security team noticed the strange calls to our servers and demanded we moved the API to their infrastructure anyway