If you’re using free Heroku dynos, the first visitor in a while will experience long load times because the dyno has to be spun up. This is a pretty bad experience. I’d spend the 7 dollars each month to make sure your dyno is always up.
A two-person startup already uses twenty-eight other tools
51–60 of 468 posts
Re: A two-person startup already uses twenty-eight other tools
#52“28 other tools” on top of the two already working there? Sorry, couldn’t resist.
Why this personal abuse?
Re: A two-person startup already uses twenty-eight other tools
#53I feel like a big portion of the apps you accomplish similar things. To name a few, Airtable, Notion, and Trello can all do CRM funnel, product roadmap and issue tracking. Even though 2 out of 3 are free, you guys could probably condense them into a centralized spot.
They only spend $227/month in total. Why even bother centralizing? That's peanuts. I spend more than that on my personal AWS bill.
Re: A two-person startup already uses twenty-eight other tools
#54Re: A two-person startup already uses twenty-eight other tools
#55I believe the attention cost of using and keeping up with so many great tools is underappreciated. Maybe it's just me, but I'd rather use Github Projects than Trello not because GHP is better (it is not) but because I'm already using Github, and the mental and workflow cost of adding Trello to the mix is (I feel) higher than its additional value.
Notion in particular drives me nuts. I mean it's very very well done, but you use it to create a hierarchy of collaborative documents... because apparently GSuite docs are not good enough? Notion I think is a case of local maxima, because Gdocs/Office365 offer so many more ways to keep documentation and data in better formats (doc, sheet, slides...).
Sometimes I feel crushed under the weight of a thousand good things. :)
Re: A two-person startup already uses twenty-eight other tools
#56A one-person startup uses not less than yours :) https://www.listennotes.com/blog/the-boring-technology-behin... It's a good thing that we can outsource tasks to 3rd party SaaS for a small fee, rather than hiring full-time employees
I love this post. Have you upgraded PyCharm to make use of the Django support in your IDE?
Re: A two-person startup already uses twenty-eight other tools
#57Not exactly the same, but I have sometimes wondered how many startups are just burning other startups' money, and would collapse if VCs tightened the belt. For instance, startup X seems profitable but all revenue is from other startups not making money yet. Like a big ponzi scheme of sorts. Most products mentioned in the article are now mainstream, but for lots of them a few years back they were small and only used b…
Welcome to the Mass of the Church of Decentralization. Here is your baptismal wallet address.
Re: A two-person startup already uses twenty-eight other tools
#58[deleted]
Re: A two-person startup already uses twenty-eight other tools
#59It would be interesting to see this kind of list for the "start-ups" in '90s.
I guess Windows and MS Office licenses would be unavoidable items on the list.
Re: A two-person startup already uses twenty-eight other tools
#60I am the CIO of a mostly remote, cybersecurity startup (50 FTEs). I balance between not single-threading all choices through me and not letting things get too out of hand. That means no one is every really happy. E.g., we use Uberconference for videoconferencing. We thoroughly looked at a bunch of others and chose UC for its functionality, price, and simplicity (every conference gets a simple phone number, no stupid…
Eh, the problem with the "IT department dictates all the choices because the devs are stupid" approach is that it takes ownership away from the devs, therefore leading to a self-fulfilling prophecy. If I can't be trusted to make technology decisions for the system I know about (and the IT department knows nothing about), then why should I care about delivering the best possible product? Sorry, I've seen exactly that…
I think both view points are true.
- In orgs that don't trust dev typically have significantly less understanding of dev, and in my experience have really poor security postures. Everything is a slow manual process decided by people who don't understand apps or automation.
- In orgs that trust dev too much, you usually get a federated architecture that doesn't make any sense from a strategy point of you. Some teams are great; others don't have basic controls. You typically have a bunch of different consultancies playing land and expand and selling expensive solutions that don't actually work.
As usual, the sweet spot is probably somewhere in the middle.