OS/2 Museum -- https://www.os2museum.com/
Fun With Virtualization -- https://virtuallyfun.com/
The Old New Thing -- https://devblogs.microsoft.com/oldnewthing
The Byte Cellar -- https://bytecellar.com/
McMansion Hell -- https://mcmansionhell.com/
James' posts were very inspirational to me at the start of my career in games, I was very sad when he decided to stop but at the same time it seems like he covered a lot. I read them all again from time to time.
https://solar.lowtechmagazine.com/ -- An assortment of low/high tech cool things, with a bent towards environmental preservation.
https://100r.co/site/home.html -- A blog by indie software developers who live on a boat.
https://hackaday.com/ -- Self describes as "Fresh hacks every day". It's an accurate description.
https://drewdevault.com/ -- A blog about FL/OSS software and technology.
Edit: See 4ad's comment here: https://news.ycombinator.com/item?id=24539935
> In the interest of discussion and discoverability, I urge the commenters in this blog to write a synopsis to each blog instead of just dumping a list of blogs. Or worse, a list of XML feeds (!).
It appears to be up now though.
It's hard for bloggers with self hosted blogs to get discovered and reach a big audience. So a lot of them end up moving to a platform like Medium which gives them the audience. But they in turn give up their identity and content. diff.blog aims to fix that by solving the discoverabilty problem of self hosted blogs. diff.blog is not anywhere near in terms of the audience size of Medium at the moment. But it has been growing steadily since I launched it an year before. Hopefully it will come close one day :)
I want to open source the project at some point. My full time job is working for an open source project. Open source projects require a lot of time and attention from the maintainers to make it sucessfull. I am not ready for that yet. But hopefully oneday.
Beautiful design and excellent deep dives on technical topics that interest me personally (Postgres, web architecture, etc).
Why should you read it? You should read it if you're interested in learning about ideas from finance, business,science and technology that can be applied. I also write about ideas and concept that I originated.
Who am I? I am a software engineer who loves learning about all things business, psychology and science. I also built a small startup in Europe with my close friend while I was in university.
Some of the themes I have touched on are:
1. The price you pay for your first major project https://leveragethoughts.substack.com/p/paying-a-premium-on-...
2. Why it sometimes pays to leverage ideas that have worked https://leveragethoughts.substack.com/p/originality-is-not-t...
3. The importance of showing your work to the right audience https://leveragethoughts.substack.com/p/cracking-the-who-you...
I don't think I was, until now.
I think I'll be adding this to my reading list
Don't understand anywhere near as much of what Ken writes as I would like to, but seeing the die shots he gets and his analysis of awesome old devices is super fun.
EDIT: Added some more links which i found interesting from other comments.
I'm "using" Fraidycat, but it kind of stop working since the last update :/
Even though it is mostly about gaming history, his writings on the history of Atari, Commodore, Apple, IBM and Microsoft, and the people behind them are absolutely fascinating.
A Collection of Unmitigated Pedantry - https://acoup.blog/
And of my favourite posts:
Http://marginalrevolution.com is great and has been mentioned at least once already.
As a Software Engineer I check this one occasionally and read through the backlog
They don't go so much into the soft skills that are required and often the toughest part of the transition. That's where Alison Green's column (Ask A Manager) is great. (She's also written some books but I have not read them. I imagine they're great too.)
I'd recommend signing up for the newsletter and then simply reading it daily as a sort of game or quiz. Imagine you're confronting the situation described. How you would deal with it? Then compare your response with hers.
You'll soon identify some common fairly obvious techniques that will resolve 90% of problems. Probably the two most common ones:
- Did you clearly state your expectations?
- Did you communicate your concerns calmly and directly to this person?
Finally, this Hacker News thread from years ago addresses exactly your situation:
See in particular jbob24's comment.
Congratulations and good luck!
https://slatestarcodex.com <-- Currently unavailable
1) daringfireball.net - mainly Apple related
2) http://highscalability.com/ - All things tech
Farnam Street, Shane Parrish [farnamstreetblog.com/blog]
Less Wrong [http://lesswrong.com/] [lesserwrong.com]
Raw Thought, Aaron Swartz [aaronsw.com/weblog]
Slate Star Codex [slatestarcodex.com]
Melting Asphalt, Kevin Simler [http://www.meltingasphalt.com/]
Essays, Paul Graham [paulgraham.com/articles.html]
Minding Our Way, Nate Soares [http://mindingourway.com/]
Ribbonfarm, Venkatesh Rao [ribbonfarm.com]
Overcoming Bias, Robin Hanson [overcomingbias.com]
Shtetl-Optimized, Scott Aaronson [http://www.scottaaronson.com/blog/]
Raikoth, Scott Alexander [http://web.archive.org/web/20140220082152/http://raikoth.net...]
Heterodox Academy [https://heterodoxacademy.org/]
Hacker News [https://news.ycombinator.com/]
Worrydream, Bret Victor [http://worrydream.com/]
Naval Ravikant [https://startupboy.com/]
Unenumerated, Nick Szabo [http://unenumerated.blogspot.com/]
Simply Statistics [https://simplystatistics.org/]
Chris Olah [colah.github.io]
Marginal Revolution [marginalrevolution.com]
Project Syndicate [project-syndicate.org]