kevsim

7 ms·

31.
by kevsim 3y ago
After relocating from the US to Scandinavia, people here are always give me crap for having worked in a cubicle farm. And I always tell them I'd go back to that layout in a second compared the open landscape nightmare we have everywher
32.
by kevsim 3y ago
I'm pretty sure if you have to commit wire fraud to build your business, you can't really claim to be that great an entrepreneur.
33.
by kevsim 3y ago
Congrats on the launch! For teams that are using something like customer.io, how does this fit into the picture? Is it a replacement or a companion? And to nerd out a bit - how was working with Lexical? We chose Slate.js for our editor in K
34.
by kevsim 3y ago
We used Webflow for our company's landing page for a while but for our uses it was more "slow code" than "no code". To get the layouts we wanted you still had to understand the quirks and intricacies of flex/gr
35.
by kevsim 3y ago
The typical way would be to report it to the data protection authority in the European country in which you reside. Then they'll decide whether to take any action.
36.
by kevsim 3y ago
Unsolicited praise - we've been using ToDesktop at Kitemaker for a while now and we're super happy with it. The team is always super responsive to our requests and the product has been very stable. We were rolling our own Electron
37.
by kevsim 3y ago
I guess if you can afford the jet, you can afford to have a helicopter waiting to pick you up?
38.
by kevsim 3y ago
Meaning your server?
39.
by kevsim 3y ago
Gotta say, not really looking forward to GPT generated recipes rendered by Stable Diffusion.
40.
by kevsim 3y ago
Just be sure to bring a raincoat
41.
by kevsim 3y ago
Yeah, need to select everything to read it.
42.
by kevsim 3y ago
For me, it was the exact opposite. It was a feeling of "finally, this is what I'm supposed to be doing". It takes all sorts, as they say.
43.
by kevsim 3y ago
I think Segment did something similar a while back. Instead of using Kafka for the queue of events in coming in, they built a queue on MySQL [0] 0: https://segment.com/blog/introducing-centrifuge/
44.
Fixing a 3 second lockup in our app by switching from Apollo Client to URQL(kitemaker.co)
18 points by kevsim 4y ago|0 comments
45.
How to write great one-pagers, PRDs, Specs, and more(kitemaker.co)
2 points by kevsim 4y ago|0 comments
46.
by kevsim 4y ago
This is somewhat similar to the Shape Up methodology from Basecamp [0] where there's a 2 week "cool down" at the end of every development cycle. So 6 weeks of feature development, followed by 2 weeks of bug fixing, refactorin
47.
by kevsim 4y ago
I've never seen tip #4 (Rewrite negative conditions) or anything like it before. I can't see how that improves readability at all. If I saw it in a code review I'd ask the developer if they forgot to fill in the body of the i
48.
by kevsim 4y ago
> Is wearing blue denim jacket and jeans an anti-pattern? The Canadian tuxedo is clearly a best practice.
49.
by kevsim 4y ago
I think this is the default for services like Intercom and you can't stop it [0]. It's super annoying. 0: https://www.intercom.com/help/en/articles/5053699-how-do-i-s...
50.
by kevsim 4y ago
We also had the OT vs. CRDT discussion with regards to our editor at Kitemaker (kitemaker.co), and also ended up with OT. For us there were a number of factors, but (in addition to the case you mentioned) it came down to the fact that (at t
51.
by kevsim 4y ago
Totally agree. "Hey Siri, start a timer for X minutes" and "Hey Siri, play Y on Spotify" are the entire extent of my voice assistant interactions.
52.
by kevsim 4y ago
Yeah, when we built our product (kitemaker.co) we introduced offline capabilities quite early because my co-founder often had very spotty wifi during train commutes. We ended up making all writes totally optimistic with data sync in the bac
53.
by kevsim 4y ago
That's what I read it as and was a bit disappointed when it turned out not to be the case.
54.
Lessons Learned from Moving to Recoil.js(kitemaker.co)
10 points by kevsim 4y ago|0 comments
55.
by kevsim 4y ago
I find the 'never fix a bug and refactor in the same commit' advice somewhat questionable. If the code is a mess and I'm going to refactor it anyway should I spend a lot of time trying to fix the bug in the old code only to r
56.
by kevsim 4y ago
> Because an issue tracker is for tracking issues... not... oh nevermind. That's exactly the point we are trying make. Issue trackers are good at tracking issues, but now people use issue trackers to track everything, from product d
57.
by kevsim 4y ago
We've discussed introducing automation to move done things to the archive periodically (just to keep the board tidy) but we haven't gotten many requests for automatically closing stale things. Yet. Maybe there's a bit way to
58.
by kevsim 4y ago
This is very insightful feedback. Thank you for that! One thing people tell us they like about Kitemaker is the ability to have a historical view of things. Because all of those extra edge cases that pop up get captured right in the same wo
59.
by kevsim 4y ago
Thank you for the thoughtful feedback! Easy one first - pricing. It's always a challenge but we try to find something that's reasonable when compared to the competition. We're not big fans of tools that do limited time featur
60.
by kevsim 4y ago
Thanks for the tip! Zapier's SEO prowess is awe inspiring.

More ›