Memories of waiting for months to get access to a MS SQL database and ending up putting an Access database on a network share for multiple user access instead. A horrible, horrible hack solution. But it worked!
After 15 years, I use Outlook as my build pipeline
11–20 of 73 posts
Re: After 15 years, I use Outlook as my build pipeline
#12[flagged]
If your build pipeline is anything more than a monkey scratching bits into a spinning disk using a needle, you are a fraud.
Re: After 15 years, I use Outlook as my build pipeline
#13[flagged]
Uses kubernetes, blames others for over engineering. Are we living in a parody? Oh wait…
Re: After 15 years, I use Outlook as my build pipeline
#14[flagged]
No plan survives contact with the enemy.
Sure, "docker push" is all fine and well until "after two weeks, [your] coworker still does not have access to the server endpoint that he and [you] would need". And then what? Do you quit your job for fear that someone calls you a hack?
Re: After 15 years, I use Outlook as my build pipeline
#15[dead]
Re: After 15 years, I use Outlook as my build pipeline
#16[flagged]
Thankfully k8s is not overengineered or you’d have pie on your face.
Re: After 15 years, I use Outlook as my build pipeline
#17>Shoddy stuff that has no chance of making its way into production is permissible
That's cute.
Re: After 15 years, I use Outlook as my build pipeline
#18I knew a guy who would brag that he used Outlook as his build system 20 years ago. Builds would take 9 to 24 months depending on the complexity of the project. But, as the CTO of a mid-sized software company, it worked for him.
CTOs are the original vibe coders.
Re: After 15 years, I use Outlook as my build pipeline
#19Re: After 15 years, I use Outlook as my build pipeline
#20I don't know if Telegram, Slack, Discord, GitHub Actions, GitLab CI, Jenkins, or Kubernetes will be around (or without massive breaking changes) in 20 years, but email absolutely will be.