maxFlow

Coding in the flow state has always been appreciated, it's just been surpassed by a new technology.

Your brain can still "just click" with agentic coding. But it will have to be at a higher level of abstraction. Perhaps the "click" feels different, and will take some adjusting to.

Getting Lovecraftian vibes.

CS already is the super-degree.

Hi Peter. Thanks for your AMAs, always a source of great value.

A couple of questions from me:

1. Which would you say are the top spececializations within tech that employers are most willing to sponsor visas for nowadays?

2. Would you say the willingness to sponsor tech professionals has lessened somewhat as of late? Given the economic climate, opportunities to hire remote globally, etc.

3. Are there any impactful immigration reforms we should keep a watchful eye for, vis a vis the 2024 US presidential election?

Thanks & all the best.

GeeksForGeeks is the bane of my existence and IMO a symptom that the entire system has perverse incentives. Fortunately, I've moved 90% of my code inquiries to LLMs, to great success.

Currently listening to the LOTR audiobooks narrated by Andy Serkis. Highly recommended. His characters are heavily influenced by Peter Jackson's movies; it put me off a bit at first, but I've really come to like it now.

> It would be useful to give more clarity around your thoughts on the "Data Engineer" role. Is it also in decline? Is the market as a whole in a relative decline?

My thoughts: the tech job market as a whole has been in decline, as unanimously observed. There may be some signs that the slowdown is abating though. Next 6-12 months will be key to see how DS and DE rebound (or not).

> Most businesses' data engineering needs have been solved or will shortly be solved by managed services that 10 years ago would require endless and extensive self-built ETL pipelines, databases and tools. For the exceeding majority of businesses, this means they can and should focus on building capacity for business logic, analysis and predictions instead of data engineering.

Could not disagree more with your take of "DE demand will decline due to DE needs being already solved for most businesses". Apologies, but have you ever worked as a data engineer or even close to one? Pipelines break, requirements change, businesses expand, and infrastructure needs to be managed and optimized, etc. ETL processes, in the wild, are decidedly not one-off affairs.

Thanks for mentioning this. I don't get to do much writing in my time off work, since that time is devoted to (more) coding to try and make my side project into a business. So what I do to compensate is I make an effort and write all commit messages, descriptions, code review comments and documentation as if I were writing for an audience of top engineers auditing my work. I find this approach makes me enjoy the process more, be more deliberate about my actions, and how I communicate them. Even a dull runbook can be beautifully written.

Pick two books at random and start building as you read them.

Do you want to build a profitable business or do you want to theorize how to build one?

I'm in a similar situation to yours, and I've kind of settled on a similar approach: put out the most pressing fires and reassess 3-6 months down the line. At first I had thoughts to refactor but now I just don't want to deal with the complexity, not to mention I have end-users pressing me. I'll have to tolerate the spaghetti, but at least make it produce correct output.

Best of luck with the migration to DO :)