Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

IBM completes acquisition of HashiCorp

newsroom.ibm.com

Post reply on HN
Print view View original

291–300 of 407 posts

Re: IBM completes acquisition of HashiCorp

#291

Post by oso2k »

dralley wrote: post #194
cpitman wrote: post #185

Earlier quoted context omitted.

Every time you say rocket chat, I have to appear. FWIW, the change at Red Hat has always been hard to separate between the forces of IBM and the reality of changing leadership. In a lot of ways those are intertwined because some of the new leadership came from IBM. Whatever change there was happened relatively gradually over many years.

Paul Cormier was a very different type of CEO than Jim Whitehurst for sure. But that's not an IBM thing, he was with Red Hat for 20 years previously. I agree with you FWIW. The company also basically doubled in size from 2019 to 2023. It's very hard to grow like that and experience zero changes. And COVID happened shortly after so that also throws a wrench into the comparisons. The point is, it's hard to point to any…

I do miss having Jim Whitehurst around. Jim spent 90 minutes on the Wednesday afternoon of my New Hire Orientation week with my cohort helping to make sure all of us could login to email and chat, answering questions, telling a couple short stories. He literally helped build the Red Hat culture starting at New Hire. Kind of magical when the company is an 11K person global business and doing 5B in revenue.

Cormier and Hicks have their strengths. Hicks in particular seems to care about cultural shifts and also seems adept at identifying key times and places to invest in engineering efforts.

The folks we have imported from IBM are hiring folks that are attempting to make Red Hat more aggressive, efficient, innovative. Some bets are paying off. More are to be decided soon. These kinds of bets and changes haven’t been for everyone.

Re: IBM completes acquisition of HashiCorp

#292

Post by heywire »

avhception wrote: post #238
zifpanachr23 wrote: post #201

Earlier quoted context omitted.

The green screens tend to be much quicker and more responsive than the web frontends that are developed to replace them. I've seen a lot of failed projects for data entry apps because the experienced workers tend to prefer the terminals over the web apps. Usually the requirement for the new frontend is driven by management rather than the workers. Which is understandable to me as a programmer. If it's a task that I'm…

I second the TUI argument here. Back in ... maybe 2005 or what, in our ~60 people family business, I had the pleasure to watch an accountant use our bespoke payroll system. That was a DOS-based app, running on an old Pentium 1 system. She was absolutely flying through the TUI. F2, type some numbers, Enter, F5 and so on and so on, at an absolutely blistering speed. Data entry took single-digit seconds. When that was c…

I was at a ticket window buying concert tickets a couple weeks ago and was surprised to see the worker using the Ticketmaster TUI / Mainframe interface. She flew through the screens. The same experience on the Ticketmaster website is awful.

Re: IBM completes acquisition of HashiCorp

#293

Post by Foobar8568 »

swarnie wrote: post #256
nayuki wrote: post #196

Earlier quoted context omitted.

> Every IBM product I've ever used is universally reviled by every person I've met who also had to use it During my time at IBM and at other companies a decade ago, I can name examples of this: * Lotus Notes instead of Microsoft Office. * Lotus Sametime Connect instead of... well Microsoft's instant messengers suck (MSN, Lync, Skype, Teams)... maybe Slack is one of the few tolerable ones? * Rational Team Concert inst…

Can we add DOORS to this list please? I have no idea how/why IBM of all places developed or sold this software but it badly needs to die in a fire. Database technology which would seem outdated in 1994 with a UI and admin management tools to match.

DOORS is/was a requirement management tool and frankly speaking was crap but I have never seen another software as good and comprehensive in requirement management.

I expect it to be still used in aviation or army related domain, maybe pharma.

Re: IBM completes acquisition of HashiCorp

#294

Post by ghaff »

throwaway2037 wrote: post #146
subpixel wrote: post #103

Earlier quoted context omitted.

Broadly independent but filled to the gills with folks who spent a decade or more at IBM before landing at Red Hat. While this has been true of rank and file for years, recently it’s true on the c-suite.

> filled to the gills with folks who spent a decade or more at IBM before landing at Red Hat Was this true before the acquisition?

Was probably truer of middleware than other areas. (Which I gather is largely going over to IBM.) Linux had a very significant DEC legacy. OpenShift was essentially greenfield from a startup acquisition (that got totally rewritten for Kubernetes anyway) and I'm not sure I would characterize people in that area as broadly coming from any particular large vendor.

Re: IBM completes acquisition of HashiCorp

#296

Post by steveBK123 »

In some ways to me it feels like a turning point for the GFC/ZIRP thru COVID era of tech companies with no path to profit.

After the haze of the LLM bubble passes, I hope startups have an exit strategy other than "we'll just get 0.01% of users to pay 6+ figures for support" or "ads".

Good tech deserves a good business model such that it can endure for the long term.

Re: IBM completes acquisition of HashiCorp

#297

Post by gryfft »

dralley wrote: post #119
gryfft wrote: post #114

Earlier quoted context omitted.

Give it time.

It's been almost 6 years

IBM acquired SoftLayer in 2013 and the bluewashing didn't reach a fever pitch until 2019 or so. Also, the pandemic slowed things down at an already dinosauric company. IBM is over a hundred years old. I have faith that it will get around to entirely ruining Red Hat sooner than later.

Re: IBM completes acquisition of HashiCorp

#298

Post by sudomateo »

I learned many things at HashiCorp but none as important as choosing ISOs over RSUs when given the chance. Thank you for the gains $HCP.

I met some great people along the way that I'm glad to have gotten the opportunity to work with. Godspeed all!

Re: IBM completes acquisition of HashiCorp

#299

Post by jsk2600 »

lenkite wrote: post #245
avhception wrote: post #238

Earlier quoted context omitted.

I second the TUI argument here. Back in ... maybe 2005 or what, in our ~60 people family business, I had the pleasure to watch an accountant use our bespoke payroll system. That was a DOS-based app, running on an old Pentium 1 system. She was absolutely flying through the TUI. F2, type some numbers, Enter, F5 and so on and so on, at an absolutely blistering speed. Data entry took single-digit seconds. When that was c…

Things have changed back though - the CLI is hot again at-least amongst developers.

I find it ironic that we developers prefer to use CLI because it's quick, efficient, stable, etc., but what we then deliver to people as web apps is quite the opposite experience.

Re: IBM completes acquisition of HashiCorp

#300

Post by regularfry »

anonfordays wrote: post #200
dpkirchner wrote: post #190

Earlier quoted context omitted.

I'm not familiar with every lifecycle argument but I don't know of any that prevent resources being destroyed if they are removed from the tf file (what the parent was talking about). prevent_destroy, per docs, only applies as long as the resource is defined. I think the only way to avoid accidentally destroying a resource is to refer to it somewhere else, like in a depends_on array. At least that would block the pla…

>I don't know of any that prevent resources being destroyed if they are removed from the tf file (what the parent was talking about). Azure Locks (which you can also manage with Terraform), Open Policy Agent, Sentinel rules, etc. will prevent a destroy even if you remove the definition from your Terraform codebase. Again, if you're not operationally mature enough, the problem isn't the tool, it's you.

"Operationally mature" is code here for "the gun starts out loaded and pointed at your foot". It's fine to point out that that's a suboptimal design for a tool.
Post reply on HN