Jamie Tanna
jvt.me · Personal blog · on HN since 2018
Jamie Tanna, a software engineer who writes about his public salary history, IndieWeb, Go, SQL and developer tooling.
What HN saysHN links his salary history posts in pay-sharing threads and his IndieWeb site as an example of a personal website, plus his Renovate advice.
41HN people shared it
8linked it in comments
114stories submitted
1.7Kstory points
3 months agolast shared
2018people per year2026
Most-shared posts
- 1Lessons learned since posting my salary history publicly5 people · 135 points · first shared 2022 · 162 comments on HN
- 2Why I Have a Website and You Should Too4 people · 12 points · first shared 2019 · discussion on HN
- 3My Salary History3 people · 37 points · first shared 2022 · 24 comments on HN
- 4Some useful SQL(ite) tips I've learned3 people · 19 points · first shared 2024 · discussion on HN
- 5Providing a Public Salary History Page3 people · 6 points · first shared 2021 · discussion on HN
- 6Why I Actively Discourage Online Tooling like jwt.io and Online JSON Validators2 people · 213 points · first shared 2020 · 164 comments on HN
- 7Why I recommend Renovate over any other dependency update tools2 people · 185 points · first shared 2024 · 73 comments on HN
- 8Learning a new language, or how I gained familiarity with Go2 people · 120 points · first shared 2022 · 56 comments on HN
- 9Google confirms microformats are still a supported metadata format for content2 people · 102 points · first shared 2020 · 40 comments on HN
- 10You're not mature enough to release your first version as v12 people · 21 points · first shared 2024 · 15 comments on HN
- 11IndieWeb: Owning Your Data and Being the Change You Want to See in the Web2 people · 8 points · first shared 2019 · 1 comments on HN
- 12Blogumentation – Writing Blog Posts as a Method of Documentation2 people · 7 points · first shared 2018 · discussion on HN
- 13Worries about Open Source in the age of LLMs2 people · 7 points · first shared 2025 · discussion on HN
- 14Don't do Agile, be agile2 people · 6 points · first shared 2024 · 1 comments on HN
- 15Go 1.24's `omitzero` is another one of the best additions to the ecosystem in y2 people · 5 points · first shared 2025 · 2 comments on HN
What HN people wrote when they linked it
jamietanna · 2026-01-18
Always happy to self-promote!
Website: https://www.jvt.me (used for blog, but I also use as an IndieWeb site, so I i.e. reply to social media posts from my website, and they're syndicated out to the different platforms)
Blog: https://www.jvt.me/kind/articles/
Archives page: https://www.jvt.me/archives/
Feeds: https://www.jvt.me/subscribe/
eitland · 2020-04-27
See https://www.jvt.me for some really interesting examples of what can be done on the indieweb now. (I found that site because he shared a link to a post I wrote.)
Edit: an earlier version of this post said I found it in the referrers log. It seems I was wrong.
pfix · 2024-04-12
Because it's linked in another post right now:
If you feel confident that renovate[1] pull requests can be merged without review on a green pipeline, you have 100% confidence in your tests ;-)
My first context was that way.
[1]: https://www.jvt.me/posts/2024/04/12/use-renovate/
hunter2_ · 2024-01-03
You could store all state in the URL fragment. Maybe each key is a sound and each value is the volume, like /#whale=5&fire=8 or whatever. Call replaceState (better than pushState to avoid polluting the back button history with every little tweak) whenever the user changes something. On page load, read from the URL fragment using window.location.hash and then sharing is just a matter of copying the URL, which could be done entirely in browser chrome, and/or via a "share" button you provide.
These might help:
https://www.jvt.me/posts/2019/08/01/node-parse-url-fragment/
https://stackoverflow.com/a/66416539
metadat · 2022-10-11
Did you see this thread today?
https://www.jvt.me/posts/2022/09/21/year-later-salary-history/
https://news.ycombinator.com/item?id=33168697
In any case, here's mine to get you started:
$950k this year, Tech Executive, Mid-peninsula in the Bay Area.
Almost all this currently goes to the bank paying down a mortgage. Money is so dumb.
lichtenberger · 2022-05-10
Why would it make more sense? You'd first have to sort the keys, then pretty print, then diff:
https://www.jvt.me/posts/2020/08/24/pretty-print-json-diff/
I'm also using a JSON-diff format in my data store[1], which is accumulated during insertions/updates/deletes in-memory and serialized during a commit, admittedly for large JSON instances (a few Gb and much more).
[1] https://github.com/sirixdb/sirix
jhatemyjob · 2022-05-08
My god. They are doing you DIRTY. 8 years of experience and only making 90k euros??? My first job out of college i was making $105k. OP should be making AT LEAST $400k by now.
Reading his compensation history is making me depressed. What a waste of a career! I would take this page down and switch jobs ASAP. You could easily make 3x your current income. https://www.jvt.me/salary/
unsungNovelty · 2022-02-19
I started blogging after seeing a similar post by Jamie Tanna - https://www.jvt.me/posts/2019/07/22/why-website/.
I wrote something similar - https://www.unsungnovelty.org/posts/11/2019/why-do-i-host-a-website/
And I hope somebody else will get inspired by these as well! There are a lot of personal blogs still BTW.
And for those who plans to write. Creating a blog is easy. Maintaining it is the hard part. Irrespective of your experience and topics you want to share, just keeping the website and writing is hard. Do keep in mind so that you will prepare well for this. :)