Live data from Hacker News

My 20 year career is technical debt or deprecated

blog.visionarycto.com

231–240 of 585 posts

Re: My 20 year career is technical debt or deprecated

#231

Earlier quoted context omitted.

Do people who loves JIRA exist for real?

What's not to love? Infinitely configurable and extensible system that can accommodate any workflow and any process that comes to mind. It can be used and also misused, but blaming Jira for its misuse is like blaming Lisp because it's too flexible and too powerful.

Indeed. Blaming Jira because it's missing this or that feature, or because the managed version is being slow is fine. Blaming it because it's an implementation of the twisted processes of your organization it is not (and that's what most people usually do, even if unknowingly)

Re: My 20 year career is technical debt or deprecated

#232

Earlier quoted context omitted.

Do people who loves JIRA exist for real?

What's not to love? Infinitely configurable and extensible system that can accommodate any workflow and any process that comes to mind. It can be used and also misused, but blaming Jira for its misuse is like blaming Lisp because it's too flexible and too powerful.

That's exactly the problem, we need a JIRA that is quick, efficient and not a death trap of a corvette for a 16yr old mental adult. Pretty please....

Re: My 20 year career is technical debt or deprecated

#233

I think it's normal. Some systems I've built were quite sticky in the sense that they started as prototypes to be scrapped once we figure out the "real" system architecture, and 8 years later they're still in use and integrated into dozens of business processes, so hard to replace. In general, looking back at old code I wrote it seems my solutions were better when I was more naive / less experienced, as I would often…

I've taken the opposite lesson to you, I now keep everything super simple and am quite conservative on adopting new concepts. It's because I've so often seen the cycle here of "X is brilliant" and then 2 years later "how we switched off X and saved millions of manhours!".

So, the same lesson

Re: My 20 year career is technical debt or deprecated

#234

Earlier quoted context omitted.

People don't hate Jira because it's written in Java. They don't know or comprehend that something like Jira or Confluence or Minecraft can be written in Java.

Jira does, somehow, faintly smell of Java. There's just something about how slow it is, and how maximalist it is in supporting every whimsical idea that any rich corporate customer has ever asked of them. No matter how poorly the request blended with everything else Jira does. Mind you, I've only ever used Jira when its been setup, poorly, to fit in to a badly designed "scrum" process. People say it can be usable if…

jira's slow because it's a badly written piece of crap

requiring 20mb of data transfer for each page load isn't java's fault

Re: My 20 year career is technical debt or deprecated

#235
post #230

Earlier quoted context omitted.

> And most devs hating on Java are using an IDE written mainly in Java (all the JetBrains ones): the irony of that one gives me the giggles. Guilty as charged! I hate using Java because everything written in java seems to blend into the same indistinguishable swamp of classes with meaningless names, full of methods that constantly find new and interesting ways to obscure what your program is actually trying to do. De…

I feel like if Java had immutability by default it would be such a better language to work with. It is so hard to determine what actually gets modified where in a large Java codebase.

Too bad immutability breaks the quite-ubiquitous-in-JVM-land Bean spec (and I wonder what one was smoking before drawing that spec).

I think having proper sum-types with pattern matching would have also made it a much better language.

Re: My 20 year career is technical debt or deprecated

#236
post #50
post #32

Earlier quoted context omitted.

See as someone who knows Rust fairly well. let &mut -- Essential keywords. writer = -- Duh Writer -- Generic types. Important. ::writer::new -- Boilerplate. (connection.clone()).clone; -- Relentless cloning is a big problem. ... .unwrap -- "Consistent names for optional types," is an issue in Rust. Every module has different jargon for Some(x). Rust certainly isn't perfect. The borrow checker creates... awkwardness,…

I feel like those clones don't get enough attention. At a glance, you don't really know what those clones are doing. Is it allocating, is just increasing reference counter? Makes code hard to understand

clone() makes an immutable, deep copy/recursive copy of the original data structure.

clone() itself makes perfect sense. Why the programmer needed those clones... is a legitimate issue with Rust.

In my experience so far, it's usually to hack around an interaction between the borrow checker and the output of a function constructed using dot syntax.

Re: My 20 year career is technical debt or deprecated

#237
The lessons I've learned from all my programming projects are:

1. If the codebase would still work on a "dead platform", but you are targeting something new, you are chasing after hype, to some degree.

2. If the code involves significant data entry, you probably want to leverage a spreadsheet, because eventually you will want to edit something tabular and also make charts and reports. The things "dashboards" do are also very reasonable to do from inside a spreadsheet - make a tiny shim to pipe in some data, and then make the dashboard frontend using all the built-in goodies.

3. If the code is mostly about making custom UI, you are on the path to saleable application software, or at minimum, a tech demo that people will talk about.

Re: My 20 year career is technical debt or deprecated

#238
I write a project using primarily a foss stack which has a 20+ year history of being committed to backwards compatibility, and I couldn't be happier.

Utilizing the Lindy Effect to my benefit, I've been able to almost entirely avoid the typical framework frustrations, such as breaking changes and abandoned dependencies.

Instead, I've been able to focus on features, figure out a good code style, and support nearly all mainstream or once-mainstream browsers. On the back-end, I'm working on the Windows install process, but on *nix it's fairly uniform across different flavors and lineages.

For those curious, it is Perl, text files, PGP, HTML, CSS, low-sugar JS, and a little bit of sh, Python and PHP for server glue. Now probably to include batch files...

Re: My 20 year career is technical debt or deprecated

#240

> My entire career is now technical debt, or the code has been deprecated. My fellow dev often laugh when I tell them that instead of looking at all the long dead techs that are not useful to me anymore, my way to feel good is to look back at all the long dead techs that I didn't bother to learn . And, geez, is the graveyard huge. > Java Applets were also a big thing once upon a time. They were slow, and having the c…

> And most devs hating on Java are using an IDE written mainly in Java (all the JetBrains ones): the irony of that one gives me the giggles. Guilty as charged! I hate using Java because everything written in java seems to blend into the same indistinguishable swamp of classes with meaningless names, full of methods that constantly find new and interesting ways to obscure what your program is actually trying to do. De…

"Anyone who writes class names like FactoryBuilderFactoryImpl and claims to walk in the light is at best a scoundrel, and at worst a follower of a religion so dark we don't name it in polite company."

Awesome quote ... LOL.

Post reply on HN