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…
I don't think good tools are necessarily easy to approach. Some of the best tools I know have quite a steep learning curve. A good tool is one that gives you power. It makes difficult and complicated tasks easy and simple. It may come with the cost of getting good with using the tool, but once you master it, you don't know how you lived without it.
The Return of Fancy Tools
71–80 of 224 posts
Re: The Return of Fancy Tools
#72First, 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…
There's probably a crowd of people that want to move on to the next issue tracker flavour and that's fine but I've got work to do that isn't tool shuffling.
I'll use the one that integrates with so many of our systems and, though flawed, does a great job.
Re: The Return of Fancy Tools
#73It's basically cause of mobile. Simple tools often involve using files. Using plain text files too. I don't think the pendulum will swing back the same. Files are a bad abstraction. Databases via HTTP APIs are far more reliable for using between all our devices. Syncing files without something like Git is very painful and for Git to be used the user themselves need to be able to handle the diff themselves correctly.…
Files are a great abstraction. They give you ownership, actual one, not the kind sold by apple or Netflix. Files give you freedom to share informatiin instead of being held in a database by some third party with different intentions than your freedoms. Please don't spread FUD
I personally hold the view that it could have been better and that a more general notion of persistent object (not in the OOP sense) would've been better from a user facing pov.
The filesystem is doing more than one job, holding multiple responsibilities and imposing a way to present data and how to store it.
Re: The Return of Fancy Tools
#74First, 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…
Re: The Return of Fancy Tools
#75Re: The Return of Fancy Tools
#76Earlier quoted context omitted.
I mean, it’s all very opinionated. I think at this point I am borderline “I would rather have no bug tracker than Jira.” Issues isn’t perfect but it’s the best I’ve ever used.
I have never used Jira, could you say more about your feelings towards it? Currently we use an old in-house solution and are thinking of shifting.
Re: The Return of Fancy Tools
#77Good 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…
I don't think good tools are necessarily easy to approach. Some of the best tools I know have quite a steep learning curve. A good tool is one that gives you power. It makes difficult and complicated tasks easy and simple. It may come with the cost of getting good with using the tool, but once you master it, you don't know how you lived without it.
Re: The Return of Fancy Tools
#78Earlier quoted context omitted.
I have never used Jira, could you say more about your feelings towards it? Currently we use an old in-house solution and are thinking of shifting.
Jira is very sensitive to the configuration you build for it, and the hardware it is running on. The full configuration for Jira would make an Encyclopedia look small. Get that wrong (as many places do), and it is hard to use and dead-dog slow, at the best of times. But if you have a real Jira wizard who can configure things correctly, then it can easily be the fastest and easiest way to organize your development and…
Re: The Return of Fancy Tools
#79First, 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…
Right. The idea that Jira has been replaced made me laugh. There's probably a crowd of people that want to move on to the next issue tracker flavour and that's fine but I've got work to do that isn't tool shuffling. I'll use the one that integrates with so many of our systems and, though flawed, does a great job.
It's not just issue tracking, but alerting, issue management ITSM tools, source control, CI/CD, release management, documentation and I don't know what else that all need talk to each other and provide traceability from any point to another. You can do the integration yourself, but it's a gigantic PITA, and as the number of tools rises, the number of integrations you need to set up is going to rise terrifyingly fast.
I have a litany of complaints about the Atlassian suite, but none of the competitors have even have the services we need.
Re: The Return of Fancy Tools
#80Earlier quoted context omitted.
Right. The idea that Jira has been replaced made me laugh. There's probably a crowd of people that want to move on to the next issue tracker flavour and that's fine but I've got work to do that isn't tool shuffling. I'll use the one that integrates with so many of our systems and, though flawed, does a great job.
That integration piece is key. The people who want to replace Atlassian tools usually focus one part of the suite (usually Jira or Confluence), but to replace them you all you need a set of tools that work together. It's not just issue tracking, but alerting, issue management ITSM tools, source control, CI/CD, release management, documentation and I don't know what else that all need talk to each other and provide tr…
You are right that it's difficult to replace the entire Atlassian suite. The thing about Atlassian is that when there's if there's a box to check on a feature list, they've made sure to check it. If you go around the office asking everyone what features they want, Atlassian is going to check all those boxes. That's pretty hard to compete with.