This link will get you to the handbook content: https://github.com/FrontendMasters/front-end-handbook-2017/b...
Readit Newssjcrank commented on Front-End Developer Handbook 2017 gitbook.com/book/frontend... · Posted by u/blueatlas
sjcrank commented on Should a Programmer Learn to Design? medium.com/@ux_app/should... · Posted by u/ux-app
I believe the answer to this question is clearly a "yes", if you are building UIs (web or otherwise).
As a 10+ year UI developer I have found that my work is often judged by its design as much as the quality of the code, and that I will not be successful unless good design is a part of the work, and I cannot always depend on having a solid dedicated designer contributing to the project.
sjcrank commented on Ask HN: Hiring managers, what tech skills will you be hiring for in 2017? · Posted by u/changeseeker
When recruiting for web development (heavy JavaScript SPA work), I look for 3 technical skills:
1. Core JavaScript. You should be able to read modern idiomatic JS code pulled from an open source project and explain what it is doing and how you would modify it to add features.
2. Core CSS. You should be able to review Bootstrap source and explain how it works. You should be able to create static HTML/CSS to match UI mockups.
3. Higher level SPA library/framework (e.g. React, Angular, etc). You should be able to demonstrate an understanding of the core concepts of your chosen framework.
I find that these 3 skills are sufficient for productivity in SPA web development.
I like to have a clear title and opening purpose statement at the top, to set the direction for the rest of the resume.
In fact you already have something to work with in this quote: "I'm an all-round developer who cares about getting things done and uses whatever means are best for the job. I'm able to learn/understand tech quickly but this is just a means to an end. I like to focus on the team and there interaction / openness." (but fix the sp of "there interaction")
If the audience sees something like "Senior Software Engineer" followed by the above paragraph it helps them understand how you see yourself fitting into the organization.
Next I would follow with a simple tabular format of skills (languages/frameworks/platforms for example) that is quickly scannable and has been pruned to remove outdated or out of favor technologies.
sjcrank commented on Tech layoffs more than double in Bay Area mercurynews.com/business/... · Posted by u/akg_67
That layoffs have increased should not surprise anyone at this point. Unlike the dot com explosion it seems painfully difficult as a regular employee to have divested some of your equity gains mid-bubble. That makes it more painful.
However, every time there is a great deflating, it is because the market is tired and preparing to embrace something different. So far I've been through several of these, chips in the 80's dot coms in the late 90s, storage in the early 2000's, and now either web 2.0 or social (depending on how you score it). Three threads are competing for the next round, IoT, Machine Learning, and Bioinformatics. CRISPR derived technologies could be in there too but I see a lot of regulatory hurdles headed that way which will be hard to dodge.
The thing to keep in mind though if you are one of the folks getting laid off, it isn't you its them. Seriously. Layoffs happen when the world shifts and your company didn't shift with it. That said, it still sucks to suddenly be out of a job and the temptation will be to grab at the first thing that offers you something. My advice to you is to be thoughtful. Think through what you want to do, what the world is going through, and how you want to look back at your role on that. Then head for the area that best meets those needs.
"the temptation will be to grab at the first thing that offers you something" I actually think this is a good idea, since it will give you a chance to pay the bills while you take your time to find the best next step in your career. Also, like it or not, there is real bias against hiring the unemployed and you are in a better position to negotiate compensation when you are currently employed.
sjcrank commented on Unraveling of the tech hiring market blogs.janestreet.com/unra... · Posted by u/luu
This has always been a difficult challenge when job hunting for me, and I'd be curious to hear how others deal with this in their careers.
Nearly every job offer I've encountered expects a response within a few days. In practice, I'm usually interviewing at multiple places and at different stages of the interview process at each. The 'exploding offer' system makes applying to multiple companies near impossible for the job seeker.
Sure, I see how it creates leverages for the job offerers to get candidates to accept. However, the flip side is that turns the hiring process into a game of forced, snap decision making, which doesn't necessarily seem to be in everyone's interest, either.
If the offer is one you are seriously interested in it is best to not flat out refuse an exploding offer. An alternative I have found effective is to stall a few days through further negotiation of the offer, with steps such as:
- I have some more questions about the work environment, can we setup a phone call with one of the developers
- I would like to learn more about company benefits, can you send me the relevant information about healthcare options and prices for my review
- the salary offer is slightly below my target, but I am willing to consider it if we can improve the PTO offer: is this a possibility
sjcrank commented on React and the economics of dynamic web interfaces nczonline.net/blog/2016/0... · Posted by u/tbassetto
An honest question on this: how much are these touted benefits around ergonomics, code-reduction, and simplicity are relative only to Angular or vanilla JS?
Our shops avoided Angular altogether due to the complexity with larger apps, and used few other frameworks and libraries instead.
Trying various real world React examples frankly seems to involve more code, and the learning curve for React+Flux/redux/etc is really not trivial for a lot of people.
In my opinion, there's nothing wrong with using raw JS/jQuery for projects - with discipline you can keep the code performant and well-structured. On the other hand, I have found real benefits from React as the project grows in size (current SPA is 50k lines of code).
Overall, my recommendation is to use the simplest approach that works, and start adding libraries/frameworks only when they add clear value.
sjcrank commented on React and the economics of dynamic web interfaces nczonline.net/blog/2016/0... · Posted by u/tbassetto
Performance is often cited as the "big win" that React brings to web development; I really wish that wasn't the focus that (what seems like) most people take.
The DOM isn't (that) slow; it's all the crap we do to it that makes it slow.
React's strongest selling point is its ergonomics: It frees the developer from having to write huge swaths of code that they otherwise would be with most previous libraries/frameworks.
It achieves that with its immediate mode rendering: you no longer have to reason about how to transition the DOM from one state to another (in nearly all cases).
In my experience the performance benefits are when comparing React to other libraries/frameworks that also provide some level of developer ergonomics. In particular, during the early days of React, it provided great performance in contrast to AngularJS. Not so much when compared to well-written raw JS/jQuery.
Mist Systems, now part of Juniper Networks, is seeking a senior level front end developer to work with our team as we build out web applications for configuring and monitoring large scale wireless networks.
This is a great opportunity to work in a startup environment, using a modern technical stack (React/ES6), innovating at a rapid pace, while having the stability and access to resources afforded by a strong parent company, a leader in the networking industry.
Working at Mist you will be enabling WiFi access for people at schools, hospitals, warehouses, retail stores, and businesses, not delivering advertising, harvesting personal information, or building weapons.
To apply or learn more about the position contact me: scrank@juniper.net (I'm the hiring manager)