typeofnandev

4 ms·

1.
by typeofnandev 3y ago
This is so ruby
2.
Ask HN: Have you created a profitable B2B SaaS product? If so, what's the story?
1 points by typeofnandev 5y ago|0 comments
3.
by typeofnandev 5y ago
MDN gets better, and better, and better. Their discussion on "Things to consider when using frameworks" is so on point and makes me happy to read. Back when I was hiring front-end engineers, I would often ask questions that are ni
4.
Ask HN: What's the most outrageous over-engineering you've seen in the wild?
15 points by typeofnandev 5y ago|21 comments
5.
If your refactors break a lot of tests, you may not be testing the right things(typeofnan.dev)
5 points by typeofnandev 5y ago|0 comments
6.
Taking pixel-perfect screenshots every time using Chrome Devtools(typeofnan.dev)
3 points by typeofnandev 5y ago|0 comments
7.
Ask HN: What lessons did you learn from your best or worst colleagues?
231 points by typeofnandev 5y ago|258 comments
8.
by typeofnandev 5y ago
The last sentence of this piece makes it for me, and it's this optimism that generally gets me through my day: But I think we need to make a conscious effort to realize: every time is different. Even if you put the same effort in and m
9.
It's better to be naive than jaded(macwright.com)
3 points by typeofnandev 5y ago|1 comments
10.
by typeofnandev 5y ago
>The problem with Jira (or at least used to) is that it has so much complexities that let people make it overly complicated. I actually really like this take, because a lot of the times it feels like a tool's complexity is from what
11.
by typeofnandev 5y ago
If only it _was_ the case!
12.
by typeofnandev 5y ago
There's a lot of truth to this. I feel like I'm willing to really dig in and learn a tool if I can sense that the power of wielding that tool will be commensurate with the difficulty learning it.
13.
The Return of Fancy Tools(macwright.com)
447 points by typeofnandev 5y ago|216 comments