oumua_don17

> Arguing with your boss in private

Never do that if you're working under a toxic boss, in which case arguing in public is better if at all but one should anyways be working hard to find a new boss!!!

There's also Modern System-on-Chip Design on Arm textbook by David J. Greaves and it's available as a free download [1].

[1] https://www.arm.com/resources/education/books/modern-soc

And probably a prototype deployed to production!!!

From my experience, you become a lisper truly when your Lisp image is running for days on end, you miss the live editing power and loathe the exception handling system in other languages. It takes a while and concentrated effort to get you there.

I strongly recommend anyone interested use a Lisp as their prototyping language in their workplace. Another idea is to rewrite a complex component of the software you're working on and rewrite it in Lisp. More importantly ask the questions on Lisp forums especially about using the live editing workflow.

The Chip War

Why should I tell if it's supposed to be hidden? :-)

But here we go, Common Lisp for rapid prototyping at my FAANG job, so I'm actually paid to do that!!!

edit: minor typo

> spending cash on vacuous bullshit and being unhappy at work ...

I don't find anything incorrect in your response per se but I hope those weren't your assumptions about my situation and I didn't specify the details either. I've lived within my means, spend only for comfortable leisure travel, no mortgages; otherwise I wouldn't have achieved FIRE.

Neither am I sacrificing due to work as it's a good team with good WLB, it's just that I'm no longer excited by the work without dreading the Mondays. So as I mentioned in another response it's very likely that I'm actually scared of leaving this comfort level.

How'd you handle the no compete and whatever you do is ours clauses pretty much the norm at FAANG's?

I didn't mention other things like I'm living well within my means, no BS expenses except spending on leisure travel ensuring it's comfortable, no mortgages.

I'm working in good team with good WLB but after FIRE while I don't dread the Mondays, I'm no longer excited by the work. I still am able to make decent contributions to my team.

So may be I'm scared of leaving this comfort level.

Is there an option to buy this book as a pdf?

This is very insightful and also aligns/overlaps with the rather unpopular don't follow your passion mindset. one can still find some work that's reasonably enjoyable even when it's not your hobby or passion; just that such work takes a while to find and might not last forever so you'll be back to square one.

Check this out https://pikuma.com/courses/learn-3d-computer-graphics-progra...

https://duckietown.com/

https://github.com/TheCloudlet/Stratum

Quite a few comments refer to BLFS which is Beyond Linux from scratch https://www.linuxfromscratch.org/blfs/view/stable-systemd/in...

> Claude Codex

Do you mean codex or Claude code standalone without cursor? Codex is OpenAI’s coding tool competing with Claude.

Based on my limited experimentation Claude code is better. I haven’t used any of these coding agents with an ide only from the cli.

All the code in the book PAIP by Peter Norvig.

Any chance you were in one of that infamous orgs?

One should be simply amazed that amidst the AI hype most fail to realise that if it's too good to be true, it probably is! Just waiting for this bubble to pop.

edit: typo

> Migrating away is obviously not an option in 2025 and onwards

Why so? Yes it may seem difficult with lesser immigration friendly sentiments; however that shouldn't deter you.

You haven't mentioned your current situation, your experience etc to give more tailored suggestions. However, if making a living is not a concern for you in Nepal, then that gives you the freedom to pursue contributing to open source projects in subjects/areas (graphics programming may be) of your choice.

Otherwise based on your experience, you can apply to companies in UK and Europe, many will sponsor if you have the right skills and experience. That takes a while but it's not impossible.

Have you explored India as an option as Nepal and India have free trade movement and Banglaore/Hyderabad/Pune are great options if you focus on product and FAANG companies there. This may in fact be an easier route to get valuable experience in a reputed company.

> My age is 28...

And 28 is hardly the age really to worry about moving/not moving, unless there are compelling reasons like having to stay back for strong personal reasons.

- Vim vs Emacs

- Mac HW vs Linux OS (I really want a combo else give me Snow Leopard)

- Staying put vs Leaving/Sabbatical (AI nonsense is boring/burning me out)

> So basically, you write the design doc in English, maybe with some semantics, with some abstract paragraph, some other things which might help

Isn’t that literate programming or in similar vein?

> Of course, exceptional circumstances exist where long hours are required

Sorry, but despite your best intentions, even those long hours are wrong and unnecessary. It's the leadership's planning skills and inability to take responsibility of the exceptional circumstances. In such a situation good leadership just cuts scope without flinching and reflects to avoid a repeat.

edit: typo

Start as early as possible in investing (in index funds) and otherwise being financially savvy. It is very beneficial to realise early on that growing your hard earned money and spending it wisely is way more important as it will in the future lead to some unexpected benefits. Freedom of thought and action!

Yes and it isn’t just a matter of in but when the bubble pops. Then everyone will be hailing apple as the strategic visionary, fun times!!!

> Something to do with status from headcount?

And usually projected as ensuring bus factor > 1

There has never been a rivalry in any sport better than that between Roger Federer and Rafael Nadal.

Not sure if it's appropriate to post ChatGPT's response here, but I gave the same challenge to o3 and it's response was:

``` 2025-07-20 10:32 That’s an exhilarating challenge! But here’s the sober reality:

*1. Scale & Surface Area*

* *Jira* and *GitLab* each represent well over a decade of engineering effort from dozens‑to‑hundreds of developers, QA, designers, product managers, and SREs. * They’re not just web apps—they’re ecosystems: issue tracking, CI/CD pipelines, permissions, integrations, APIs, marketplace extensions, mobile clients, high‑availability clustering, compliance tooling, analytics, and elaborate permission models.

*2. Engineering Effort in One Week* Even an aggressive “strip‑to‑core‑features” build would demand:

| Area | Must‑Have Functionality | Typical Complexity | Realistic Time (solo) | | ---------------------------- | ------------------------------- | ------------------ | --------------------- | | Auth & user management | SSO, 2FA, roles | weeks | 3‑4 weeks | | Issue / Merge request model | CRUD, workflow, attachments | months | 4‑6 weeks | | Git backend or sprint boards | Repo storage or board drag‑drop | months‑years | 8‑12 weeks | | CI runner orchestration | Job scheduler, logs, artifacts | years | 6‑12 months | | Notifications & webhooks | Email, Slack, webhooks | weeks | 3‑4 weeks | | Security & compliance | RBAC, audits, CVE patching | ongoing | Ongoing |

That’s after *scope‑cutting to the bone*—and still well beyond seven days for even a seasoned full‑stack team.

*3. Minimum Viable “Clone”* If the goal is a demo that looks Jira‑ or GitLab‑like and handles the absolute basics (login, create issue, simple Kanban board or Git repo viewer), you’d still need:

* *Pre‑built OSS components* (e.g., Focalboard, Gitea, Drone CI) * *Glue code* to stitch UI, auth, and database models * *DevOps* for cloud deploy, backups, SSL, monitoring * *Acceptance tests* so the demo doesn’t fall over during the pitch

With a well‑coordinated *5‑7 person tiger team*, an MVP façade might be shown inside a week—but it would be fragile, feature‑poor, and nowhere near production‑ready.

*4. What \$1 million can buy fast*

* *Fork & skin* an existing open‑source platform (e.g., Forgejo for GitLab‑like, OpenProject or Plane for Jira‑like). * Hire a *dedicated squad* (engineers, designer, DevOps) on a 3‑to‑6‑month crash program to reach parity for the specific subset of features you actually need. * Budget for *security audit, uptime SLA, and ongoing maintenance*—because the first release is only the beginning.

*5. Suggested Next Steps*

1. *Clarify scope:* Which exact capabilities do you really need on Day 1? 2. *Select a foundation:* OSS codebase vs. greenfield build. 3. *Form a team + timeline:* Realistically 12–24 weeks for a hardened v1 with a mid‑sized team. 4. *Milestones & deliverables:* Demo, beta, public launch, enterprise tier. 5. *Contingency planning:* Budget for security, scaling, and feature creep.

If you’d like, I can help map out a detailed project plan, assemble a tech‑stack recommendation, or break down resourcing and costs. Let me know how you’d like to proceed! ```

:-)

I read this blog post, then went for a walk with my spouse. On the way back, took a photo of a popular building in my city. I am not sure if it's just the way I took the photo but o3 tried for 14 minutes and then gave up with Error in message stream response.

It also curiously mentioned why this user is curious about the photo.

I relented after o3 gave up and let it know what building and streets it was. o3 then responded with an analysis of why it couldn't identify the location and asking for further photos to improve it's capabilities :-) !!!

Ironical that two companies led by the same CEO, the first one already acquired by BC and now the second one too!