71–77 of 77 posts
Earlier quoted context omitted.
Out of curiosity: What was the old language and what was its replacement?
old = ruby (rails). New = Java.
Earlier quoted context omitted.
Out of curiosity: What was the old language and what was its replacement?
old = ruby (rails). New = Java.
FWIW, he was fired after about 18 months on the job (for reasons unknown to me).
I know of a company that was pretty successful with a VB6 app they wrote in the late 90s, but twenty years later they needed to modernize. They spent two years on a from scratch rewrite that was never completed (second system syndrome). The company abandoned the rewrite, acquired a competitor, and rebranded it as the company's new product. It turns out the competitor's code base had serious deficiencies (couldn't sca…
Wow, that’s doomed to fail hard.
Where I work at, we’re slowly rewriting a legacy Perl code base to Go HTTP services, and the best decision we made was to allow interoperability between the two systems. This way we can migrate the legacy parts by parts with minimal impact. This is a slow process (in 5 years we migrated maybe 3/4 of the code) but very reliable. And we actually have something to show for it.
In the early 2000's the consulting firm I worked for got a customer who was building a "revolutionary" (their words) new medical software suite. They were having difficulties shipping the product so we were hired to help. Turns out they were insanely paranoid about IP theft, so they had 20-30 programmers working on the code, each had zero access to any other programmer's slice (i.e. source code) of the app, only bein…
IMO Healthcare technology is the final boss of bad software orgs, and is the source of all ten of the top ten worst tech decisions I've ever seen.
My guess is that the software is so boring that it attracts weak engineers. But the complexity is really high due to the regulations. So in the end it’s a bad mix.
Earlier quoted context omitted.
old = ruby (rails). New = Java.
As a ruby dev this completely makes sense to me based on the Java developers I have worked with. I'm willing to bet he also never even considered jRuby as a happy compromise, also basing this on my experiences with the Java developers I have worked with
Not sure if it will sink the company, but moving from very good native apps to a single pwa/electron style app that was poorly written. The business justification seemly makes sense to have a single development train. But the execution was horrible. Bugs, horrible performance. Inconsistent features copied over from the various native apps, etc. It was released as a major upgrade, but it was almost alpha grade in real…
Apple seems to have jumped the ship successfully by switching to ARM, their keyboard and OS are still unusable though. Wonder how their China adventure will turn out.
Intel could be bought by Nvidia or AMD, but since the government invested so much into their backdoors there, they will be kept alive. But no chance that their architectural problems can be solved at all.
Boing is unfixable since its unfriendly McDonald-Douglas management takeover and technical decline since. Now even their stable flagship product line fell down in a straight line.