> In industrial scale software development, gaining access you are fully entitled to can sometimes take weeks. 4 years in consulting. I've spent the first WEEKS of a project twiddling my thumbs waiting for a laptop, just to spend more weeks waiting on access to source code, tooling, etc. My friends on the strategy side could start and finish entire projects in that time.
After 15 years, I use Outlook as my build pipeline
61–70 of 73 posts
Re: After 15 years, I use Outlook as my build pipeline
#62>When you leave software developers alone for too long, they start developing software I've gotten so bored at work lately I've been coding for fun again
What job do you have that you get paid to do nothing?
Re: After 15 years, I use Outlook as my build pipeline
#63Re: After 15 years, I use Outlook as my build pipeline
#64Memories 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!
I ended up building an Access app at an enterprise-y company I used to work at because it would have taken years for IT to build it. The app did something super specific and kept needing super specific additional features, and there wasn't anything on the market that met our needs. The Access UI talked to another Access database on a shared network drive. I just found out that it's still being used heavily by several people every day, 17 years later. You pretty much nailed it, Access is hacky, but it works!
Edit: grammar
Re: After 15 years, I use Outlook as my build pipeline
#65Re: After 15 years, I use Outlook as my build pipeline
#66[flagged]
People don't get sarcarm :/ Totally unrelated, if you need to suffix a k8s deployment with "-deployment" you are a hack, a fraud, an overengineer and someone who should NOT work as software or devops engineer.
Famously so. If you want to remain unmisunderstood, make sure to use sarcasm. Draw a clear line into the shifting sand while cocking a single eyebrow. It's widely appreciated, it's an artform, and the comments are a blast. :)
Re: After 15 years, I use Outlook as my build pipeline
#67Memories 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!
Re: After 15 years, I use Outlook as my build pipeline
#68Earlier quoted context omitted.
For a moment there I thought this was the parody llm HN site.
Please give me the link
Re: After 15 years, I use Outlook as my build pipeline
#69In the middle are Mule, Rabbit, Kafka, ZMQ.
At the other end is UDP multicast, and I still use that for VM hosts or where I can trust the switch.
Re: After 15 years, I use Outlook as my build pipeline
#70> In industrial scale software development, gaining access you are fully entitled to can sometimes take weeks. 4 years in consulting. I've spent the first WEEKS of a project twiddling my thumbs waiting for a laptop, just to spend more weeks waiting on access to source code, tooling, etc. My friends on the strategy side could start and finish entire projects in that time.
Not necessarily worse, but the stereotype fits! You are, at least, soon doing tangible things.