peterbell_nyc

7 ms·

61.
by peterbell_nyc 7y ago
> There's also opportunity cost. What could this team have done if they were working on something more... disruptive? The execution here is incredible, applying that to a new problem would have probably also done very well. My lates
62.
by peterbell_nyc 7y ago
Making a product might be easier. Getting enough people to buy it to turn it into a profitable business, not always easier :)
63.
by peterbell_nyc 7y ago
Yup - another resource is "the E-myth revisited" which makes the point that if you want to be a baker, don't start a bakery because now you're dealing with taxes, permits, hiring, vendors, marketing, etc - not just bakin
64.
by peterbell_nyc 7y ago
I think at best this is fizzbuzz for DS, which is not inherently wrong. It's nice to know a software developer can write a loop and a data scientist can use a JN, so for weeding out people who have no practical experience with a given
65.
by peterbell_nyc 7y ago
I think there are misalignments, but I'm not convinced that false negatives are one of them. If I can fill all my req's with amazingly talented, lovely and capable people, it doesn't really matter so much to me if there are o
66.
by peterbell_nyc 7y ago
Sounds like your team might be doing standups wrong. Firstly they should be 3-8 mins tops. Secondly, I consistently find that when someone mentions what they're working on, more days than not, someone shares something useful (hey, we d
67.
by peterbell_nyc 7y ago
I'm going to disagree. For every year I've spend doing something, I've got better at it. While there are definitely people with "1 year of experience repeated 30 times", I can't believe that you hit a point in
68.
by peterbell_nyc 7y ago
That's a great way of hiring people who aren't good enough to get a remote job at SF wages. The problem is that it cuts off the ability to hire the top of the market. I currently live in Boulder, Co, but I never even considered wo
69.
by peterbell_nyc 7y ago
The difference is that every time you do the process, you can consider writing a couple of tests and automating the step.
70.
by peterbell_nyc 10y ago
I'm not a climate scientist and don't play one on TV> It appears that most people who are (and are thus way better informed than me) have a consensus suggesting that climate change is both being caused by humans and lining up t
71.
by peterbell_nyc 10y ago
Although without sufficient oxygen production globally, new coastal property would be of limited value! Would be interesting to see peer reviews of the study to get a sense of how problematic this might be. I guess worst case we could all g
72.
by peterbell_nyc 11y ago
Well, I think an engineering team of 200 (or even 50 if 200 is your entire company) starts to exhibit some of the characteristics of a "large company". I've seen very small engineering teams succeed with microservices, but I&
73.
by peterbell_nyc 11y ago
Depends where you are in your product lifecycle. Pre-product market fit, it's often a bad idea to build and keep a stable backlog a few weeks in length.
74.
by peterbell_nyc 11y ago
Great job and congratulations!
75.
Quiz: do you know how to undo anything with Git(credspark.com)
5 points by peterbell_nyc 12y ago|0 comments
76.
by peterbell_nyc 13y ago
Great post. It's a real issue for many startups I talk to that wonder why they're having a hard time recruiting tech talent and haven't spent the time to build a brand and relationship with engineers. If you happen to have a
77.
by peterbell_nyc 14y ago
Hi Jean, Agreed 100% - both with the value of meetups and balancing the technical risk assessment. I'm doing a keynote at NFJS New York on "how to select and adopt technologies" that talks a lot about community focus, where in the technolog
78.
by peterbell_nyc 14y ago
Yeah - that's a really hard change. For anyone dealing with a legacy system, I always recommend Mike Feathers' book on "working effectively with legacy code". He talks about lots of patterns for dealing with this. I'd probably see if I coul
79.
by peterbell_nyc 14y ago
@Matt, thanks for including this link. I'd read it a while back (maybe a link from you!) but couldn't find it when I was putting this together last night.
80.
Innovation Debt(blog.pbell.com)
52 points by peterbell_nyc 14y ago|26 comments