HN user

joshSzep

116 karma

http://www.linkedin.com/in/joshszep

Posts11
Comments57
View on HN

I’ve been thinking about how modern family structures seem increasingly misaligned with what our biology and history may have prepared us for. It seems likely that nature "intended" families to be multigenerational, larger clan-like units linked by shared responsibility, proximity, and care.

Modern norms have instead left many parents effectively on their own, juggling full-time work with full-time childcare. If multigenerational living were normalized, the retired could help raise the kids while the working adults focus on providing. That setup allows for more quality time rather than burnout.

This isn’t anecdotal. I didn’t grow up in a household like that. But the research supports it:

1. Older adults living with younger generations experience less loneliness, better mental health, and even longer lifespans. 2. Multigenerational households are more financially resilient, less likely to live in poverty, and able to share housing, food, and caregiving costs. 3. Children benefit cognitively and emotionally from regular grandparent involvement. 4. Multigenerational setups enable parents to stay in the workforce while providing more consistent and affordable childcare. 5. Families in these homes report stronger relationships and better intergenerational understanding.

Of course there are challenges. Privacy, space, and generational conflict are real. But with today's social isolation, rising living costs, and aging demographics, we might want to normalize this kind of household again.

Maybe the future isn't just smarter cities or more automation, but rethinking how we live together.

---

*Sources:*

1. https://www.ncbi.nlm.nih.gov/pmc/articles/PMC9876343/ 2. https://www.pewresearch.org/social-trends/2022/03/24/the-inc... 3. https://academic.oup.com/psychsocgerontology/article/75/6/12... 4. https://www.gu.org/app/uploads/2021/03/FamilyMatters2021.pdf 5. https://www.cdc.gov/nchs/data/databriefs/db255.pdf

I am very impressed and I am getting great results for queries like "Show me how to use langchain in python".

However I am disappointed that when I provide a url it can not read the page. Given that this is a search engine I would expect it to be able to read any public URL I provide it. For example I attached a PDF of my resume and provided a link to a public job description and asked it to generate a cover letter tailored to my experience for this position. This is something I have done with easy success with ChatGPT GPT-4o, but Phind throws its hands up. :(

Location: Los Angeles, CA

Remote: Open to remote or hybrid

Willing to relocate: No

Technologies: Python, Django, FastAPI, PostgreSQL

Résumé/CV: https://drive.google.com/file/d/13lFWbghYECCzY8QAEjXcC44RlPd...

Email: joshszep@gmail.com

Hey HN,

I’m a Staff Backend Engineer with 20+ years of experience, currently looking for my next opportunity. I specialize in Python, Django, FastAPI, PostgreSQL, and scalable system architecture. I’ve built and led the development of high-performance applications, mentored engineers, and leveraged AI-assisted development tools to accelerate workflows.

I’m particularly interested in startups or small companies where I can have a high impact, take ownership, and help build something great. I thrive in fast-moving environments and love solving complex problems at scale.

We are loving it and we aren't even using it fully to its ability. For example we do almost no communication in the 'chat' that exists for each issue (in place of comments) since we are a very small team and still are talking mostly in slack about the issues, but I predict as we grow this will become a useful feature for us.

In the meantime we are loving the 'every issue can have sub-issues' and have customized the fields to our liking.

This is a tool with a lot of power. I can see a well-intentioned PM going crazy with it, but for our needs I was startled with how great it is.

pylance is pyright under the hood, isn't it? it's the main reason I use pyright over mypy: I work in VSCode and I want compatible type checking

excellent! I have been using Cursor for the last couple months after a year of using GitHub Co-Pilot.

it's not even a fair comparison. Cursor is just so much better, especially comparing it's chat quality to GitHub Co-Pilot chat.

DMNO looks wonderful. I would love to use it for a monorepo which is using TypeScript/React for frontend services and Python for the backend. Native Python support please, `user_demand += 1`

And the following examples show it is not. While it is pretty straightforward to add `uv ` in front of any pip calls, it is not API compatible.

By itself it is fun but ineffective. I combined it with twice a week personal tutoring sessions. Now I have someone to explain the grammar and the sentences in Duolingo start to make sense. Start to pick up vocab quicker.

I really love Duolingo and wish it didn't get so much hate.

Excellent comment, inimino.

Over ten or twenty years, the difference between these two habits is night and day. The people who read the documentation first, and only then ask for help, and the people who ask for help first and get it and so never read the docs, end up in a totally different place with respect to overall confidence and comfort with the tools.

Ooof! This one's hit home.

Because ain't nobody got time for that. ;)

More seriously, I think that we have been trained to rely on just in time searches (or ChatGPT sessions) when we encounter the next thing we need to learn. RTFM is just so time consuming and I personally don't recall everything I have read, leading me to rely on search/AI to re-learn the next thing just in time anyways.

In some ways this is a vast improvement, which is why it's the default behavior now. Why cream your brain with information you might never use?

But it DEFINITELY has a weakness in that you don't know what you don't know. I never knew about this 'trap' trick, for example... and I didn't know I didn't know it, despite it being something I see as quite useful.

Side note: I think RTFM has historically meant "try to find the answer first before asking for it", leading to me designating LMGTFY (Let Me Google That For You) as the modern equivalent in this just in time searches reality we live in. I wonder how long it will be before we start saying LMAAIFY (Let Me Ask AI For You)...

Nix vs not Nix seems like a parallel to Infrastructure As Code (terraform for example) vs Cowboying the AWS Console. Is that a fair comparison?

I recall Yelp's onboarding to be the best I've encountered anywhere. Some highlights: - Before Day 1 I received a pleasant email on my personal account that walked me through Day 1: simple things like getting a badge, finding my team, etc was stress free as a result. - There was a "space camp" presentation to give me a high level overview of the technology and culture, as well as step by step instructions guiding me through my first commit and first deployment (both of which are expected within the first week) - I was assigned a dedicated mentor on my team. I'm someone who often wants to "figure it out" on my own as a response to my "asking for help" anxiety. Having someone assigned to answer my questions and who micro managed me through the first couple weeks (in a good way) really helped me get up to speed much faster. - Always a (expensed) team lunch to welcome in a new hire.

Anyways, I'm now in the "remote till I die" camp and I have been struggling to translate this into a remote first company. It can be challenging to make a new remote team member feel comfortable, productive, and "safe" without that physical presence.

The government can't really enforce bedtimes, but it can enforce this.

And as someone who has identified as a night owl my whole life I am thankful that future night owls may be less forced to accommodate the morning bird world we live in.

First priority, IMHO, is to support running on Linux and Apples.

For an open source business model consider "open core". Open source the core engine, and charge for additional features. I would recommend SQL Server and Oracle be paid enhancements as companies in that ecosystem are used to paying for tools. Keep postgres/MySQL/SQLite, etc open source as they are tools that developers using open source would be using.

Then charge through the roof for the additional features. I recommend at least two tiers: a lower price for access to the premium features, and an "Enterprise" tier which adds in support guarantees.

Don't do a one-time payment either. Make it a subscription to receive new updates etc.

The low tier could be ~$50/month, the high tier can be "contact for pricing": but if contacted start the discussion at $1000/month. Then allow them to negotiate a lower price, perhaps with your absolute floor being $500/month.

This is all armchair advice, so take it with a grain of salt. But I hope it is helpful.