kaishin

Kaching AB | Stockholm, Sweden | 3 Roles | Full-time, Onsite preferably

We are Stockholm-based startup founded in 2016 and we're building cloud infrastructure and mobile apps to support the next wave of brick-and-mortar and online retail innovations (self-checkout, mobile POS, RFID applications, machine learning, etc). We're looking for cloud engineers, backend, and Web developers.

Career Page: https://www.indeedjobs.com/kaching-ab/

* Cloud Engineer: Experienced cloud engineer with razor sharp knowledge about cloud architecture.

Keywords: AWS, Cloud Formation, Cloud Front, Cloud Watch, Elastic Compute Cloud, Lambda, Route 53, API gateway, pm2, Apache Kafka, Networking, Security, GDPR Link: https://www.indeedjobs.com/kaching-ab/jobs/3db2068f08a445282...

* Backend Developer: Experienced backend developer with strong interest in system design.

Keywords: NodeJS, TypeScript, pm2, CQRS, Kafka, Event Sourcing, Micro Services Link: https://www.indeedjobs.com/kaching-ab/jobs/7828451b61553d4e1...

* Lead Web Developer: Experienced Web developer to take ownership and bring our web platform to the next level.

Keywords: JavaScript, client-side frameworks such as VueJs, ReactJS, webpack, CSS, npm, TypeScript Link: https://www.indeedjobs.com/kaching-ab/jobs/3867a157e5249d648...

JavaScript + Webkit.framework = Leaks.

It's not just about typing less, it's a whole UNIX philosophy of having dedicated shells for programs that are complex enough for subcommands.

Here: https://github.com/thoughtbot/neat#browser-support

Please take some time to read the documentation and see the examples. The omega() (there is no alpha() mixin btw) mixin doesn’t compile to CSS, so debating whether it's semantic or not is beside the point. If, after having a closer look, still think that Neat would not be solving any of your current problems, then you are more than welcome to stick to your guns. No tool is perfect for everyone.

Thanks for pointing that out betageek. That's certainly an oversight. We will be working on more IE compatibility and a better documentation.

Agreed. Here is something better http://robots.thoughtbot.com/post/30928446434/introducing-bo...

Fair enough. Until we come up with a better way to detect nested columns, I don't think explicit nested rows is the route we want to take. Our primary goal is to use as few mixins as possible to achieve proper nesting.

As one of the designers behind Neat, I like what Zurb have been doing with Foundation, but I'm not entirely fond of their semantic grid framework. Many decisions have left me scratching my head and wondering if there wasn't a better way to do things (innerRow() and mobile[...]() mixins are some of these).

Hi, I'm one of the thoughtbot designers behind Neat. I have been using Semantic.gs for a while and it is one of my favorite grid frameworks out there. My gripe with Semantic.gs is that it is not responsive, i.e. it doesn't come with a straightforward way to change the grid for specific breakpoints.

I also don't see how span-columns() is any less semantic than .column().

No, they are not. At least not yet ➜ http://drp.so/058604 (16px).

That growth is exactly the worrying part of this pattern. It can get unwieldy real quick.

I really think that the vertical navigation menu is inappropriate for mobile apps. It makes the user flow feel more clunky and encourages section overload. It is also a sign that there hasn't been enough effort put into information architecture.

I expect nothing less from a programmer. But then programmers (as customers) are not the ones making Apple the most valuable company in the world. Comparing something made by programmers for programmers to something made by a consumer product company for consumers is pure nonsense.

I wouldn't expect anything less from a programmer. But then programmers (as customers) are not the ones making Apple the most valuable company in the world. Comparing something made by programmers for programmers to something made by a consumer product company for consumers is pure nonsense.

The look of the cheat sheet lives up to the 'for Programmers by programmers' part...

A dozen operations may be more than enough for 80% of users. Designing for the remaining 20% is a common UI design mistake.

What's your logic behind this number? Do you think Microsoft made all those billions selling crappy software to geeks like us?

The problem has more to do with the excessive number of available commands. My suggestion is to cut the clutter and avoid hierarchical UI elements altogether, regardless of their nature.

This http://kaishinlab.com/2011/05/pitfall-of-customizability/

My parents definitely won't.

I think the ribbon concept is inherently flawed because no human brain can remember such an overwhelming amount of information (what command in which function group in which tab).

Github makes it easier to track projects without having to download 3kb files only to forget about them several days later... And of course, there is the Git part.

Hi all, I am interested to know if any of you have used Tweetbot for iPhone and would like to hear your feedback to wrap up my piece!

My message is clear. You are free to disagree, just don't feel the need to bring down my piece sentence by sentence...

Sure, I might have gone overboard, but the basic idea is still the same: That thing needs serious design thinking, not patchwork.

I consider it unethical for a company to throw a smokescreen instead of solving the real problem. And my piece was all about shedding some light on this.

What I said reflects solely my opinion on the people who enter the contest. As far as I am concerned, anyone who takes UI design seriously wouldn't bother doing so... Again, I am not expecting you to agree.

If you, as a designer, truly feel the work you are doing is better than a design competition, then don't submit your work to a design competition. If you're really that good, freelancers offering services for cheap, near-free, or even free shouldn't bother you at all << This is exactly why I wrote the article. You guys are talking money, I am talking ethics.

Hi all,

I have spent almost one hour reading all of your comments and replied to as many as I can. Needless to say, I don't expect everyone to agree with me. Actually, I was expecting quite the opposite, if the strong tone of the article is anything to go by.

Again, let me reiterate that I am NOT against design contests per se. I am against companies who take design lightly and try to patch stuff when things go astray. Do any of you think that changing the visual style of the chat pane will solve the several issues of the new UI?

Folks, this is a program used by millions of people, including computer un-savvy people who are having serious problems with the new UI. Forget logos, the problems here are functional first and foremost, and it is not a design contest that will solve them.

For those of you saying that this is a chance for young designers to get their name out in the world, allow me to tell you that there are hundreds of other ways to do that. Free or open source projects that need UI designers are not hard to come by.

Also, I am under 25, and by no means an old timer who is trying to spoil the party.

Cheers,

I do not run a design firm. I am just a no-name freelance designer who loves his job. If you think that I wrote the article because I am concerned about paying my bills, then you completely missed the point.

It's sad to live in an era where someone who loves what he is doing for a living is called a "smug ass with an unwarranted sense of importance" ...