strife25

7 ms·

1.
by strife25 3mo ago
I think context matters a LOT here. Knowing when to be pragmatic and quick vs thorough is the mark of an experienced engineer. The trick is knowing HOW to pick the right approach. A key point is understanding the business (or personal) goal
2.
by strife25 3mo ago
Generally agree with this approach. We need to make sure that friction exists in our kids' lives. I have a toddler, and screen time is something that is on top of my mind, Balancing the trade-offs of when to use it while also minimizin
3.
by strife25 5mo ago
Marginal costs matter in this world.
4.
by strife25 5mo ago
I like this angle. I didn't read much of the article, but I do think this is a topic that people should consider, at least when it comes to estimating software projects. I don't think we really think enough about the monetary cost
5.
by strife25 4y ago
Does anyone know of good building science websites? I'd love to better understand best practices. The only one I've found is https://inspectapedia.com There's great stuff on YouTube too (e.g. Matt Risinger's
6.
Essential Scrumban Metrics for Elite Software Teams(buildthestage.com)
1 points by strife25 4y ago|0 comments
7.
by strife25 4y ago
> Sometimes making the cinematics wasn't a core competence of the studio working on the game, so VFX or animation studios would be contracted to do this. That explains why FFX's cinematics had different character models compare
8.
by strife25 4y ago
What I've been annoyed with for years: Drying Racks. What do people do instead of using these? I'm guess just hand drying them. I do have a lot of air-tight container lids that are super annoying to hand dry. I like the convenienc
9.
Stop Asking Small Questions(buildthestage.com)
2 points by strife25 4y ago|0 comments
10.
by strife25 4y ago
Labor wasn't the issue, it was UX. Users wanted responsive UIs and Gmail showed the power of AJAX in the browser. In the mid-2000s, server power, network latency, and maintaining state were the challenges. The UX was more powerful when
11.
by strife25 4y ago
_hums the rhythm of wisdom_
12.
by strife25 4y ago
+1 SPAs were a workaround to slow CPU servers serving millions of requests in the mind-2000s. Client computers were faster, so it made sense to push UX logic there. We've flipped things around. Servers are fast as hell for rendering HT
13.
Stop Asking Small Questions(buildthestage.com)
1 points by strife25 4y ago|0 comments
14.
by strife25 4y ago
I switched from Paprika to Plan to Eat this year and love it. Https://plantoeat.com It has the same features as Paprika but Generates a shopping list from your meal plan. Saves a ton of time when shopping. The one thing I don’t li
15.
by strife25 4y ago
Exactly! It’s a crazy diverse user base too. The needs of designers creating a marketing site and engineers working on a real web app are different, but they all work with web tech.
16.
by strife25 4y ago
The bar to writing javascript is so much lower compared to other languages. All you need is a browser and learn how to open its devtools. Beyond that, you need a text editor, learn basic HTML and JS, and open a file in your browser. Compare
17.
Headcount Planning and Title Levels(buildthestage.com)
1 points by strife25 4y ago|0 comments
18.
Finally, a reason to over-engineer your app(buildthestage.com)
5 points by strife25 4y ago|1 comments
19.
Who owns your product roadmap?(buildthestage.com)
2 points by strife25 5y ago|0 comments
20.
by strife25 5y ago
The book is completely fine and worth the read! Just know that it's a book to explain the career path of an Engineering Manager in the tech industry. My criticism is around how often the book is recommended. Many people want to learn H
21.
by strife25 5y ago
Everyone recommends The Manager's Path, but I don't think it's a good book to explain HOW to become a manager. The book's goal is to explain the career path of a manager from tech lead to CTO. My #1 recommendation these
22.
Writing Performance Reviews That Inspire People(buildthestage.com)
2 points by strife25 5y ago|0 comments
23.
by strife25 5y ago
When it comes to how much testing should be done, I think it's contextual on the project. I expand on this specific point in a blog post: https://www.buildthestage.com/just-enough-automated-tests/
24.
by strife25 5y ago
I've had the most luck w/ TDD for designing APIs. When I write the tests first, it gives me a feel for how consumers of the API will use it. It's a great method to understand the UX of the re-usable code.
25.
by strife25 5y ago
Shameless plug for my blog: https://www.buildthestage.com I write about technical leadership and engineering management. The target audience are technical leads, managers, and people who wish to become leaders one day.
26.
Just Enough Testing(buildthestage.com)
3 points by strife25 5y ago|1 comments
27.
by strife25 5y ago
Reminds me of a recent email I got from a CTO community commenting on the "crazy salary inflation" that's occurring in the tech industry.
28.
Project Estimates Are Not Deadlines(buildthestage.com)
2 points by strife25 5y ago|0 comments
29.
Hank Scorpio: Great Boss, Vision(buildthestage.com)
2 points by strife25 5y ago|0 comments
30.
by strife25 5y ago
I used this method for a while on one of my teams. It was useful and helped provide more accurate estimates. Some tips I have for people interested: * Get about two months of velocity data in place first. * Run the simulation on a regular b

More ›