8,862 karma · joined October 23, 2014
Note: Any comments on this site attributed to me are my opinions and not those of any current, past, or future employers/clients. Consider yourself so notified.
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.
edit: typo
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.
- 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)
Isn’t that literate programming or in similar vein?
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
And usually projected as ensuring bus factor > 1
``` 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! ```
:-)
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 :-) !!!
Can you share some details, I was planning to try Windsurf during the holidays but may skip if you have negative feedback that may be agreeable. Thanks.
This, a million times, and is often overlooked.
In fact, I would say that you should try working it out backwards. Find the place where you will really enjoy to live and find the best possible work you can do aligned with or leveraging your current skills with decent prospects for future growth.
Twice in my career, I found work that was interesting but in places where I didn't like to live. And living well is way more important than working!!!
Then unless IP issues restrict you from using ChatGPT, ask it to summarise your work and also split the summary into weekly, monthly, year logs. Read that summary and it can serve as a good reminder of what else ancillary work you did (design work, authoring docs, conducting trainings etc)
Of course, all of this is assuming you are an Individual contributor whose major work is design and implementation. Otherwise YMMV.
Just a suggestion. It may instead be preferable to put a `Other Work Experience` section with a bullet point highlighting either tech skills or domain or a mix with the duration.
``` Java, J2EE, .NET
Various Companies
mm/dd/yyyy to mm/dd/yyyy
Enterprise app development
- Design and implement various travel, finance applications/modules ```
edit: formatting
It takes a lot of experience, wisdom and courage to accept and fix that. What other factors do you think helped you fix it? Financial security which allows one to take breaks or top notch in demand skills that helps one find a new job quickly come to mind, but it could something non-material and I am interested in hearing that. Thanks for sharing your journey.
Nothing of the sort really, at least in the teams/org I work in. As long as you are performing to expectations i.e good and hardworking as you put it, it's just a matter of letting your manager know and the rest is taken care of.
>> I am guessing that there is a tactical way to do that without telling them that
You can always ask during the interview stage about relocation opportunities, how these are handled and how easy/hard it is to relocate. More often than not, the manager/HR will be transparent about it. If the manager/HR is curious as to why, you can always say that you would like to experience working in the US; nothing wrong in that.
More often than not chances of moving to US after working at a FAANG in Europe should be possible unless your company doesn't support relocations; it's better to be upfront in the interviewing stage if you want to do that.
I have never aimed for PR in US so can't speak to that; I may want to move to California only for the weather and the higher salary but my wife likes the UK weather ;-)