cjcenizal

Great post! I totally agree that quality of tests is more important than code coverage, but the author does a great job of really explaining what that means, why it's important, and shares some great practical examples.

I'm a developer with a background in design. In my career I've built and maintained UI component frameworks in SCSS and React, built web apps, and collaborated with designers and product owners to improve the app's UI and UX. As the builder of these products, I'm usually the first one to actually experience the them, so I'm in the strongest position to notice problems and suggest improvements.

So, yes, there is such a thing as a UX/UI developer/engineer.

This is a good point, but to be fair you need to learn and implement similar solutions in an Angular-based project. You still need to implement a layering architecture that separates application/model state from view state (e.g. Flux/Redux), a module system (e.g. Webpack, Browserify), and a router (e.g. ui-router, react-router).

Ask the employer what the salary range is for the position (they should already have a number budgeted). Add $10-$15K to the higher number in the range they give you to get an idea of what you can push for if you are able to convince them that you will be a really remarkable hire. If you have a hard time figuring out how to do that, then you are probably not at that point in your career yet (which you shouldn't feel bad about if you're just starting out).

It's funny how even a professional as experienced as Martin can be so terrible at estimating! I don't think it reflects poorly on him. I just think it supports the idea that estimates are really, really, really hard to get right.

"Learning CSS" is a pretty broad topic. Have you checked out http://cssguidelin.es? It's pretty high level. For some fun stuff you could also check out flexboxpatterns.com (I'm the author).

I think I understand what you're saying, but I think you're drawing the wrong conclusion here. You just stated that services break by default. I think that's what the author is stating, too. Services break. People make mistakes. Failures happen. By accepting screw-ups we arm ourselves with a mindset that's focused on moving forward, instead of beating ourselves up over what's already occurred.

Success can have a strange effect. It raises the bar for you. The merit of your accomplishments become relative to what you did yesterday. If you don't out-perform past results, you're failing. And if you're failing... then aren't you a failure?

I think we forget that failure is the default state. Which redefines success to be making any attempt at all. Like Edison said: "I have not failed. I've just found 10,000 ways that won't work."

From the context, I think the author was probably referring to office politics, not corrupt politicians.

I currently have the role of the lead reviewer you describe and I often worry I'm focusing too much on minor details. Fortunately my coworkers are comfortable pushing back. I think if you're able to have an objective discussion and agree on your goals, and whether a suggested change meets them better than the existing code, you'll be able to get work done together without one of you feeling like you're being a problem. The reviewer also has to be prepared to let go of a suggestion if the change won't have an actual impact.

Do you really think his arguments were reasonable? Why did they fail to persuade you?

This is honest, clear, and on the mark. Disregarding people's feelings isn't cool. Being an asshole isn't cool. I think those traits are orthogonal to skill, and only imply immaturity.

Awesome! Creative coding is how I got into programming, too (http://cenizal.com/projects/vfx_portfolio/)

You'll be paying for your own utility costs (power and water), so your utility bill will probably double. Make sure your salary is high enough to cover those extra costs.

Does the company already have a good system in place for remote collaboration, e.g. Slack channels for asynchronous standups, shared calendars, Confluence documentation, screen sharing tools for pairing, Google Hangouts, a healthy PR and code review process? Those tools and processes will need to be habitual for you to be a productive member of the team.

You're absolutely wrong. Here are two examples of human activity having global, negative effects:

1. Our use of CFCs caused global ozone depletion: https://en.wikipedia.org/wiki/Ozone_depletion#Antarctic_ozon...

2. Our use of leaded gas caused global lead poisoning: https://en.wikipedia.org/wiki/Tetraethyllead#History_of_cont...

I can appreciate the need for gut checks, and have asked people for feedback so I can get a better idea of how I'm being perceived. But the burden of knowing when you're full of shit should really fall on the individual. So to that end I think we should all strive to be conscious of how our words and actions affect those around us and the task at hand, instead of relying on someone else to rein us in.

Ironically, this blog post doesn't contain an actual link to Google+.

Seems like it was, not sure why though.

Hey, I'm one of the guys working on this project. You're right, we're not sure how to make sure the winner splits the money with everybody, but given how unlikely it is that anyone wins at all, we're just focusing on executing the bracket distribution for now. If someone actually wins, figuring out how to get that person to split up the money is kind of a nice problem to have! Just think of the drama...!

Somewhat ambiguous domain name!

Why not? It is a good solution for lacking good library documentation.

I really enjoyed your post. I agree that it's a good "directive smell" if your directive is reusable and application-agnostic.

In that vein, I think you're right that an isolate scope is generally a better default because it makes it clear that the directive expects no dependencies on the inherited scope, and it prevents the directive from overwriting any scope properties set by an ancestor.

I think using an inherited scope makes sense if you're building very app-specific directives that are tightly-coupled to their ancestor.

Imagine capturing footage on your phone/Glass and reviewing it on a large display that tracks your head movements and adjusts the camera accordingly.

Think of the Minority Report scene when Cruise is watching pseudo-3D footage of his family.

The history of media shows a trend towards 100% faithfully recreated experiences. Photos > Film > Video w/ audio > 3D. This gets us one step closer.

TamDenholm's comment is absolutely correct. At your stage, the easiest way to get revenue is to learn how to sell something, e.g. present your services in a way that demonstrates value to your customer.

You should read "Breaking the time barrier"[1]. It's a quick read, but it presents some key guidelines on how to accomplish this, and will be invaluable training when you're talking with a potential customer and trying to figure out the best deal for you both.

[1] http://www.freshbooks.com/blog/tag/breaking-the-time-barrier...