11 ms·

I joined HashiCorp in 2016 to work on Nomad and have been on the product ever since. Definitely a lot of feelings today. When I joined HashiCorp was maybe 50 pe

I joined HashiCorp in 2016 to work on Nomad and have been on the product ever since. Definitely a lot of feelings today. When I joined HashiCorp was maybe 50 people. Armon Dadgar personally onboarded us one at a time, and showed me how to use the coffee maker (remember to wash your own dishes!). There have been a lot of ups (IPO) and downs (BUSL), but the Nomad team and users have been the best I've ever gotten to work with. I've only ever worked at startups before, but HashiCorp itself left that category when it IPO'd. Each phase is definitely different, but then again I don't want go back to roadmapping on a ridiculously small whiteboard in a terrible sub-leased office and building release binaries on my laptop. That was fun once, but I'm ready for a new phase in my own life. I've heard the horror stories of being acquired by IBM, but I've also heard from people who have reveled in the resources and opportunities. I'm hoping for the best for Nomad, our users, and our team. I'd like to think there's room in the world for multiple schedulers, and if not, it won't be for lack of trying.

linuxftw 2y ago
There are no resources and opportunities after being acquired by IBM. I worked for Red Hat when they were acquired. Our former CEO was quickly shown the door. We were making so much profit, almost a $1B in quarterly revenue. I left not long after the acquisition. Not long after I left, they laid off a bunch of staff. No matter what they tell you, your day to day will not improve. For my area, it was mostly business as usual, but a net decrease in comp because IBM's ESPP is trash.
- deleted 2y ago
  [deleted]
- zzzeek 2y ago
  if you left right after the acquisition how can you even speak to what the experience has been?
  - linuxftw 2y ago
    It was within a year, not like the day after.
  - worthless-trash 2y ago
    I have found the experience very different than what the OP's experience is. As you know the layoffs that happened were around the same time as the rest of the industry layoffs were happening (fashion firing), I don't feel like it had a significant effect on the culture. I am fully remote though, and have been for 15 years.
    - linuxftw 2y ago
      What part of my experience did you find different than your own? I said the day to day was mostly the same, minus the decrease in comp. I mostly was trying to articulate that the idea that IBM is going to 'super power' Hashicorp is not real, despite what IBM says. A lot of what was communicated during the acquisition process was how IBM was going to super power Red Hat and help Red Hat grow into an even larger entity, and how Red Hat actually need IBM to survive.
      - worthless-trash 2y ago
        > There are no resources and opportunities after being acquired by IBM. Got promoted twice, once between teams. Went to multiple countries and I was in product security (cost center ) at the time. > No matter what they tell you, your day to day will not improve. I am down to a 40 hour work week, down from 50-60. > Not long after I left, they laid off a bunch of staff. I don't see any difference, corporate has laid off many different groups, I guess the only different to the mothership laid off people in the US so it hits closer to your home. I've seen layoffs in Support in phillipines, Documentation in Brisbane, Most of Singapore GLS/GPS. The USA has always been insulated from the layoffs because execs find it harder to lay off people you meet in the corridors. > A lot of what was communicated during the > acquisition process was how IBM was going to super > power Red Hat and help Red Hat grow into an even > larger entity, and how Red Hat actually need IBM to > survive. Maybe this was in the US, most of the IBM briefing/cheerleading meetings were not held during the APAC timezone so I skipped them and prioritized high value work. I have always assumed that if I needed to know something my manager would tell me. If i was getting let go, nothing I could do about it if I was already doing the work I was supposed to be doing.
spicyusername 2y ago
Unfortunately IBM is going to ruin everything that was good about working for Hashicorp and eventually everything that was good about Hashicorp products. I worked for a company acquired by IBM, and we held hope like you are doing, but it was only a matter of time before the benefit cuts, layoffs, and death of the pre-existing culture. Your best bet is to quit right after the acquisition and hope they give you a big retention package to stay. These things are pretty common to ease acquisition transitions and the packages can be massive, easily six figures. Then when the package pays out you can leave for good.
- zzzeek 2y ago
  Red Hatter here. none of that has happened for us at Red Hat. Other than the one round of layoffs which occurred at the time that basically every tech company everywhere was doing much larger layoffs, that was pretty much it and there's no reason to think our layoffs wouldn't have been much greater at that time if we were not under the IBM umbrella. Besides that, I dont even remember when we were acquired, absolutely nothing has changed for us in engineering; we have the same co-workers, still using all Red Hat email / intranets / IT, etc., there's still a healthy promotions pipeline, all of that. I dont even know anyone from the IBM side. We had heard all the horror stories of other companies IBM acquired but for whatever reason, it's not been that way at all for us at least in the engineering group.
  - mroche 2y ago
    Former Hatter here (Solution Architect Q2 '21 -> Q4 '22). Other than the discussions that took place around moving the storage/business products and teams under IBM (and the recently announcement transfer of middleware), I wouldn't have expected engineering to do that much interfacing with IBM. At most, division leadership maybe (this is just personal speculation). Finance and Sales on the other hand... quite a bit more. We had a really fun time where the classic s-word was thrown around... "s y n e r g y". Some of the folks I got to meet across the aisle had a pretty strong pre-2010 mindset. Even around opinions of the acquisition, thinking it was just another case of SOP for the business and we'd be fully integrated Soon™. They key thing people need to remember about the Red Hat acquisition is that it was purely for expertise and personnel. Red Hat has no (or very little) IP. It's not like IBM was snatching them up to take advantage of patents or whatnot. It's in their best interest to do as little as possible to poke the bear that is RH engineering because if there was ever a large scale exodus, IBM would be holding the worlds largest $34B sack of excrement we've seen. All of the value in the acquisition is the engineering talent and customer relationships Red Hat has, not the products themselves. The power of open source development! It's heartening to hear that your experience in engineering has been positive (or neutral?) so far. Sales saw some massive churn because that's an area IBM did have a heavier impact in. There were some fairly ridiculous expectations set for year-over-year, completely dismissing previous results and obvious upcoming trends. Lost a lot of good reps over that...
chippiewill 2y ago
I worked with a bunch of people who had worked at a startup that got bought by IBM. As the other commenters attested, they too experienced that IBM is not the kind of company that's going to turn on the investment taps. There are worse companies to get bought by, but if you've only ever worked at startups then you're not likely to enjoy what this becomes.
- mistrial9 2y ago
  I spoke with a guy (too long ago) that was a "genius architect" and worked for a company that was small enough, that he got to implement his castles in the air. Knowing him, they might have been quite good, but it was one person that knew the details and made changes at the architect scale. He had a quirky way of thinking. When IBM acquired that company, after a few weeks, this guy had a meeting with new engineering people. The very first meeting, they changed things for him. Instead of a single winding road of development, they wrote out a large spreadsheet. The rows were the distinguishable parts of his large'ish and clever architecture; the columns were assignments. They essentially dismantled his world into parts, for a team to implement. He was distraught. He didn't think like that. They did not discuss it, it was the marching orders. He quit shortly afterwards, which might have been optimal for IBM.
  - kaushikt 2y ago
    If you are a good at your job and want to deliver fast then you need to adapt to changing circumstances and continue on. Nothing wrong if you can’t but I have learnt that’s how you play along to deliver your best continuously.
    - deleted 2y ago
      [deleted]
    - asimovfan 2y ago
      You mean perhaps if you define "your job" and "adapting to changing circumstances" strictly through a corporate vocabulary. One could argue that to deliver his best continuously he adapted to changing circumstances and left.
thisisnotauser 2y ago
I've had the incredible displeasure of having to maintain multiple massive legacy COTS systems that were once designed by promising startups and ultimately got bought by IBM. IBM turned every last one into the shittiest enterprise software trash you can imagine. Every IBM product I've ever used is universally reviled by every person I've met who also had to use it, without exaggeration in the slightest. If anything, I'm understating it: I make a significant premium on my salary because I'm one of the few people willing to put up with it. My only expectation here is that I'll finally start weaning myself off terraform, I guess.
- throwaway2037 2y ago
  How is Red Hat going after the acquisition by IBM? From my view, it is going well. The enterprise product (RHEL) is still excellent.
  - dralley 2y ago
    It's going basically fine. If you're in engineering you would never notice the difference.
    - sverhagen 2y ago
      Companies are often brought in and told that nothing will change, and as long as they can pull their weight, this may be true. IBM seems a pretty diversified company, and there RedHat doing 5% of the total revenue may not be too bad. I don't know how well RedHat is doing commercially, but a few bad quarters could draw negative attention of the sort where upper-management wants to start messing with you, seek more synergy, efficiency, alignment. Being a much smaller small company within Verizon, having been left alone for a little while, we were then told that The Hug was coming. It did. We didn't grow to be their next billion dollar business unit (as no surprise to anyone in our little company), nor were we able to complement other products (ha! synergy!) and we were shuttered. At some point... engineering will notice.
  - adastra22 2y ago
    Dropping CentOS was a terrible decision. I’m not sure if that happened before or after the acquisition though.
dramm 2y ago
I would GTFO, IBM ain't your friend and ain't your savior and are unlikely to invest and the worse may come with increasing IBM management sticking their fingers in the pie. The folks who did well out of this already know, they have the checks to cash if that was your take away congratulations. Otherwise find another opportunity. If nothing else look around and find out what you are worth on the market and then have that hard discussion soon with HashiCorp/IBM.
morkalork 2y ago
No matter how long you worked at the acquiree and instrumental you were, be prepared for your opinions to be overridden by IBM lifers because you're not "true blue" (ie. directly to IBM). Also prepare for the bluewashing!
superjared 2y ago
What a blessing to see your comment today. It's been a while. I hope this works in your favor, whatever that means.
- schmichael 2y ago
  <3
ddreier 2y ago
Fairly large Nomad Enterprise user here, and I just want to say thanks for all of the work you and the team put in. I'm a big fan of Nomad and really appreciate the opportunities it has afforded me. Regardless of the general sentiment, hoping for the best outcome for all of you.
- schmichael 2y ago
  Thanks for supporting us!
jonathanoliver 2y ago
We use Nomad where I work and we LOVE it. Previous to Nomad we used K8s for several years which, at that point, allowed us to become cloud agnostic. With the move to Nomad about 3+ years ago, we were able to transition away from cloud and back to leased, bare metal machines. During our time with K8s, it didn't have a good bare-metal strategy with their ingress mechanism. In contrast, as we investigated Nomad, it was easy to deploy on pure metal without a hypervisor. The result of our migration to Nomad was having so many capable and far-less-expensive hosting options. Lastly, as part of our Nomad control plane, we also adopted Vault and Consul with great success. I know there are horror stories around this acquisition and lots of predictions about what will happen, but only time will tell. On a minimum, it has been a delight to use the Hashicorp software stack along with the approach they brought to our engineering workflow (remember Vagrant?). These innovations and approaches aren't going away.
- schmichael 2y ago
  Glad to hear Nomad is working well for you! It always means a lot. We as the dev team spend all day staring at bugs and missing features, so it's nice to be reminded of what's working well! No one files an issue for a happy cluster. :)
- nunez 2y ago
  Lol at "remember Vagrant". I used it literally this year to create a test double of the NUC that runs my home automation stack. I also used Packer to configure Flatcar and create the qcow2 that Vagrant consumes. Vagrant is still the best tool for creating a general purpose VM on your machine. It got kind-of forgotten in the containers and Kubernetes hype, but it still gets the job done. Packer is also the best tool for creating VM images that got buried for the same reasons. The datacenter is coming back, though. IBM would be smart to invest in these tools as loss leaders to TFE and Vault and monetize the providers, IMO.
heipei 2y ago
I just wanted to say thank you for your work on Nomad. It's one of the most pleasant and useful pieces of software I have ever worked with. Nomad allowed us to build out a large fleet of servers with a small team while still enjoying the process.
- schmichael 2y ago
  > Nomad allowed us to build out a large fleet of servers with a small team I really love these stories. Our customers constantly shock me with how large of clusters they're able to manage with just a few people. >10k nodes by <10 people isn't uncommon although we are not good at rigorously collecting data on this. Nomad is far from perfect, but we really strive to ease the pains of managing your compute substrate.
Hrun0 2y ago
The Nomad team is a big reason why I am using it and I am sad to see you go.
- schmichael 2y ago
  > I am sad to see you go. I'm not going anywhere! My grammar isn't always the best, so I apologize for the confusion.
proxysna 2y ago
Just wanted to say thanks for your work on Nomad. Amazing tool that had me rethink a lot of things about how i work with infra and software in general and is always pleasant to work with by itself.
- schmichael 2y ago
  Thanks! I think this is a really insightful comment because Nomad is more opinionated than I think we let on. The subtle interactions between signals, service discovery, health checks, templates, etc. all have a big impact on the reliability of the system as a whole. I've always wanted to do a "HashiCorp Validated Nomad App Design" kind of doc to outline these best practices, but it's always proved too big of a lift. Maybe now is the time!
  - proxysna 2y ago
    As good of a time as ever. Feels like it would be a good read.
m1keil 2y ago
Hey on a personal note, dealing with you and your team on Nomad's GitHub issue tracker was always a good experience. I hope nomad still has a future under IBM's roof.
- schmichael 2y ago
  Thanks! We have kept an explicit community rotation and issue triage policy for Nomad's entire life. Definitely one of my hard lines. I know we aren't perfect. In fact it's my turn this week, and I've utterly failed at keeping up with triage!! We get tremendous joy and value from engaging with our community. Thanks for your patience (with me in particular!)
parasense 2y ago
I was at a certain open source company IBM acquired, and it was certainly an interesting experience. I certainly don't harbor any overtly negative feelings towards IBM. I used to have negative feelings about IBM many years ago, as a customer in my former life as a sysadmin, many decades ago. However being under the IBM umbrellas was alright. Yall are going to be fine!

linuxftw 2y ago

There are no resources and opportunities after being acquired by IBM. I worked for Red Hat when they were acquired. Our former CEO was quickly shown the door. We were making so much profit, almost a $1B in quarterly revenue. I left not long after the acquisition. Not long after I left, they laid off a bunch of staff. No matter what they tell you, your day to day will not improve. For my area, it was mostly business as usual, but a net decrease in comp because IBM's ESPP is trash.

deleted 2y ago
[deleted]
zzzeek 2y ago
if you left right after the acquisition how can you even speak to what the experience has been?
- linuxftw 2y ago
  It was within a year, not like the day after.
- worthless-trash 2y ago
  I have found the experience very different than what the OP's experience is. As you know the layoffs that happened were around the same time as the rest of the industry layoffs were happening (fashion firing), I don't feel like it had a significant effect on the culture. I am fully remote though, and have been for 15 years.
  - linuxftw 2y ago
    What part of my experience did you find different than your own? I said the day to day was mostly the same, minus the decrease in comp. I mostly was trying to articulate that the idea that IBM is going to 'super power' Hashicorp is not real, despite what IBM says. A lot of what was communicated during the acquisition process was how IBM was going to super power Red Hat and help Red Hat grow into an even larger entity, and how Red Hat actually need IBM to survive.
    - worthless-trash 2y ago
      > There are no resources and opportunities after being acquired by IBM. Got promoted twice, once between teams. Went to multiple countries and I was in product security (cost center ) at the time. > No matter what they tell you, your day to day will not improve. I am down to a 40 hour work week, down from 50-60. > Not long after I left, they laid off a bunch of staff. I don't see any difference, corporate has laid off many different groups, I guess the only different to the mothership laid off people in the US so it hits closer to your home. I've seen layoffs in Support in phillipines, Documentation in Brisbane, Most of Singapore GLS/GPS. The USA has always been insulated from the layoffs because execs find it harder to lay off people you meet in the corridors. > A lot of what was communicated during the > acquisition process was how IBM was going to super > power Red Hat and help Red Hat grow into an even > larger entity, and how Red Hat actually need IBM to > survive. Maybe this was in the US, most of the IBM briefing/cheerleading meetings were not held during the APAC timezone so I skipped them and prioritized high value work. I have always assumed that if I needed to know something my manager would tell me. If i was getting let go, nothing I could do about it if I was already doing the work I was supposed to be doing.

spicyusername 2y ago

Unfortunately IBM is going to ruin everything that was good about working for Hashicorp and eventually everything that was good about Hashicorp products. I worked for a company acquired by IBM, and we held hope like you are doing, but it was only a matter of time before the benefit cuts, layoffs, and death of the pre-existing culture. Your best bet is to quit right after the acquisition and hope they give you a big retention package to stay. These things are pretty common to ease acquisition transitions and the packages can be massive, easily six figures. Then when the package pays out you can leave for good.

zzzeek 2y ago
Red Hatter here. none of that has happened for us at Red Hat. Other than the one round of layoffs which occurred at the time that basically every tech company everywhere was doing much larger layoffs, that was pretty much it and there's no reason to think our layoffs wouldn't have been much greater at that time if we were not under the IBM umbrella. Besides that, I dont even remember when we were acquired, absolutely nothing has changed for us in engineering; we have the same co-workers, still using all Red Hat email / intranets / IT, etc., there's still a healthy promotions pipeline, all of that. I dont even know anyone from the IBM side. We had heard all the horror stories of other companies IBM acquired but for whatever reason, it's not been that way at all for us at least in the engineering group.
- mroche 2y ago
  Former Hatter here (Solution Architect Q2 '21 -> Q4 '22). Other than the discussions that took place around moving the storage/business products and teams under IBM (and the recently announcement transfer of middleware), I wouldn't have expected engineering to do that much interfacing with IBM. At most, division leadership maybe (this is just personal speculation). Finance and Sales on the other hand... quite a bit more. We had a really fun time where the classic s-word was thrown around... "s y n e r g y". Some of the folks I got to meet across the aisle had a pretty strong pre-2010 mindset. Even around opinions of the acquisition, thinking it was just another case of SOP for the business and we'd be fully integrated Soon™. They key thing people need to remember about the Red Hat acquisition is that it was purely for expertise and personnel. Red Hat has no (or very little) IP. It's not like IBM was snatching them up to take advantage of patents or whatnot. It's in their best interest to do as little as possible to poke the bear that is RH engineering because if there was ever a large scale exodus, IBM would be holding the worlds largest $34B sack of excrement we've seen. All of the value in the acquisition is the engineering talent and customer relationships Red Hat has, not the products themselves. The power of open source development! It's heartening to hear that your experience in engineering has been positive (or neutral?) so far. Sales saw some massive churn because that's an area IBM did have a heavier impact in. There were some fairly ridiculous expectations set for year-over-year, completely dismissing previous results and obvious upcoming trends. Lost a lot of good reps over that...

chippiewill 2y ago

I worked with a bunch of people who had worked at a startup that got bought by IBM. As the other commenters attested, they too experienced that IBM is not the kind of company that's going to turn on the investment taps. There are worse companies to get bought by, but if you've only ever worked at startups then you're not likely to enjoy what this becomes.

mistrial9 2y ago
I spoke with a guy (too long ago) that was a "genius architect" and worked for a company that was small enough, that he got to implement his castles in the air. Knowing him, they might have been quite good, but it was one person that knew the details and made changes at the architect scale. He had a quirky way of thinking. When IBM acquired that company, after a few weeks, this guy had a meeting with new engineering people. The very first meeting, they changed things for him. Instead of a single winding road of development, they wrote out a large spreadsheet. The rows were the distinguishable parts of his large'ish and clever architecture; the columns were assignments. They essentially dismantled his world into parts, for a team to implement. He was distraught. He didn't think like that. They did not discuss it, it was the marching orders. He quit shortly afterwards, which might have been optimal for IBM.
- kaushikt 2y ago
  If you are a good at your job and want to deliver fast then you need to adapt to changing circumstances and continue on. Nothing wrong if you can’t but I have learnt that’s how you play along to deliver your best continuously.
  - deleted 2y ago
    [deleted]
  - asimovfan 2y ago
    You mean perhaps if you define "your job" and "adapting to changing circumstances" strictly through a corporate vocabulary. One could argue that to deliver his best continuously he adapted to changing circumstances and left.

thisisnotauser 2y ago

I've had the incredible displeasure of having to maintain multiple massive legacy COTS systems that were once designed by promising startups and ultimately got bought by IBM. IBM turned every last one into the shittiest enterprise software trash you can imagine. Every IBM product I've ever used is universally reviled by every person I've met who also had to use it, without exaggeration in the slightest. If anything, I'm understating it: I make a significant premium on my salary because I'm one of the few people willing to put up with it. My only expectation here is that I'll finally start weaning myself off terraform, I guess.

throwaway2037 2y ago
How is Red Hat going after the acquisition by IBM? From my view, it is going well. The enterprise product (RHEL) is still excellent.
- dralley 2y ago
  It's going basically fine. If you're in engineering you would never notice the difference.
  - sverhagen 2y ago
    Companies are often brought in and told that nothing will change, and as long as they can pull their weight, this may be true. IBM seems a pretty diversified company, and there RedHat doing 5% of the total revenue may not be too bad. I don't know how well RedHat is doing commercially, but a few bad quarters could draw negative attention of the sort where upper-management wants to start messing with you, seek more synergy, efficiency, alignment. Being a much smaller small company within Verizon, having been left alone for a little while, we were then told that The Hug was coming. It did. We didn't grow to be their next billion dollar business unit (as no surprise to anyone in our little company), nor were we able to complement other products (ha! synergy!) and we were shuttered. At some point... engineering will notice.
- adastra22 2y ago
  Dropping CentOS was a terrible decision. I’m not sure if that happened before or after the acquisition though.

dramm 2y ago

I would GTFO, IBM ain't your friend and ain't your savior and are unlikely to invest and the worse may come with increasing IBM management sticking their fingers in the pie. The folks who did well out of this already know, they have the checks to cash if that was your take away congratulations. Otherwise find another opportunity. If nothing else look around and find out what you are worth on the market and then have that hard discussion soon with HashiCorp/IBM.

morkalork 2y ago

No matter how long you worked at the acquiree and instrumental you were, be prepared for your opinions to be overridden by IBM lifers because you're not "true blue" (ie. directly to IBM). Also prepare for the bluewashing!

superjared 2y ago

What a blessing to see your comment today. It's been a while. I hope this works in your favor, whatever that means.

schmichael 2y ago
<3

ddreier 2y ago

Fairly large Nomad Enterprise user here, and I just want to say thanks for all of the work you and the team put in. I'm a big fan of Nomad and really appreciate the opportunities it has afforded me. Regardless of the general sentiment, hoping for the best outcome for all of you.

schmichael 2y ago
Thanks for supporting us!

jonathanoliver 2y ago

We use Nomad where I work and we LOVE it. Previous to Nomad we used K8s for several years which, at that point, allowed us to become cloud agnostic. With the move to Nomad about 3+ years ago, we were able to transition away from cloud and back to leased, bare metal machines. During our time with K8s, it didn't have a good bare-metal strategy with their ingress mechanism. In contrast, as we investigated Nomad, it was easy to deploy on pure metal without a hypervisor. The result of our migration to Nomad was having so many capable and far-less-expensive hosting options. Lastly, as part of our Nomad control plane, we also adopted Vault and Consul with great success. I know there are horror stories around this acquisition and lots of predictions about what will happen, but only time will tell. On a minimum, it has been a delight to use the Hashicorp software stack along with the approach they brought to our engineering workflow (remember Vagrant?). These innovations and approaches aren't going away.

schmichael 2y ago
Glad to hear Nomad is working well for you! It always means a lot. We as the dev team spend all day staring at bugs and missing features, so it's nice to be reminded of what's working well! No one files an issue for a happy cluster. :)
nunez 2y ago
Lol at "remember Vagrant". I used it literally this year to create a test double of the NUC that runs my home automation stack. I also used Packer to configure Flatcar and create the qcow2 that Vagrant consumes. Vagrant is still the best tool for creating a general purpose VM on your machine. It got kind-of forgotten in the containers and Kubernetes hype, but it still gets the job done. Packer is also the best tool for creating VM images that got buried for the same reasons. The datacenter is coming back, though. IBM would be smart to invest in these tools as loss leaders to TFE and Vault and monetize the providers, IMO.

heipei 2y ago

I just wanted to say thank you for your work on Nomad. It's one of the most pleasant and useful pieces of software I have ever worked with. Nomad allowed us to build out a large fleet of servers with a small team while still enjoying the process.

schmichael 2y ago
> Nomad allowed us to build out a large fleet of servers with a small team I really love these stories. Our customers constantly shock me with how large of clusters they're able to manage with just a few people. >10k nodes by <10 people isn't uncommon although we are not good at rigorously collecting data on this. Nomad is far from perfect, but we really strive to ease the pains of managing your compute substrate.

Hrun0 2y ago

The Nomad team is a big reason why I am using it and I am sad to see you go.

schmichael 2y ago
> I am sad to see you go. I'm not going anywhere! My grammar isn't always the best, so I apologize for the confusion.

proxysna 2y ago

Just wanted to say thanks for your work on Nomad. Amazing tool that had me rethink a lot of things about how i work with infra and software in general and is always pleasant to work with by itself.

schmichael 2y ago
Thanks! I think this is a really insightful comment because Nomad is more opinionated than I think we let on. The subtle interactions between signals, service discovery, health checks, templates, etc. all have a big impact on the reliability of the system as a whole. I've always wanted to do a "HashiCorp Validated Nomad App Design" kind of doc to outline these best practices, but it's always proved too big of a lift. Maybe now is the time!
- proxysna 2y ago
  As good of a time as ever. Feels like it would be a good read.

m1keil 2y ago

Hey on a personal note, dealing with you and your team on Nomad's GitHub issue tracker was always a good experience. I hope nomad still has a future under IBM's roof.

schmichael 2y ago
Thanks! We have kept an explicit community rotation and issue triage policy for Nomad's entire life. Definitely one of my hard lines. I know we aren't perfect. In fact it's my turn this week, and I've utterly failed at keeping up with triage!! We get tremendous joy and value from engaging with our community. Thanks for your patience (with me in particular!)

parasense 2y ago

I was at a certain open source company IBM acquired, and it was certainly an interesting experience. I certainly don't harbor any overtly negative feelings towards IBM. I used to have negative feelings about IBM many years ago, as a customer in my former life as a sysadmin, many decades ago. However being under the IBM umbrellas was alright. Yall are going to be fine!