kevsim

35 ms·

421.
by kevsim 6y ago
That’s a very good question. The reality may be that if one cannot afford at least one native iOS dev and one native android dev (given the size of the app that person could share other duties) then one is not in a place to launch a mobile
422.
by kevsim 6y ago
I think perhaps the more interesting question (more interesting than what you label something) is how much functionality you develop before trying to get people to actually use your product. At least in the space I’m working in (issue track
423.
by kevsim 6y ago
Probably a boring story but I worked with my co-founders for years at a larger company before we agreed we wanted to scratch our own itch, quit, and make a startup. Nothing beats a multi-year test drive.
424.
by kevsim 6y ago
I've always worked in relatively large companies, and I've led several mobile teams. I've always ALWAYS been a native mobile purist. I had iOS people writing Obj-C and Swift, I had Android people writing Kotlin/Java. I h
425.
by kevsim 6y ago
The leaders I've had who have been the best at delivering bad news are the ones that have been decisive and clear about the direction we're heading all along. If a "leader" who is rarely visible and who doesn't actu
426.
by kevsim 6y ago
> There was transparency and traceability That makes a lot of sense. Do you think you could have achieved the same thing with regular sync ups or prioritization meetings or discussions without worrying too much about what you'd get
427.
Ask HN: Does your team plan work in sprints/cycles?
2 points by kevsim 6y ago|5 comments
428.
by kevsim 6y ago
Completely agree. I’ve been in engineering and engineering management for years, but starting my own company has forced me into a whole new skill set, particularly around getting distribution for a SaaS product. It’s all hands on a deck whe
429.
by kevsim 6y ago
Both could work. Pick the one that’s closest to the type of thing you’d be working on in the types of roles you’d be applying for.
430.
by kevsim 6y ago
It's a challenging situation you're in. As a hiring manager, I often find people who've done a lot of outside learning don't stand up to interviews because they often haven't really internalized the material. What c
431.
by kevsim 6y ago
Question for the HN crowd - seems like people doing any sort of self promotion on these types of questions inevitably get downvoted. Is there a stated rule against it or is it just generally not appreciated?
432.
by kevsim 6y ago
Congrats on launching! As a happy Superhuman user, I'd be very tempted to try this out. Tough to commit to the price without testing though.
433.
by kevsim 6y ago
I'd say the main factors that avoid getting stuck in the weeds of opinion vs. opinion are: - Focus on the outcomes you want to achieve, not the exact thing you're building or the way you're building it. This should be based o
434.
by kevsim 6y ago
This article makes me feel very fortunate to work the way we do in my company. We have tight feedback loops with our users, we plan work together as a team (not just a PM dictating things), we're not forced to give finger-in-the-air es
435.
by kevsim 6y ago
I've been considering integrating the ability to embed diagrams written with Mermaid into the issue tracker I'm building [0]. Would you say it's ready/robust enough for that? People typically want to scribble down quick
436.
by kevsim 6y ago
In left wondering what the actual pain users are experiencing with labels and how this actually solves that pain. Hearing things “all issues need to be assigned a label” makes me think this way of working will cause more pain than it solves
437.
by kevsim 6y ago
I guess you’ll hit a lot of SPAs that don’t work at all, but then again you can always opt in on those.
438.
by kevsim 6y ago
Absolutely but then the answer I need is in git.
439.
by kevsim 6y ago
It's something I haven't tried because I can already predict the outcome. I'd get into for a few weeks, I'd put a bunch of stuff in there, but I wouldn't be able to break the muscle memory of just using Google/
440.
by kevsim 6y ago
Looks roughly like how we do it as well with one exception - we don’t crash on “programmer errors” because we don’t maintain any local state in the node process. If all state lives in your DB, Redis, etc. it’s perfectly ok to have a catch a
441.
by kevsim 6y ago
As a startup CTO, I’m grateful not to have anyone hounding me to deliver features “on time”. We iterate on them until they meet the desired outcome for our users and my own requirements in terms of quality. Then we ship them. Might take a w
442.
by kevsim 6y ago
Sounds like something you could pull off in Zapier (or an open source equivalent) perhaps?
443.
by kevsim 6y ago
Previous discussion https://news.ycombinator.com/item?id=23467289
444.
by kevsim 6y ago
I've worked part time as an engineering manager before. Anything from 80% down to 50% (after my kids were born, when trying to start a startup on the side, etc.). It's usually possible to scale your work to suit the percentage you
445.
by kevsim 6y ago
Just to be clear, I wasn't saying it's not unethical. Just not illegal.
446.
by kevsim 6y ago
In my experience, the easiest way to make these "leaps" is to do so within the company in which you're already working provided that a) you've been successful in your role and b) your company is a flexible place that val
447.
by kevsim 6y ago
Any FB employees on here that can discuss what the constant deluge of articles like this does for morale inside the company? Curious if the rank and file are preoccupied with all this or if it still just feels like good times.
448.
by kevsim 6y ago
IANAL but I would assume FB is in the clear legally though as they're not actively blocking anything in particular, merely providing the tool with which admins can do the blocking themselves.
449.
by kevsim 6y ago
We use the term "theme" rather than "epic" but it's in the same ballpark in terms of "thing used to gather issues together". However, we don't use them to represent features, instead we use them to re
450.
by kevsim 6y ago
Congrats on launching! The service looks really nice and professional. One criticism though. It's possible to overstate the value of user feedback: > We provide everything you need to learn from your users while saving you hundreds

More ›