would you mind sharing how you reduce it. I am testing hacks like asking to draw in block diagrams, write like RFC, write like algo and pseudocode

context engineering, with guidelines drawn from examples in my own projects

more up front planning, in a markdown file, multiple sessions

review processes, for the plan and then the code

the "recursive self improvement" (at the harness/context engineering level) feels like it is starting to kick in

But how are you scoping the features these days? Unlike back in the day, these days a feature is equivalent of research paper

if you prompt differently, you can instruct them to work on small things

they have a strong tendency to over engineer (volume), prompt against this - in permanent files like AGENTS.md or per-session in follow on messages

Yeah this over engineering is really annoying bit

I agree with this. We can think of anything and nothing can prevent that at all. I have to go therapy to be told, it's okay to not think 24/7.

One thing that is working for me is simply getting a handheld and playing good old video games like in old days.

It is something I look forward to everyday because I can be anywhere and play anytime.

It is simply best hack I came up with.

Any games with "online" element is slop and avoid that toxicity.

very compelling. do the nations that never participated in colonization -- such as Switzerland, for example -- get exemption, or is the blood guilt shared among all wh*te people?

say that to visa laws that were designed by your ancestors that carry around the world. Say the same to currency arbitrage, freedom of mobility and everything that you enjoy for granted in protected walls.

The reason remote worker can out compete you is because of this currency arbitrage you designed. Your pennies goes a long way in this so called third world. Your one day dinner at nice place is a months salary for family of 4.

Seriously, if you can’t compete globally, then you don’t deserve your privilege of being born in rich world.

Stop labelling other humans as serf when your entire wealth was built on shaky foundations.

You == not you the person, but the government and laws.

Once again *I* didn't design and of it. Leftists don't like hearing that.

The fix would be obviously to control and limit foreign workers by regulating companies.

Oh my god!! You nailed it. I see two categories in tech. One the builder, innovators, tinkerers, those who just wanted to use tech to draw their ideas to life.

Then other is artisan, those who took pride in organizing and craft.

Second one is having miserable time. The former like me are having a blast. I love tech for that reason.

I stopped talking to people who think LLMs are waste. It's because they don't even touch it. They think it's a taboo to touch it.

So anything in tech is exciting because it enables us to do so many random things. Wish more people learnt about it.

>They think it's a taboo to touch it.

I'm in a tricky situation as someone out of a full time job. Where "I love AI" might be a red flag that I'll use it to cheat. So I'm even more hesitant to make use of it.

It seems like both of us have similar definition of an average. That's really cool that you got my idea of being average. Thank you!

So do you have any clue how I can optimize the position in the industry? I am interested in the most of the subtopics in the field of computer science. I just want to find a route with highest reward for an average developer.

Apparently average research engineers makes a lot compared to say web developer, but the route requires PhD.

What do you think is a good track?

Those "average" PhD researchers are in reality all very smart and hard working people. If you want big salaries, people who get them often have PhD degree from top20 universities in the world. They will be your competition when interviewing.

In general, if you want to maximize money, it does not make sense to go into any hard and niche fields (graphics, machine learning research etc.) because they're filled with very talented enthusiasts, and if you're not that, you will have a very hard time even being average in such fields. Not to mention that such fields often (but not always) pay less that your run of the mill backend development job, and have 1000x less open positions, which means it's harder to apply for jobs, you may have to move more often etc. It's basically all downsides pretty much, and the only upside is being able to work on your passion - which is what motivates people who get into those fields.

> It's basically all downsides pretty much, and the only upside is being able to work on your passion - which is what motivates people who get into those fields.

Yes!! I can totally relate to what you are saying. I got started because I was interested and I am still passionate about it. But there is only so much that I can do. It just doesn't make sense for me to continue for PhD because even with PhD there is no guarantee that I would be able to get somewhere as I am definitely not someone coming from those top20 universities.

So by definition I rule out the chances of being an average research engineer. That's one clarity! Thank you!

Since I have most background in hard niches as you mentioned above, is there a way to transition to something else? What would the possible path be like if my ultimate goal is to become staff engineer or principal engineer?

This really depends on your previous experience. If, for example, you have previous experience with C++ (which is what is often used in those hard niches), it would make sense to just apply to generic C++ roles, and work your way up to high salary by getting promotions or changing companies. If you're in the US, it probably wouldn't hurt to apply to FAANG-type companies, as they rely heavily on the leet code, so your lack of concrete experience in things they do will not be a big problem (likely will just get you a low pay grade, but you can change that with promotions later).

I've met several PhDs in "data scientist" positions that write complete garbage code. Simply having a PhD (or any other degree) doesn't mean you'll be a good engineer.

Thanks for letting me know!

Okay! This makes sense. Culture is important!

However, I kindly request you to not conclude that wanting to be average doesn't mean not having interest in the field. It's the contrary. I am so invested, I know what mind blogging things people can do. And I also know I will never be able to reach where these people are.

Hence, I want to understand a way to find the balance. It's okay to be curious and learning. Also the fact life isn't fair for everyone. For some it comes easy, for some it may take lifetime.

So it likes transition into a business roles or try to be CEO.

My question, is there no way to be eternally stuck as "senior/staff engineer". I do not want anything beyond that. The salary of an average senior/staff engineer is always greater than median salary of the country.

That should solve all the living expenses.

You can if course stay at that level forever.

Living expenses may or may not be constant. If you have a family expect them to increase alot while having less time to keep up with tech.

Oh no, I thought the salary would be adjusted for inflation. Are there no social safety nets? This is really sad to know that salary isn't adjusted for living expenses!