HN user

auchenberg

554 karma

kenneth.io

Posts34
Comments33
View on HN
www.youtube.com 2mo ago

Andrej Karpathy: From Vibe Coding to Agentic Engineering [video]

auchenberg
4pts0
kenneth.io 1y ago

No code is dead. Long live vibe coding

auchenberg
27pts32
getfaktor.com 2y ago

Show HN: Faktor – The missing 2FA code autocomplete for Chrome

auchenberg
26pts49
kenneth.io 3y ago

Developer Experience Infrastructure (DXI)

auchenberg
2pts0
inspect.dev 5y ago

Show HN: Inspect – DevTool to debug Safari and WebViews on iOS devices

auchenberg
75pts19
code.visualstudio.com 8y ago

What's new for Chrome debugging in VS Code

auchenberg
1pts0
medium.com 9y ago

Super-charged live editing and JavaScript debugging for Angular using VS Code

auchenberg
1pts0
medium.com 9y ago

iOS web debugging and screencasting in Chrome DevTools

auchenberg
1pts0
medium.com 9y ago

Hello RemoteDebug iOS WebKit Adapter: Debug Safari and iOS WebViews from Anywhere

auchenberg
1pts0
medium.com 9y ago

Live edit and debug your React apps directly from VS code

auchenberg
2pts0
medium.com 9y ago

Simultaneous “nirvana” JavaScript Debugging for Chrome and Node.js in VS Code

auchenberg
7pts0
github.com 9y ago

Show HN: Slack 538 – Presidential forecasts in Slack

auchenberg
2pts0
blogs.msdn.microsoft.com 9y ago

Introducing iOS Web Debugging for Visual Studio Code on Windows and Mac

auchenberg
10pts0
blogs.windows.com 10y ago

Debug Microsoft Edge from Sublime or VS Code with the Edge Diagnostics Adapter

auchenberg
4pts0
medium.com 10y ago

Why every Product Manager should learn how to code

auchenberg
4pts0
devtoolsremote.com 10y ago

DevTools Remote – Debug your browser tabs remotely via Chrome DevTools

auchenberg
2pts0
kenneth.io 10y ago

Chrome Dev Summit, a flashback to the good days of Google I/O

auchenberg
2pts0
github.com 10y ago

Volkswagen – detects when your tests are being run in CI, and makes them pass

auchenberg
195pts20
kenneth.io 11y ago

Safari isn’t the problem, but the lack of browser choice in iOS is

auchenberg
286pts223
kenneth.io 11y ago

Show HN: Concurrent editing and real-time visual comparison in Chrome DevTools

auchenberg
2pts0
kenneth.io 11y ago

Use Chrome DevTools to debug your user’s browser remotely with BrowserRemote

auchenberg
4pts0
github.com 11y ago

BrowserRemote, debug your user's browser remotely via Chrome DevTools

auchenberg
35pts1
kenneth.io 11y ago

RemoteDebug and cross-browser DevTools: One year later

auchenberg
2pts0
medium.com 12y ago

Seeing how long it takes to read a book with a paper clip and an extension

auchenberg
5pts1
dev.sh 12y ago

.dev – zero-config wildcard domains/dns

auchenberg
2pts0
kenneth.io 12y ago

What if you could use Chrome DevTools with Mozilla Firefox?

auchenberg
2pts0
www.nihilogic.dk 12y ago

JuicyDrop – Winamp Music Visualization with JavaScript and Canvas

auchenberg
66pts44
auchenberg.github.io 12y ago

SlotCount.js - Simple slot machine-like counter, inspired by Google Plus.

auchenberg
2pts0
kenneth.io 13y ago

The messy state of Web Notifications in Chrome's Blink and Safari's Webkit

auchenberg
3pts0
blog.kenneth.io 13y ago

Our web development workflow is completely broken.

auchenberg
9pts0
Stripe Checkout 6 years ago

Hi, Kenneth here from Stripe. I'd love to chat with you about the problems you have with webhooks. How can I best reach you? My email is auchenberg@stripe.com

Hi It's Kenneth from VS Code.

We have looked into this, and haven't found an intentional change that should change your opt-out settings. This shouldn't happen.

We have two theories:

1) Your settings file was deleted, which means that you would have lost all of your settings, and not just the telemetry setting. This can happen if the AppData or ~/Library/Application Support was cleaned up.

2) One of your installed extensions updated the settings either accidentally or on purpose. This would require further debugging, and a list of your installed extensions.

To help debug this further, it would be great help if you could open an issue on Github, https://github.com/Microsoft/vscode/, with more details about your OS, VS Code version and installed extensions, so we can figure out what happened.

Thanks!

/k

Working for Microsoft, and moved to Seattle, WA last year, after having lived in Vancouver, BC for about 1.5 year.

I can confirm this trend for several reasons:

1) The pay gap is real. Many get about a 40% pay increase by moving 3 hours down south. It's significant.

2) Taxes are aprox 10% lower in Seattle. Makes a difference too.

3) Rent-net-pay-ratio is about the same for Vancouver/Seattle

4) For a tech worker the health care is both places privately insured and the same.

Personally, I miss Vancouver. The city is awesome, and life quality is better, but financially it's simply not attractive enough.

Firefox doesn't implement the Chrome Debugging Protocol, but has it's own (FDP).

Valence is an protocol adapter that adapts CDP to FDP, so Firefox DevTools (using FDP) can be used with iOS (which uses WDP)

I completely agree. There's still a long way until we have a common API that caters for all use-cases across tools and runtimes, but uniting around the same protocol is the first tiny step towards this vision of better decoupled tooling.

Luckily the Chrome Remote Debugging protocols is quite flexible, so we could start iterating on the API's too using some sort of vendor prefixing, if needed.

No that's not what I'm saying in my post. A browser choice on iOS wouldn't make Safari go away, and wouldn't mean that developers shouldn't cater for mobile Safari.

But it would give us the option to deliver experiences for other browsers, that might lead to better and more innovative experiences for our end-users. We don't know, because we don't have the choice.