10,417 karma · joined July 24, 2008
email me - hn@reemer.com
- Fogbugz
- Unfuddle
- Pivotal Tracker
- Bugzilla
- Redmine
- JIRA
- Linear
- Basecamp
- Spreadsheet
- GitHub Issues
- Codetree (I ran this)
- Zenhub
- Shortcut
Probably missing a few. I've settled on Shortcut for now (formerly Clubhouse). It's a good balance between the "bag of bolts" JIRA approach and the "one way to do things" take that Pivotal Tracker has. Shortcut gives you sane defaults but with enough customization to suit reasonable workflows.
One trend that I don't really get is dev teams using general purpose tools like Trello or Asana to run their software projects. Sure, it's possible to do. But I find it much more sensible to use a purpose-built tool that understands the kinds of first-class objects (Issues, PRs, Comments, Workflows, Workflow Stages, Tasks). Makes life a lot easier.
Maybe it’s just me. But I don’t consider publicly traded companies to be anywhere near a startup.
As a buyer, I'd love to spend more with not-Amazon and get comparable service.
I'm increasingly disappointed with Amazon. It's full of knockoff crappy products with unrelated 5 star reviews. That eroding trust in Amazon is pushing me to smaller brands who have a face and stand behind their product for key purchases. This move by Shopify will just accelerate that transition away from Amazon.
Just waiting for the search bar to shop every Shopify store so I have a viable alternative to Amazon to buy whatever I need.
It has a bunch of extensions that you can use for budgeting, emailing daily transactions, reporting, optimizing debt payoffs using various different methods, etc.
Plus it's just a spreadsheet, so sorting/filtering etc just work. And it's as fast as having a large Google Sheet. So pretty darn fast.
https://www.savio.io/blog/how-saas-companies-get-in-app-prod...
At my co we ask for feedback:
0. When someone books a demo (email)
1. When a user signs up (in-app and via email)
2. When a user converts from trial to paid (email)
3. When a user cancels (email)
We also:
1. Use Intercom and lots of feedback comes in there
2. Have several in-app callouts to vote on features on our voting board or contact support
3. Close the loop with customers when we ship a feature they asked for, and ask for feedback
We could definitely do a better job on the in-app feedback collection side.
Are you saying account-level analytics are hard to come by in Amplitude, Mixpanel, etc?
Phrasing my comment a slightly different way: what’s the point of writing *in public* if you don’t get feedback?
—-
Original comment:
I don’t get it. If you want to write and don’t care how much you’re read, write privately (Google Docs, a journal, text file, etc.)
If you’re writing publicly presumably it’s for public consumption. The way you know if your writing is read is through feedback - comments, shares, email subs, etc.
Feedback on your writing both helps you understand where you need to think more deeply about what you wrote AND provides valuable positive reinforcement: somebody is reading what you put into the world.
Not providing hooks for these seems to defeat the purpose of writing in public.
I'm leading the development of an MVP. We have a tight set of product requirements and are seeking two fulltime full stack Rails devs to help us build it. Estimating the contract length will be 6 months to build the MVP, give or take. We'll also be building hybrid iOS and Android apps. Once done, there'll likely be a need to stay on further to transition the product to an internal team.
Tech stack is Rails 7 w/ Stimulus + Hotwire, TailwindUI, and Postgres deployed (probably) on Render. No code has been written yet but I'm considering using Jumpstart Rails.
Looking for product-focused devs who think about the end user scenarios, self manage, communicate well and often, and are fluent in written and spoken english. We'll use GitHub, Shortcut (or maybe Linear), and Email to run the project, and Zoom if we need to go sync.
It's a pretty dev-friendly gig:
- no legacy code to deal with
- we'll use modern tools + tech
- some interesting tech with the hybrid apps
- no daily standups
- async communication
- I'm a dev and your main point of contact (and I've been building w/ Rails since 2007)
Please email hn@reemer.com with subject "Loadspace Rails dev". Please share:
- the Rails projects you've built and what you did on them
- your hourly rate
- anything else you feel would be relevant
NO AGENCIES - SOLO DEVS ONLY PLEASE.
Thanks!
Our operating theory was that using a JS FE framework was overkill for a CRUD app. So we went with stock Django and server-rendered HTML.
It became clear that parts of our UX would benefit greatly from client-side interactivity, which is what we eventually expected to happen. We sprinkled in HTMX (on top of our Jquery) on certain pages and it's been a breath of fresh air. We even built a nice Kanban board w/ HTMX and a Jquery plugin. Key benefits include:
1. When you're looking at a template the HTMX syntax makes it obvious what happens
2. HTML is rendered server-side in templates (imho where it should be) and is sent down the wire
3. We get a lot of stuff for free from Django (routing, back button handling, etc) that we don't need to build with a FE framework
Even though we're devs we believe the best code is no code (in the literal sense, not the de rigeur "No Code" sense). Maintenance costs are important to us. Getting stuff for free is important to us. Building for a specific use case is incredibly important to us.
With that in mind, the Django + sprinkled HTMX experiment has been pretty successful thus far.
For example:
1. Has the Userpilot team failed at building and MVP and succeeded with an MLP? If so what did they learn and why?
2. Lots of people have succeeded with an MVP approach. They describe a handful of things you can do wrong when building an MVP... but what if you DON'T do those things that they claim lead to MVP failure?
3. Digging into one of the recommendations - don't sacrifice delighters. They talk about how they wouldn't include the Asana unicorn in their MLP and end with "balance delighters with effort". Fine. But HOW do you do that? What framework can you provide ME to do that?
This smacks of a writer doing a Google Research Project to offer up hand-wavy advice. 0/10 would not recommend.
FWIW I think it's reasonable to collect emails. But at least be honest as to whether the email field required (or not) on the form.
Or filling out pdfs programmatically (a docspring alternative)?
1. When the screen color changes at sunset it's a subtle but powerful cue to know that the work day is coming to a close. And then if I'm on my computer when it changes around bedtime that's a cue to GTF off the computer.
2. All the science I've read suggests removing blue light in the evenings does indeed help with sleep. So why not use it?
> There is a nonzero risk of autoimmune disorders which will be difficult to detect, especially if past preprints regarding expression of the spike protein in human tissues post vaccination prove to be true.
Which preprints? Why do you say autoimmune disorders have a nonzero risk and will be difficult to detect?
> actual safety trial data is a secret known only to pfizer/moderna and the FDA
Do you have a source?
> multiple points of "misinformation" have been proven correct.
Which points of misinformation are now correct?
1. How exactly it works
2. How it's different from existing remote work tooling (Slack / Zoom / Google docs / Miro / etc)