Hi Olivier,

These are just my thoughts and they are based on nothing tangible, other than that I own a tech company and hire developers and designers. I also come from a mixed engineering and design background and am probably from about the same area in Europe as you are and now live & work in California.

— You're young and it's hard for someone your age to master multiple disciplines. I'd focus on presenting one discipline. If I were you I'd sharpen and highlight your development skills. Maybe you can present yourself as a design-driven front-end developer?

— Recruiters often search by keywords. LinkedIn can help you experiment with what keywords get you the most attention. You could for example try learning React.js which is very popular right now, or further developing your iOS skills and change your LinkedIn title to React.js developer or Swift & iOS developer. Try different things and see what gets you more attention.

— Some recruiters like seeing big names on resumes. Have you considered applying to, for example, big international ad agencies that have Paris offices? Companies like Grey, Ogilvy, BBDO might have local offices that need design sensitive front-end developers. I have no opinion about any of these companies, I just know they're big agencies that have offices all over the world. You might be able to transfer or those names might open some doors for you in the US.

Again, please take this with a grain of salt. These are just some quick thoughts.

This number sounds about right.

Curious, do you have a solution to automating food intake logging?

Props for using Shopify!

First we're trying to master the food suggestion part of that equation. We want to encourage people to eat the healthiest thing they have available. This means our tool doesn't try and punish you if you aren't shopping perfectly. By using an "SOS" button, we are going to work with what our users have access to and make suggestions for certain plates at restaurants near the user.

There are some emerging IOT products (like smart cups) that we plan on interfacing with that may aid in this process.

In short my answer is not yet. But interfacing with IOT health tracking products is a huge part of our platform.

So something like a GitHub timeline for exercise and healthy eating?

I have that. It's called a FitBit.

The fact that you manually have to log your food intake seems like a hurdle though. It's an important part of the puzzle and it takes a lot of discipline to log every single thing you eat.

But automating food intake logging sounds difficult…

I've been doing the exact same in the last few weeks in the opposite order.

I remember reading these as a young teen and liking the stories, but thinking the concepts were so far from ever being possible.

This was the age where the brutality stories of my grandparents surviving WWII started sinking in.

I was convinced mankind would never ever allow anything to happen again that could lead to what happened in the late 30s.

Mankind has a historically short memory (unless stories are elevated to religious levels). Witness the recent Holocaust Remembrance statement from the White House.

I like the clean UI.

And then there's the Wu-Tang thing.

His whole story even made him a character Watch Dogs 2.

What's wrong with the code? It's just HTML. Do you expect some NodeJS responsive React Web 3.0 app for this? I think the format, layout and code for the website is entirely appropriate for this.

The site is exactly what it should be. Politics aside, both the code and content are just straight to the point which I find very refreshing in an age of all React everything where every step along the way needs approval from a bunch of different people before anything gets done.

He sat down and said what he needed to say. At least he's not afraid to speak his mind.

This is all just delightfully postmodern.

If your project is going to face the general public and needs the best chances of being indexed correctly by Google, you should start with some type of server side rendering.

Currently, I'd opt for using either an existing CMS like Wordpress or Shopify, depending on the needs, with a layer of React.js on top of it. Or a full stack React.js + Node.js custom build.

You'll find plenty of resources saying Google can index JS SPAs but regardless of what you think about that, the no JS user should not be left out in the cold.

If you're building an internal application where you can dictate the browser support I've actually found that I'm fastest completing projects building a JSON API with an Angular.js front end. React.js would work just as well of course, just depends on what you are more comfortable with.

Lastly, PageSpeed. Some clients don't care about this, but some do. If you're deciding on a stack, try running your build through Google PageSpeed Insight once in a while during the early stages to make sure you're not getting any road blocking red flags.

I personally don't care much for PageSpeed's reports, I have found them to be buggy or bizarre at times. But having your client rip your masterpiece apart just because they hired a marketer that's blaming all their shortcomings on a less than perfect PageSpeed score isn't fun.

I hope that helps! Let me know if you have any questions. I would be happy to clarify or elaborate.