4 ms·

Seconded. I dislike a forced-subscription model, but I'm definitely onboard with this type of hybrid model. Often times I go between jobs where a particular pi

by ajford 6y ago

Seconded. I dislike a forced-subscription model, but I'm definitely onboard with this type of hybrid model. Often times I go between jobs where a particular piece of software is no longer relevant to me, such as perhaps DataGrip from JetBrains. I occasionally have use for it again, but in general I'm no longer interacting with a rdbms anymore in my current role. Thanks to the hybrid subscription model, I can stop paying for the tool but keep my last 'lifetime' version as long as I care to use it. And if I pick up a job in the future that makes heavy use of it, I can re-evaluate whether it's worth subscribing for another term to get updates. In the same vain, I have an active sub for PyCharm (also from JetBrains) because as a Python dev, it makes a lot of sense for me to keep up with the new features as they continue to provide increasing value.

iruoy 6y ago
The Jetbrains IDEs all have a database explorer built in. Which is handy for (local) databases related to your project. If you write SQL directly in your app it'll even highlight and autosuggest according to your actual database.
- ajford 6y ago
  Yup. And they're tremendously useful (and the reason I don't normally need a db workbench tool). However, at a past employer, I inherited an absolutely awful CMS/fulfillment system/CRM hybrid that was bad at all parts of it's purpose. It proved to be dramatically more efficient to have a full blown DB tool just dedicated to exploring and interfacing with that monstrosity's database and have my regular PyCharm instance for code dev and light touches against the DB. Additionally, at another time it proved nearly impossible to get the IDE db explorer to work properly with the jdbc drivers for a couple of large-scale hosted data lakes, but was rather straightforward in DataGrip. I have no clue why it was an issue with the explorer in PyCharm, but since I got it working in DataGrip I rather quickly moved on and accepted that I was gonna use DataGrip for the data lakes. That said, I definitely love the db explorer feature, and recommend everyone take a look at it if you're already using a JetBrains product. Also, just another shout-out to JetBrains again for their hybrid subscription/lifetime ownership license approach, demonstrating that paid software can exist in the realm of linux systems and that you can make a successful company without resorting to bleeding your customers dry over subscription fees.

by ajford 6y ago

iruoy 6y ago

The Jetbrains IDEs all have a database explorer built in. Which is handy for (local) databases related to your project. If you write SQL directly in your app it'll even highlight and autosuggest according to your actual database.

ajford 6y ago
Yup. And they're tremendously useful (and the reason I don't normally need a db workbench tool). However, at a past employer, I inherited an absolutely awful CMS/fulfillment system/CRM hybrid that was bad at all parts of it's purpose. It proved to be dramatically more efficient to have a full blown DB tool just dedicated to exploring and interfacing with that monstrosity's database and have my regular PyCharm instance for code dev and light touches against the DB. Additionally, at another time it proved nearly impossible to get the IDE db explorer to work properly with the jdbc drivers for a couple of large-scale hosted data lakes, but was rather straightforward in DataGrip. I have no clue why it was an issue with the explorer in PyCharm, but since I got it working in DataGrip I rather quickly moved on and accepted that I was gonna use DataGrip for the data lakes. That said, I definitely love the db explorer feature, and recommend everyone take a look at it if you're already using a JetBrains product. Also, just another shout-out to JetBrains again for their hybrid subscription/lifetime ownership license approach, demonstrating that paid software can exist in the realm of linux systems and that you can make a successful company without resorting to bleeding your customers dry over subscription fees.