HN user

rluhar

174 karma

http://thinking.luhar.org

Posts9
Comments80
View on HN

I've read both versions of the book and would strongly recommend the audiobook version that came out last year (it's available on Spotify). They did a good job handling the redactions and the narrator really brings the protagonist to life. A very strong recommend if you like audiobooks.

I am building QuietReads (quietreads.com) - a single-player book tracking app with an AI assistant.

I got tired of the gamification and social elements of Goodreads, StoryGraph and others. I don't care too much about reviews, but do care about engaging deeply with what I am reading.

Lot's to do still: - Refining the experimental MCP integration so I can bring my bookshelf into my AI assistants - OCR to build notes from screenshots - Voice notes

I wrote a little about why I am building the app here: quietreads.com/about Thoughts on building the app: https://thinking.luhar.org/2026/01/building-at-the-speed-of-...

Accelerationists and doomers both assume AI means rapid change. But what if the incentives point toward stasis instead? A world frozen in place by those who got there first.

I bought a Nikon FE2 recently from keh.com. There are plenty of manual focus film SLR cameras available. You may also want to try your local camera store. Mine has a good selection of used cameras and lenses. Things are more expensive than they used to be but there are still plenty of options available.

Can confirm that Ethan Allen is still selling decent, US made, furniture - though at high prices. We got a couch for an awkward sized space from Ethan Allen and were very happy with the shopping experience, installation, and the quality of the furniture.

TLDR - Credit Suisse has been a sh*t show for over a decade. This has been coming for a while.

Credit Suisse is in investment banking and wealth management. It does not have a significant retail presence (EDIT - outside of Switzerland). Credit Suisse has also had a number of accounting, risk management, and other scandals over the last few years. They were bailed out late last year by a fund linked with Saudi Arabia who took a ~10% stake in the company. Today, they (the Saudi fund) refused to inject more capital and the shares have collapsed.

I am in a similar situation to you - 2 year old and a newborn and feeling a little burnt out at work. The way I have been coping is just realizing that at this stage the timelines for pretty much everything shrink from months or years to hours and days. You need to focus on getting through the day at work, keeping sane, and being present for your partner and kiddo. Your work might not be pleasant, but you have been there for ten years so you should have a good idea of what your MVO (minimum viable output) is. I think the Kanban approach of reducing the Work In Progress is the way to go. I have made a conscious effort to not worry too much about big picture "career questions" and just focus on the task at hand. Our first kid is young enough for me to know that things become more manageable once the kid is sleeping 5-6 hours at a time. For us, this happened around 4 months in. Good luck, and I wish you and your family well!

I think a key skill to evaluate is the "learning how to learn". Can a developer pick up a new language and are they flexible enough to get their head around a different concept. I agree that we need to support learning - knowledge can be acquired, but the willingness to go outside your comfort zone is something that is a bit more innate.

I read the book when it came out. It is an interesting snapshot of a particular period in technology history but, as in any memoir, it comes with heavy dose of the author’s personality. I finished the book because the time period is interesting (social media maturing, Facebook and Twitter both growing, the start of “SV bro” Culture etc).. but I found parts of the book incredibly, teeth-grindingly irritating. YMMV.

The Knowledge Project podcast is awesome. Here are some snippets that I found very useful.

On starting his company in a secondary market: I do think that there is an almost complete difference between how you build a company in a primary talent market and sort of secondary talent markets. For instance, one of the biggest differences in secondary places is, if I hired someone, the chance that we are going to still work together in a decade from now is super high.

Hiring for future potential It means that it’s a much better idea to hire for future potential rather than for current skill. Once you do that, what you realize is, a dollar invested into helping to train people or even subtle things like making sure that next to any junior programmer, like for every five junior programmers in a team, you have one person who can become their mentor—these basic ideas all start having way more dividends

On building a hiring process for a learning organisation ..we have a hiring process that really, really finds people of high future potential. And then, we try to help them reach this potential 10, 20 years earlier in their career than they ever thought was possible, through coaching, through book clubs, through anything. Fixed vs. Growth Mindsets Everything in Shopify is built around this idea that if someone shows up with a fixed mindset, we convert them to a growth mindset quickly. And then once we have a growth mindset, we fill people with context (i.e. explain what their role is and what they are expected to do).

On the role of processes with an organisation There are three kinds of process. There’s a kind of process that makes things that were previously impossible to do, possible. That’s good. Then there’s a kind of process that makes something that was previously possible significantly simpler, which is also good. However, 99.9% of all process that exists in corporate America is the third category, which is actually just telling people to behave slightly different from what common sense tells them to do.

So we have lots and lots and lots of examples where we just avoided having to create process by just changing the environment in which we all spend our time in.

I am a member of the learning community. I found great value in the transcripts of the Knowledge Project podcasts. The podcast is free but the transcripts are available to the learning community. My favourite recent podcast was with Tobi Lutke (CEO of Shopify) - https://fs.blog/tobi-lutke/. Other podcasts that were super interesting were with Robert Greene, Naval Ravikant and Venkatesh Rao. The forum itself is interesting - there is a regular reading group which I really enjoy as well. It is expensive, but I think it is worth it (or am I simply a victim of the sunk cost fallacy?)..

Use the right tools for the job. If you are running your Python models in containers anyway, a suitable API will work with any backend language. Go and even the JVM (Java / Scala / Kotlin) ecosystem are great candidates. Our stack uses Python (models deployed as dockerized WSGI applications) for machine learning and web services written in Java for the backend. It is relatively easy to get developers who are comfortable in the JVM ecosystem and the tooling available makes it easier to build robust systems.

2. Collect examples. Start with a spreadsheet of data that highlights the data you have available.

This is true not just for data science but when trying to solve any numerical problem. Using a spreadsheet (or a R / Python notebook) to implement the algorithm and getting some results has helped me in the past to really understand the problem and avoid dead ends.

For example, when building a FX pricing system, I was able to use a spreadsheet to describe how the pricing algorithm would work and explain it to the traders (the end users). We could tweak the calculations and make sure things were clear to all before implementing and deploying the algorithm.

Great advice!

Mainly because the market was fragmented and FX had a lot of arbitrary laws (i.e. which currency pairs can be traded, which pairs have a peg against the dollar) and also the complexity of settling cash trades. Looser regulations and burgeoning global trade have provided the impetus for the automation in the FX business.

TLDR: FX is getting to where equities and derivative markets have been for a while

FX is an OTC market. There are no official "exchanges". Most trading happens either on the interbank markets or via brokers like ICAP, BGC, etc.

Over the last few years, the spreads (difference between a buy and sell price) have compressed. FX Clients (i.e. corporations, hedge funds etc.) who would trade directly with their preferred banks; now aggregate feeds from multiple banks and brokers to attempt to get the best possible price.

This automation and increase in client sophistication has led directly to tailored market making and sophisticated risk management. The number of players in the FX market has increased as the technology has commoditised. Things like the latency and quality of your market making feed have become differentiators.

All of the above has resulted in the market going electronic and a massive reduction in the proportion of trades being quoted and managed by human traders. In most banks, market making is now done by algorithms that aggregate market data and other information from a variety of sources.

Traders have either become specialised to niche currencies (Asian, Emerging Markets, etc.) or at dealing with extremely large trades. Their job is now all about determining the type of rate (i.e. which algo) a client should get and how the risk from those trades is managed (aggressively, passively, etc.).

I have worked on FX desks (as a developer) for 10+ years. I have seen spot trading desks shrink incredibly, with old school traders being replaced by quants and quant-developers. The algorithmic trading space in FX is not as sophisticated as that in equities of derivatives, but is getting there.

Finance companies do have incredible technical and regulatory challenges that require good programmers. There are a number of strong programmers who work in finance and are indeed attracted to some of the challenges around finance. I have worked across a number of banks and each has had its own challenges and I have worked with talented and motivated programmers working to solve these.

Return of a King (William Dalrymple 2013) - A book about the Anglo-Afghan wars of the 19th century. To paraphrase Mark Twain: History doesn't repeat, but it rhymes

Being Mortal (Atul Gawande, 2014) - Powerful book about old age and confronting the mortality of our loved ones

The Dark Forest (Cixin Liu, 2014) - Wonderful science fiction from China

The Peripheral (William Gibson, 2015) - Bleak, near future science fiction.

The Water Knife (Paolo Bacigalupi, 2015) - More bleak, near future science fiction.

Just being pedantic here - grand parent post mentions £650 a day, which is around $1000 per day depending on the prevailing exchange rate.

Happy Birthday!

There will always be things that you feel like you should or must be doing when you are 24 or 25 or 65!

Its great that you have found something you enjoy. As you get more experience and explore new avenues, you may find things that interest you more. Be open to change. The peanut gallery will always be there, but the only person you are accountable to is yourself.

The social pressures are a part of the culture, but they are background noise as such and should be treated as much. Focus on what you want to do, and where you are going. The other things will fall into place one way or the other.

You can sync your passwords across multiple devices using DropBox. It will work with IE, FireFox, Chrome and Safari.

It will also allow you to share passwords (via Dropbox) between Macs and Windows machines. It can generate strong passwords as well.

Yes spot on - many restaurants, especially the smaller places do not take credit cards. Even a large chain of Convenience Stores (FamilyMart) do not accept credit cards for payment.

(Way off topic) Japan can be quite strange with banking and ATMs as well. Unlike, for example, the UK, your ATM cards usually will only work on the ATMs of your bank or perhaps in some convenience stores.

For example, my Citibank card only works at Citibank ATMs, and 711 convenience stores, but won't work at a MUFG ATM. You also get charged for withdrawing money outside of "office hours" at an ATM, and some ATMs stop working after 2100.

It was a little bit of a shock moving from London where I walked around with 10 pounds in my pocket to Tokyo where withdrawing and walking around with 500 dollars worth of yen seems pretty normal.

This is quite similar to way convenience stores work in Japan. You can pay at a convenience store and get Amazon to ship your goods to a convenience store. Japan (similar to India) is still very much a cash based society and I suppose some people prefer to pay in cash at a convenience store instead of paying online.

India also has loads of tiny convenience stores, I think this is an excellent idea. It also simplifies the logistics. The eCommerce company only has to build out a supply chain to the convenience store instead of having to deliver to each customer or rely on the Indian postal service.

(I have lived both in India and Japan)