rvdm
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.
Props for using Shopify!
But automating food intake logging sounds difficult…
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.
He sat down and said what he needed to say. At least he's not afraid to speak his mind.
His whole story even made him a character Watch Dogs 2.
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.
I like that Shopify isn't your typical Silicon Valley tech company. But coming from a background as a tech and security consultant for Fortune 500 companies, Shopify does feel like I'm back in the tech little leagues sometimes.
And this is an unfair image association problem Shopify has. Their tech is quite amazing and a lot of very brilliant people work there.
It’s great to see Xal, the CEO of a publicly traded company with a close to $4bn market cap, this active on HN. I’ve always considered him one of the most brilliant engineers of our generation ever since the Active Merchant days. To me these programs and the way they are being shared on HN really help bringing his company the credit it deserves.
I'd be curious to find out if the success FB has had with Haskell for spam filtering means they might consider Haskell for different parts of their stack too? Does anyone have any insight on this?
I'd love to know what the Swiss themselves think about this system.
To any Swiss people on HN :
— Do you feel this had a positive impact on society?
— Maybe more important, would you recommend this to other governments?
Their RoR stack might have gone out of fashion but it seems like they consistently made the right decisions considering a lot of their customers rely on the Shopify platform for their livelihoods and not just to express their opinions in 140 characters.
Looks like we placed our bet on the right horse.
imho xal / Tobi should get far more recognition for what he built. Shopify is really quite remarkable and in a league of its own.
Curious if they'll ever beat Amazon / Alibaba volume.
Regarding Javascript fatigue, I want to share something that greatly helped me.
I have written enterprise applications for Fortune 500s using PHP, Rails, Backbone, Angular, React, Node, Express, Grunt, Gulp, Webpack, Yeoman, Bower, Redux, jQuery, Coffescript, Prototype.js ( remember them!? ), LESS, SASS... Basically whatever was hot at the moment.
Long I've enjoyed learning new things, but after having made a solid investment in Angular only to find out none of it's SEO solutions were really commercially viable the fatigue hit me hard and I gave up on trying to learn new things for a while. I simply stopped caring.
Then I got approached by SpaceX for a JS full stack position. All they told me about the interview beforehand was that it would be very JS heavy, yet no details on what stack or framework they were working with.
To prep I brushed up hard on my basic JS skills. Codeschool.com their JS road trip was very useful. So were "Eloquent JavaScript" and "JavaScript: The Good Parts".
After making that tough but very rewarding investment, learning React, Flux, Redux, Elm etc. all became a breeze. I no longer have any attachment to any framework. They're all just different ways of using JS to me. And no matter what the future brings, no matter how many frameworks and build tools get thrown our way, I don't think ( hope? ) my heavy investment in Javascript will soon disappoint.
So for those of you out there trying to figure out what to invest in next, React, Elm, RxJS.. My advice would be to get a deep understating of pure Javascript first. Ideally, try to build your very own framework using vanilla JS. Once you do that you'll find each new framework is just a different opinion on how JS should be used.
Many frameworks have come and gone. But after more than a decade of investing in the Javascript language, it keeps rewarding.
This, as a potential Watson customer, would give me a much better idea of Watson's potential and real world results. Plus it would establishes more confidence in IBM.
A lesson from my high school economics teacher that has always stuck with me is that you have to be your own product's biggest believer.
Amazing work Horizon team!
I have been working on a descent sized React.js commerce platform. While I was able to get past writing HTML tags that should be as simple as
<div>Product</div>
using this instead
React.createElement(
'div'
{},
'Product'
);I could justify this overhead in development time and effort because of React's obvious advantages ( Universal rendering!! ).
However when I started adding in styles using Radium I found myself more frustrated than delighted. There are a lot of situations where writing styles in javascript becomes very inelegant very quickly. While basic CSS is far from perfect, I genuinely felt like I took a step back with Radium and reverted back to the legacy CSS stylesheets I had from our previous iteration.
I do have to note the version of Radium I was using inlined all the styles, I do like the new approach Radium is using a lot better, however I'll likely end up converting my legacy CSS to CSS modules, which has my winning vote for the moment as well.
Thank you for opening up the conversation here. All things considered I'm still not sure if CSS modules are really the holy grail. Curious to see what the future will bring for CSS + JS.
I'm currently working on a simple React.js commerce platform and even in it's early stages I'm already wrangling tens of thousands of lines of UI code. Anything to make React development easier is welcome.
Also, thank you for bringing awareness to how hard building a proper UI is in your Medium post.
I'll try to give you some more thorough feedback on github.
I am curious to find out if you have any plans for future features or where you see this project going from here?
For example, ip address + timestamp + even a rough geo ip location could reveal travel patterns of users simply visiting your site.
Let's say those travel patterns include visits to nations less friendly to the US and you just might find out some details about someone ( or at least a certain IP ) they really wouldn't want you to know.
All you need is a web server and a little bit of javascript.
Just my 2 cents, but I feel like there might be some commercial demand for something like this if you'd ever consider packaging it.
In the last few years plenty of fantastic, user-friendly online learning resources have popped up teaching all the cool things you can do with code but very few of them ever mention security. And all too rarely do github repos mention 'Watch out! This could be dangerous!'.
Teaching security always feels like someone else problem. I'm all for many more articles like this one!
enter office politics