Thoughtworks Technology Radar Vol. 17 [pdf] | Hacker News Reader

Thoughtworks Technology Radar Vol. 17 [pdf]

assets.thoughtworks.com

66 pointspagade18 comments

The web version is pretty decent - https://www.thoughtworks.com/radar

PDF can be a pain to work with on some devices.

I'm curious what Roy Singham's plans are for the windfall he got from selling Thoughtworks to Apax back in August. HN discussion at the time: https://news.ycombinator.com/item?id=15082116

Guess it hasn't been that long, but that's a lot of capital.

I think this is a great resource (seriously, thanks ThoughtWorks!), but do you really need to tell me that “antipatterns” or things that are “over-ambitious” are in the bad category? It would be more helpful to give things neutral names.

I think they described it properly. They are specifically talking about a bunch of bad practices with Kafka. So the issue is that people are actually using anti patterns in a new technology that were previously identified for ESB.

Assess Angular, but no mention of React?

It was on there previously

It's in "Adopt" and they say it's their "default choice" for FE frameworks [1]. Also, the "Trial" details for Angular mention "Most of our teams, however, still prefer React, Vue or Ember over Angular."

If a technology is consistently listed in a section, they remove it from the radar, which is mostly focused on changing trends.

[1]: https://www.thoughtworks.com/radar/languages-and-frameworks/...

Things that consultancies like == things that people valuing maintainable solutions should avoid

That's a generalized and somewhat bigoted opinion.

That's an odd use of the word bigoted.

Bigoted simply means prejudicial without a valid reason.

Depends on the consultancy. ThoughtWorks is pretty useful as a data point.

I started the Selenium project at ThoughtWorks, fwiw. That could be used as a data point for whatever conclusion you want to make. :)

I agree, ThoughtWorks tends to make generally sound technical decisions. Years ago, I worked on a team that was 90% TW people, and learned a LOT of techniques and tools I still use to this day. Their senior devs are unusually active in mentoring.

It is more profitable to have a healthy relationship with your client than building a shitty product and hoping you'll never run out of clients.

What makes you think that about consultancies?

At my last consulting agency we were frequently more concerned with sustainability than our clients were. Fact is, that sustainability is not a "down the road" issue. It can start rearing it's ugly head within months or weeks of starting a new project. If you have a long-term relationship with a client, it's even more important.

Might be more accurate to call out "Things that Thoughtworks like". Not all consultancies or organizations work this way.

Still, handy to know what is being sold so our contractor CVs can be tailored.

You can adopt Mashape/Kong API Gateway now. Apple have been using it for years. The same goes for Apache Mesos/Marathon, which is what they use to run Siri.

Reply on news.ycombinator.com