Hard truths about outsourcing: you’re always dealing with a cultural, political, and legal gap.

Stuff that’s hella-illegal, that not even the remotest WFH citizen would ever try to pull, might look very tasty from another perspective. Economics that favour that cheap labour also means even marginal scams can seem wildly tempting on the other side.

Non-existent AFAICT, files saved as ‘.py’. I use Jupyter primarily with F#, the multi-language support is huge.

Turns out everyone was completely wrong except for that one guy working in Haskell.

Tale as old as time.

Java was probably close to 50% of the job market at some point in the 2000s and C significantly dried up with C++ taking its place. So I'm afraid everyone was right actually.

To be honest, I'm convinced the reason so many people dislike Java is because they have had to use it in a professional context only. It's not really a hobbyist language.

Just for the record, I don't think C ever dried up in the embedded space. And the embedded space is waaaay bigger than most people realise, because almost all of it is proprietary, so very little "leaks" onto the public interwebs.

Believe it or not but there is plenty of Java and C++ in the embedded space. It’s far from being a C fortress.

Java in the embedded space? I believe you, but I know nothing about this area. Can you share some examples?

Kafka also provides early architectural scaffolding for multiple teams to build in parallel with predictable outcomes (in addition to the categorical answers to hard/error-prone patterns). It’s been adopted in principle by the services on, and is offered turn-key by, all the major cloud providers.

Personally I’d expect some kind of internal interface to abstract away and develop reusable components for such an external dependency, which readily enables having relational data stores mirroring the brokers functionality. Handy for testing and some specific local scenarios, and those database backed stores can easily pull from the main cluster(s) later to mirror data as needed.

> WFH only, limit stress, run away from job if things go bad again

I’m facing a similar set of health-based restrictions, it’s edifying and impressive how you’ve pushed through. I’m curious: how do you broach this with potential employers and shape your job search/career path around it?

Applying for pure remote positions puts one in direct competition with younger people who can pull obscene hours with no accommodation needs. Leading with disability/accommodation needs feels like the opposite of the ‘best foot forward’ honeymoon phase salesmanship associated with new jobs, and kinda soul crushing regurgitating the circumstances for chronic illness while hoping for a job. And uncontrollable management changes can eliminate medical protections and acceptable working environments, leading to an enhanced need to be able to hop jobs (exacerbating both the previous situations).

I’m fortunate my primary skills are amenable to straightforward accommodations, but you gotta get the job to do the job…

> kinda soul crushing regurgitating the circumstances for chronic illness while hoping for a job

I have to do this every time now because I have a resume gap. I don’t have to explain in detail, but even revisiting those three years for a brief explanation sucks.

I’m sure there’s an implicit realization that I will likely ask for accommodations when I explain the gap which likely reduces my chances of being hired.

> I’m curious: how do you broach this with potential employers and shape your job search/career path around it?

Could you get the job without these conditions and then drop the bomb on them as a disability accomodation

Sounds like a fully functioning feature to me: “make up a task to force the project managers eyes to glaze over” ;)

“Quick, Claude, what have I supposedly been WorkingOn all morning? … ‘Blockchain Token Configuration Update’, perfect!”

“A good engineer will solve your problem in 5 days. A great engineer will spend 3 days figuring out how to solve it in 2.”

...and will also have a deeper understanding of the problem that will help solving other problems down the line?

Show up at a meeting looking like you wet yourself, it’s all anyone will ever talk about.

Show up at a meeting where a whole bunch of people appear to have wet themselves, and we’ll all agree not to mention it ever again…

Behaviour Driven Design, following Test Driven Design practice, can create a living specification. Human readable domain exploration, human-readable criteria, and direct links to the test harness to demonstrate conformance and domain capabilities.

This gives you verifiable set of spec documents (BDD reports for integration tests, acceptance tests, domain requirements, etc with green/red status), to iterate and collaborate on without requiring undue upfront work separated from the actual product. ‘Agile’, JIT, YAGNI-aware, specifications, no waterfall necessary.

You’re describing core features of Domain Driven Design.

Innovating, evolving, creating, and capturing new domain concepts to create Blue Ocean solutions inside and outside the Enterprise. Iterating on core concepts, via subject matter expert led/involved discussions and designs, and using new concepts to better articulate the domain. Managing that change over time and accounting for ontological and taxonomical overlap versus Enterprise System development needs.

That’s the foundation that can actively copy insights, and doesn’t rely on Immaculate Specification or premature data modelling. No need to start over, thanks to clearly separated concerns.

Note: copying an insight is a far cry from having the wherewithal to make that insight, there are numerous downstream benefits to articulating your business domain clearly and early.