Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
mrskitch
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
91.
▲
by
mrskitch
7y ago
Nice work, Tim! Glad to see you’re still doing well, hoping the best for you and ChecklyHQ. I’ve also thought and noticed similar results with the on-site chat UIs. I really don’t like them from a consumer perspective, but they sure do get
92.
▲
Simple tips to improve puppeteer's performance
(docs.browserless.io)
1 points
by
mrskitch
7y ago
|
0 comments
93.
▲
by
mrskitch
7y ago
Thanks for that! Hope it’s going well!
94.
▲
by
mrskitch
8y ago
Hey! I just did/am doing an AMA on dev.to (located here: https://dev.to/joelgriffith/i-m-the-creator-of-browserless-i... ). I run a one-person (me!), bootstrapped business called browserless ( https://bro
95.
▲
Painless Puppeteer Debugging
(docs.browserless.io)
2 points
by
mrskitch
8y ago
|
0 comments
96.
▲
Show HN: Browserless usage-based accounts are live (solo, self-bootstrapped)
(docs.browserless.io)
2 points
by
mrskitch
8y ago
|
0 comments
97.
▲
by
mrskitch
8y ago
++ to this. Experience is the best teacher, though I think it widely depends on the person learning. Some individuals will learn well from others' whereas others really need to feel the fire to know why it's hot. This, of course,
98.
▲
by
mrskitch
8y ago
This post was in response to another (last year) post we did last year: https://docs.browserless.io/blog/2018/06/04/puppeteer-best-p... . Many of those things still applied, but we've picked up on a
99.
▲
Headless Chrome tips after running 5M sessions a week
(codeburst.io)
11 points
by
mrskitch
8y ago
|
1 comments
100.
▲
by
mrskitch
8y ago
I can attest to the quality of Fathom. I switched over browserless.io from Google Analytics to fathom. Been very nice.
101.
▲
by
mrskitch
8y ago
Good luck! Having just reached that milestone with browserless.io (Revenue: https://www.indiehackers.com/product/browserless ), I can assertively say you’ll learn _a lot_ from getting there. The biggest skill I wish I h
102.
▲
Elegantly debugging puppeteer and fixes to common issues
(docs.browserless.io)
1 points
by
mrskitch
8y ago
|
0 comments
103.
▲
by
mrskitch
8y ago
Having dug ditches for septic tanks for a few years I can definitely vouch for _not_ doing it. 5 years of digging ditches is awful work, and most people aren't cut out for that level of manual labor. After a week I think most programme
104.
▲
by
mrskitch
8y ago
I, honestly, picked a library that I was passionate about (puppeteer) and sorted by either most commented or most reacted. This plus the fact that I was having hosting issues with Headless Chrome. browserless.io came quickly after.
105.
▲
by
mrskitch
8y ago
Thanks for sharing this. It's really important not to give too much thought to hypotheticals as they're purely that: a hypothetical.
106.
▲
by
mrskitch
8y ago
After having founded a non-VC backed company (browserless.io), my anecdotal experience is that most potential creators out there need more encouragement to stand out on their own two feet. The maker market has huge potential, but there are
107.
▲
by
mrskitch
8y ago
I'm not sure if I'd call it simple, but the product itself is fairly straightforward (at least to me :). I run a SaaS product called browserless ( https://browserless.io ). Goal here was to make it really simple to run h
108.
▲
Dealing with file downloads in puppeteer
(docs.browserless.io)
9 points
by
mrskitch
8y ago
|
0 comments
109.
▲
by
mrskitch
8y ago
I've written a bit about this in regards to browserless.io: https://docs.browserless.io/blog/2018/08/01/running-an-indie... if you're curious. But in short: 1. Build something that you're
110.
▲
Phantom pain: the first year running headless Chrome in production
(docs.browserless.io)
4 points
by
mrskitch
8y ago
|
0 comments
111.
▲
by
mrskitch
8y ago
Thanks! I try and be responsive as possible -- I know how painful it is to sit and wait for a response. Appreciate your comment!
112.
▲
by
mrskitch
8y ago
If you're starting something out it can be very inspiring! I used to listen to their podcast nearly daily when I was getting started, but dropped it after things got started. That same source of inspiration can be a distraction, and ev
113.
▲
by
mrskitch
8y ago
Last 30 days is kind of a bad metric for growth, especially for B2B apps where Q4 can be kind of brutal. Would be cool if they did "all time" or something more encompassing (and had other sources aside from IH). FWIW I run browser
114.
▲
by
mrskitch
8y ago
:)
115.
▲
by
mrskitch
8y ago
Appears it's locked now? Can't seem to reply :(
116.
▲
by
mrskitch
8y ago
This is a good point. My lessons from this are to pick a time when traffic isn't as high so you have a chance of gaining some visibility. Getting on the frontpage during non-peak hours is better than getting on page 2 during peak hours
117.
▲
by
mrskitch
8y ago
Great point. It's a hard thing to try and succinctly summarize, plus the title _has_ to be somewhat appealing or no one will ever visit it. It's a bit "damned if you do, damned if you don't" since lots of folks won&
118.
▲
by
mrskitch
8y ago
Hrm, it must have slipped past me, I'll take a look! EDIT: yeah, this is my bad. Totally missed it and it's a great comment too :(
119.
▲
by
mrskitch
8y ago
That's a good question. We've been doing this for ~year, whereas Chrome on App Engine/Functions has _just_ recently come out. So we've got a bit of a head-start and our infrastructure is pretty hardened at this point. Al
120.
▲
by
mrskitch
8y ago
I’ve actually had the exact opposite happen: my ShowHN posts got nowhere, but the product itself became successful. I’m sure that the opposite is also true as well, but figured folks needed to hear that, just because your ShowHN post got no
More ›