Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
scottnonnenberg
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
5 ms
·
1.
▲
by
scottnonnenberg
9y ago
You seem pretty passionate - wanna help us test proxy and system tray support? Tray support behind command-line argument: https://github.com/signalapp/Signal-Desktop/pull/1676 Proxy support behind command-lin
2.
▲
From tech person to people person
(blog.scottnonnenberg.com)
2 points
by
scottnonnenberg
9y ago
|
0 comments
3.
▲
Breaking the Node.js event loop
(blog.scottnonnenberg.com)
2 points
by
scottnonnenberg
9y ago
|
0 comments
4.
▲
What's a Monad? Digging into Haskell
(blog.scottnonnenberg.com)
2 points
by
scottnonnenberg
9y ago
|
0 comments
5.
▲
The Why of Agile
(blog.scottnonnenberg.com)
2 points
by
scottnonnenberg
9y ago
|
0 comments
6.
▲
by
scottnonnenberg
9y ago
Feel free to reach out. :0)
7.
▲
Carrots, not sticks
(blog.scottnonnenberg.com)
2 points
by
scottnonnenberg
9y ago
|
0 comments
8.
▲
by
scottnonnenberg
9y ago
Yep, as I mention down-thread, merges only happen at GitHub/GitLab/etc. The two mistaken scenarios I run into the most are: 1. `git pull` when I'm not in the right branch, which will want to do a merge. 2. When I have commit
9.
▲
by
scottnonnenberg
9y ago
Wouldn't it make sense to turn that off per-project when you encounter it?
10.
▲
by
scottnonnenberg
9y ago
My local configuration doesn't need to be ready to create merge commits because those happen on GitHub/GitLab/etc. When I rebase, it's my own pull request on top of a more recent master - the signer remains me.
11.
▲
Better Git configuration
(blog.scottnonnenberg.com)
388 points
by
scottnonnenberg
9y ago
|
63 comments
12.
▲
A JavaScript static analysis journey
(blog.scottnonnenberg.com)
3 points
by
scottnonnenberg
10y ago
|
0 comments
13.
▲
Think in alternatives (Dev productivity tip #5)
(blog.scottnonnenberg.com)
1 points
by
scottnonnenberg
10y ago
|
0 comments
14.
▲
Web application test strategy
(blog.scottnonnenberg.com)
2 points
by
scottnonnenberg
10y ago
|
0 comments
15.
▲
Getting started with Elixir
(blog.scottnonnenberg.com)
4 points
by
scottnonnenberg
10y ago
|
0 comments
16.
▲
The dangerous cliffs of Node.js
(blog.scottnonnenberg.com)
1 points
by
scottnonnenberg
10y ago
|
0 comments
17.
▲
Taking Agile beyond the dev team
(blog.scottnonnenberg.com)
1 points
by
scottnonnenberg
10y ago
|
0 comments
18.
▲
by
scottnonnenberg
10y ago
Oh, I certainly agree that coding standards are important. Consistency of coding style makes a codebase substantially more approachable. I'm just interested in making that as automated as possible: https://blog.scottnonnenbe
19.
▲
Pull request review mistakes
(blog.scottnonnenberg.com)
96 points
by
scottnonnenberg
10y ago
|
30 comments