klaaspieter

Sketch | Senior Go Backend Developer | Remote | Fulltime

Sketch is a design platform with an award-winning native Mac app and browser-based collaboration tools. Over a million people use our product to create their best work. And right now, we’re looking for a Backend Developer to join us.

Apply here: https://www.sketch.com/careers/go-backend-developer-onboardi...

When I said framework I meant standard library. The most important thing to learn is not the syntax of the language but the standard library. They know everything the language can do and will most likely use all of it's features somewhere.

Thanks for clearing it up, I think standard library is a better term :)

Thank you. My blog is rather old and still runs on app engine. First time I ever hit the free quota.

Should be up again.

Yes. I believe such a book exists (or should at least) for every language as well.

Effective Java — http://www.amazon.com/Effective-Java-Edition-Joshua-Bloch/dp...

POODR (Ruby) — http://www.poodr.com/

Javascript the good parts — http://www.amazon.com/JavaScript-Good-Parts-Douglas-Crockfor...

There is of course also the gang of 4 language agnostic classic on design patterns http://www.amazon.com/Design-Patterns-Elements-Reusable-Obje...

It's definitely a good way to get started with learning, but you have to be even more careful that you're not just copying patterns from one app to another.

I had this experience when I started working on Karma's Android app. I basically started out by copying the entire iOS architecture to Java. It helped me get started quickly without having to make too many hard decisions early on, but I did have to rewrite some things after I became more experienced and learned there was a better, more Android idiomatic, way of doing it.

The thing that helped me the most is that I became part of the community. Some of them explained to me why I was wrong and then taught me a better approach.

Acclivity NYC ([email protected])

PYTHON BACK-END DEVELOPER (Full-time - New York, NY)

We’re looking for an experienced Python back-end developer. You’ll be responsible for maintaining and extending Enstore’s existing REST API and Django Stores back-end hosted on AppEngine.

Requirements: Bachelor's degree in computer science or a related field

Expert in Python

Very good understanding of REST and HTTP

Basic knowledge of HTML, CSS & Javascript

Work well in a small team with the ability to work independently on significant pieces of functionality

Excellent written and verbal communication skills

Experience in testing and deploying web services (remote debugging, profiling, load testing, scalable, security)

Ability to work on-location in Manhattan

Experience with Google AppEngine and Django is a plus

UI / UX DESIGNER (Full-time, New York, NY)

We’re looking for an experienced user experience and user interface designer. You’ll be at the forefront of our design team responsible for every pixel we put out there. You’ll be working with a talented team of developers that care about design. You will be working on all of our core products.

Requirements: Experience designing beautiful and easy to use product

Work with developers to optimize user interfaces and improve user experience

Able to create low-to-medium mockups of desktop, web and mobile interfaces

Ability to work on-location in Manhattan

You have a strong pixel-level attention to detail

Knowledge of HTML, CSS & Javascript is a pre

I've seen the math behind it and you are definitely correct.

Cibs are indeed web optimized format. Thanks for the explanation.

Didn't know about this. I have thought about extending my example to run user defined commands on user defined files. Obviously someone beat me to it.

Thanks for the link.

Clarification: Not enstore.com itself, but the admin utility used to manage your store is built with Cappuccino.

Yeah I'm really curious about the story behind the <marquee> tag now.

I've been using `git difftool` and `ksdiff` for more than half a year now and it works perfectly.

We made it that subtle intentionally. It was supposed to be an addition that doesn't take your focus away from the actual website.

So in a way, it's there to not be seen.

Thanks, we are aware of that bug, just haven't got around to fixing it.

Building that Cappuccino/Atlas frontend