macando

10 ms·

31.
by macando 5y ago
> The absolute killer app is compilers, static analyzers, and similar. In other words, those problems that don't involve users and the outside world. Pure languages for pure problems. Impure languages for impure problems. It compute
32.
by macando 5y ago
My other favorites are Traction, Peopleware and Made to Stick. However, they are 230+ pages long. Pretty consise, but I think they could have been shorter. There aren't many non-fiction books that are 150p and less. Hmmm
33.
by macando 5y ago
> And for most business/tech books, the second price is orders of magnitude more costly than the first. Couldn't agree more. The idea is great. Lean books should be a thing.
34.
by macando 5y ago
Traction is in my top 5 of non-fiction books. [2] looks interesting
35.
by macando 5y ago
Most non-fiction books could be long essays at best. Books are usually padded with needless repetition and anecdotes.
36.
by macando 5y ago
> I simply learned long ago that people who don't have skin in the game rarely give good game advice. This is highly quotable.
37.
by macando 5y ago
I wish more authors could adopt your zero-fluff-all-insights approach. Thank you for writing the book, I recommended it many times.
38.
by macando 5y ago
Experienced and exposed to areas outside their main expertise so they are well rounded and pragmatic.
39.
by macando 5y ago
Correct. It's 136p long. I remember it as no more than 85p. It's that good. > If you just see complainers maybe the problem isn't that important ;) Good point.
40.
by macando 5y ago
It's an over-reliance on ceremony. On some days I think it's a character trait.
41.
by macando 5y ago
Best book on early stage startups period. And it's barely 100 pages long. My favorite quote from it: “Someone should definitely make an X!” “Have you looked for an X?” “No, why?” “There are like 10 different kinds of X.” “Well I didn&
42.
by macando 5y ago
> it have been divided in more that 25 files that hold 3 or 4 lines of code at most, with so many abstraction layers that it's impossible for the best of us to follow in one go. When you put engineers in charge you get overengineeri
43.
by macando 5y ago
It's because a popular book on DDD "Implementing Domain-driven Design" uses CQRS in its examples. If the book was written today CQRS would probably be replaced with Serverless computing or something even more trendy.
44.
by macando 5y ago
Most influential - Clean Code and The Joy of C (the first programming book I've read) Most informative - Effective Java Funniest - Learn You a Haskell for Great Good! Best written - Eloquent Ruby Most useful - Data Modeling Essentials
45.
by macando 5y ago
> at FAANG and hedge funds.
46.
by macando 5y ago
Since the article is talking about the great expansion I'm offering a counterpoint - the great collapse. https://www.swyx.io/js-third-age/ > Collapsed Layers (One thing doing many things well instead of many t
47.
by macando 5y ago
Great analysis. My only remark is that the focus is fully on the backend/infra. On the frontend, observability and transparency are the main reasons why I still use Redux and its dev tool. It's like live logs on steroids. Not only
48.
by macando 5y ago
You can try this experiment: Go to Google or Facebook careers page and see if any of the listed positions match what you're doing at your current co. Then cross-reference that positions with comp levels at levels.fyi If it's all g
49.
by macando 5y ago
Learning programming to consult or create a B2B product that you can sell to your current employer/industry sounds much better than starting from the ground level as a junior dev.
50.
by macando 5y ago
Unless you're immensely talented with insane energy levels and plenty of free time it would take you 3 to 5 years to get to similar comp levels as a dev. Keep in mind that established and talented engineers prepare for 3 to 12 months
51.
by macando 5y ago
No. You can be a VP of Product without an eng background. Learn just enough coding to be able to communicate with devs. Learning UI/UX Design or Project Management would be an easier path.
52.
by macando 5y ago
Amazing! I've just recommended Dieter Rams: As Little Design As Possible book on LinkedIn. Good design is needed everywhere. It's much more than adding a gradient to a Buy button.
53.
by macando 5y ago
I like this analysis. It looks like instead of Agile we need Fluid. Technically speaking, you have an equation where the number of variables is too high to successfully optimize against. From a business point of view you need to have one pe
54.
by macando 5y ago
Great comparison. > A new manifesto should make changes that reflect these systemic problems. I feel we're approaching this point.
55.
by macando 5y ago
https://pbs.twimg.com/media/E-Yqz8uVUAQSTsf?format=jpg&name=...
56.
by macando 5y ago
> Again, not strictly a problem with Scrum, but just how nearly every good process (or at least decent process) gets corrupted when it becomes institutionalized. Is there a solution to this? Where's the issue? Company size? Bad cult
57.
by macando 5y ago
No risk, no progress.
58.
Ask HN: Is it time to retire Agile?
9 points by macando 5y ago|17 comments
59.
by macando 5y ago
Fortran on Flames
60.
by macando 5y ago
Please check my answer to "capableweb" user in this thread.

More ›