Sign In

Jean-Baptiste Quéru

Software Architect at Aescape

Jean-Baptiste Quéru, known as JBQ, is a Principal Engineer at Aescape. He has a robust background in technology, having worked extensively on operating systems, browsers, and software development kits (SDKs). His academic foundation is heavily rooted in mathematics and computer science, which he pursued through various rigorous courses during his university education.

Born in France, Quéru is currently transitioning from Spokane, Washington, to Preveza, Greece. He identifies as a veteran and is also a highly sensitive person. Fluent in both French and English, he engages with the tech community through various platforms where he shares insights about technology and personal experiences. His LinkedIn profile reflects his professional journey and interests in programming and engineering .12

Highlights

Jul 26 · linkedin

More job awesomeness at Aescape (in my team!)

We're hiring an engineer in NYC to work on our Android AOSP codebase. This is a broad role, encompassing processes, tools, and technology, in close collaboration with the people building the actual hardware that your code runs on. And the hardware behind that hardware. And even the hardware behind that as well, if you really want to be curious.

This is directly in my team, i.e. for better or worse you'll be working closely with me, under my manager who is awesome (but then everyone at Aescape is awesome!)

Of course, free massages are included. Because they are anyway, and because you need to test that new AOSP build, of course.

Details are in the job posting, including the salary range.

Jul 21 · linkedin

Assumption is the maker of all failures.

I like to read incident retrospectives. Specifically, I like to try to express what went wrong in terms of humans making invalid assumptions, consciously or unconsciously. That is how I learn how to recognize the assumptions that I or the people around me might be making as we make decisions.

OS vendor assumption that 3rd-party code running unprotected in the kernel would never crash? Bad assumption, extremely bad.

Vendor assuming that their C++ code would never have memory errors? Bad assumption.

Vendor assuming that they don't need a staged rollout, and immediately deploy to 100% of the fleet instead? Bad assumption.

Vendor assuming that they can roll back if something goes wrong? Bad assumption.

The list goes on and on.

I have seen many invalid assumptions that ended up turning into significant issues. I have made quite a few such assumptions myself. I'm sure I still am making such assumptions. Because only those who do nothing make no mistakes. But I'm trying to get better, I'm trying to learn.

Related Questions

What projects has Jean-Baptiste Quéru worked on at Aescape?
What operating systems has Jean-Baptiste Quéru contributed to?
How did Jean-Baptiste Quéru transition from the USA to Greece?
What are Jean-Baptiste Quéru's main technical interests?
What is Jean-Baptiste Quéru's role at Aescape?
Jean-Baptiste Quéru
Jean-Baptiste Quéru, photo 1
Jean-Baptiste Quéru, photo 2
Add to my network