Live data from Hacker News

The Return of Fancy Tools

macwright.com

211–220 of 224 posts

Re: The Return of Fancy Tools

#211
post #97

Earlier quoted context omitted.

I got my start on Drumbeat which later was purchased by macromedia. I miss my spinning 3D text gifs.

Indeed, I still have one backend in production built back then with Drumbeat. Its UI was very new and rebuilt/consulted with Alan Cooper of Thunder/Visual Basic/About Face fame.

Interesting. I remember Alan Cooper. He wore a beret type hat.

Re: The Return of Fancy Tools

#212

Earlier quoted context omitted.

Even if that clause is enforceable, you can just tell people about it instead. No company would try to prevent talk about their products' good performance.

Actually, I’m obviously not talking about Jira but imagine some made an issue tracker in cloud mode and programmed it using microservices, the speed of each microservice would vary a lot depending on workload, time of the day, location, time since last access of the document/attachment/screen/userdata, configuration of the instance, importance of this customer (maybe I would give privileged speed to a good customer,…

Not that I disagree, although I feel the problem here is that this clause then can apply to all types of softwares. And even hardwares too. Just think if tomorrow Apple says that you cannot talk about degradation in performance in iPhones (because battery capacity reduces over time or something). We both know this, like we know that a user's experience will differ from the other. A company shouldn’t be adding a clause to prevent talking about this, it sounds like a malpractice to me. (I know it’s not that serious but still…)

Re: The Return of Fancy Tools

#213

Earlier quoted context omitted.

> I've got work to do that isn't tool shuffling. Is most of that work waiting for Jira to respond to your action so you can take the next action? I don't know if it's possible to have an adequately fast installation of Jira (since I've never seen one in a decade of Jira use at various places), but I do notice that people who have to put a lot of things into Jira seem to mostly use text editors or word processors to a…

> I don't know if it's possible to have an adequately fast installation of Jira That's not my experience of Jira. The cloud version is the best, and our current on-prem installation is perfectly fine. I agree that Jira isn't the snappiest tool to use, but I don't sit there consciously waiting for it to do stuff.

I use Jira a lot. Waiting three seconds per action makes me think that interfaces based on old-timey mainframes were probably faster.

Re: The Return of Fancy Tools

#214

First, this is an interesting take, and I think there is some kernels to consider in it. However, the author is painting very broadly with a large brush and smudging a lot. I have been happily using PyCharm/IntelliJ since what feels like the dawn of time. It is a perfectly complex and rewarding Fancy Tool. People still use IDEs for C/C++ this whole time, etc. I think the author is taking their personal journey and ex…

Jira still for the complex stuff, with many teams in enterprises. But maybe less than it was in simple projects, with one-to-one relationships between issues tracking and repository?

It works well for simple stuff too. You can just _not implement_ a complicated workflow.

Re: The Return of Fancy Tools

#215
post #2

Good games should be easy to approach and difficult to master . Good tools should be easy to approach with the ability to customize and do more advanced actions, but never difficult Good tools and products encapsulate complexity but still allow access to it where needed. Good tools aim to simplify complexity, not complexify simplicity. Good engineers and product people make tools that aim to simplify. Make it approac…

"Good tools aim to simplify complexity, not complexify simplicity." Some people don't realise that this is a goal, or that it's even possible. At Microsoft, this was the philosophy behind the .NET Framework standard library. It is simple, beautiful, and abstracts away reams of complex boilerplate that was necessary with C++ programming. Now? I'm using Azure, and... oh... my god. Every internal piece of wiring is expo…

> Every internal piece of wiring is exposed, raw, to the end-user. Wear insulating gloves.

I'm stealing this one. Hope you don't mind.

Re: The Return of Fancy Tools

#216

Earlier quoted context omitted.

They probably meant seconds. A website that takes seconds to open is unusable.

I wish I was mistaken, but I do literally mean minutes. I've measured it with a stopwatch before.

Your internet or Jira server is at fault. I've worked in some places that had really dystopian Jira installations, but never seen stuff quite that bad.

Re: The Return of Fancy Tools

#217

> JIRA was replaced by GitHub issues This is absolutely... not the case. Sure, for some kinds of projects Github Issues might do, but for anything "real" Github's issue and project management is a serious regression. --- These tools are not replacing anything, but addressing broader and broader markets. They lower the barrier to entry and bring more people into the fold (perhaps at the expense at having a lower ceili…

Github issues work well for simple needs and for issues that don't cross the boundaries of a single repo/don't refer to non-code activities. If even one of those is violated, you're much better off with Jira.

Re: The Return of Fancy Tools

#218
post #151
post #121

Earlier quoted context omitted.

You should really probably give Jetbrains' IDEs a try, if you use any of the languages they support. I find it hard to think I'd give PyCharm up for my daily Python and Typescript.

I tried PyCharm for a couple of months. It has some nice features, but they fall apart way too often. A sibling comment mentions Java, and maybe a more statically typed language does work better, but for Python the dynamic nature of the language makes “more primitive” code manipulation tools like PyCharm fail eventually.

What do you mean with "they fall apart way too often"?

Re: The Return of Fancy Tools

#219

Earlier quoted context omitted.

I hate that I agree with this but... I soured on Jira because my first experience with it was a horrible Rube Goldberg configuration on a self hosted instance. Years passed, I tried a bunch of different ways to use GH Issues as a primary tracking tool. It works but it’s... blah. It’s a good outward facing tool, it’s not good for tracking internal work. Because there’s no organizing principle. My last job forced me to…

> The only thing I couldn’t sort out to make it habitable: I really wanted to disable the “sprint” concept and have a single board without gymnastics. I don’t know if that’s just baked in or something the company configured. FWIW: We have sprints in JIRA at work -- but at my previous job we didn't. I doubt they've been added to the product in the couple of years since I left my previous employment, so I'll guess it w…

We must have missed each other on passing trains. My experience was that sprints are not just built in but required. I set up my last project with a catch all “active” sprint that never ends, and a catch-all “later” sprint that also doesn’t end for stuff that’s not being actively worked on or considered.

Re: The Return of Fancy Tools

#220

Earlier quoted context omitted.

> The only thing I couldn’t sort out to make it habitable: I really wanted to disable the “sprint” concept and have a single board without gymnastics. I don’t know if that’s just baked in or something the company configured. FWIW: We have sprints in JIRA at work -- but at my previous job we didn't. I doubt they've been added to the product in the couple of years since I left my previous employment, so I'll guess it w…

We must have missed each other on passing trains. My experience was that sprints are not just built in but required. I set up my last project with a catch all “active” sprint that never ends, and a catch-all “later” sprint that also doesn’t end for stuff that’s not being actively worked on or considered.

Hm... Maybe that's what we had at my old job too, then. Perhaps someone had set all that up before the rest of us in the team ever got to see it, so we never noticed.

Has the "Sprint" link always been on the bottom of the rightmost column?

Post reply on HN