thomasloh

Sonder | Software Engineer | ONSITE (San Francisco, Montreal) | Full-Time | https://www.sonder.com

Sonder is re-inventing hospitality by building tech that powers seamless experience for our guests, from booking to check-in and check-out. We own the process end-to-end. Having recently raised $225m and hitting 1B+ valuation, we are hiring engineers across all functions. Some of the projects we have:

- Direct booking (sonder.com)

- Pricing engine

- Connected/Smart Home System

- Logistics/Supply Chain/Inventory Management

- Unit Onboarding

Email [email protected] for more information.

like a TurboTax for all immigration forms?

We're developing out Android app in Kotlin! It is a very promising language and as others have mentioned, the IDE support is superb, first class. Easy learning curve if you already know another language.

And since Kotlin also compiles to JS, we're writing our REST api client in it so that our Android app and web product can somewhat share the same codebase.

I think Kotlin can potentially go mainstream

Isn't it just a prettier RSS reader? basically Flipboard? Also, I'm skeptical of the concept of "bynd-zero" because it is impossible. In fact it'll be even more stressful because the stream of contents is endless and the only way around it is to shut off this feed addiction.

Doing OOP in languages like Java and Ruby tend to involve classes, objects, encapsulation and state coordinating. Now, the truth is, state is really hard to maintain. You have this piece of information where everyone is trying to change or grab at, it's gonna end up leading to race conditions and locking. It may work for a small app, but as your application scale up, it's a maintainability disaster. So you said OOP done right helps. But, OOP was the wrong paradigm to begin with, it's like saying "Horse-riding done right gets you anywhere faster". I'm not saying everyone who has been programming in OOP is wrong, it totally makes sense to use OOP because it's easier to model real world things with. But no one has ever question, "This paradigm may be facilitating my understanding of the problem, BUT is it the right paradigm?"

As Dijkstra said,

"Dont't trade simplicity for familiarity."

what's the difference between boot and leiningen?

if you seriously want to understand it :)

yet another React + Flux "framework". The truth is, a lot of companies who are using React and Flux already have a framework in place, they just didn't polish it to put it out there. Nothing ground-breaking here, certainly nothing revolutionary.

The idea behind OOP makes sense. But the carry-out of OOP in pragmatic programming languages is the problem.

http://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hic...

> but your OOP needs to be on point if you hope to build something maintainable for the web.

OOP != maintainable codebase

Strip away all the fancy, it's just a list. I don't buy it

By the end of day, it's all about delivering substance, not style.

React much?

My point is: It'll be hard for your blogging platform to stand out if it's garnering first impressions that it's a "Medium knock off". I do agree with the idea of constraints and boundaries in shaping a product. Unfortunately, humans are cruel visual creatures

If it's supposed to be different from Medium, why does it imitate the look and feel of Medium?

thanks. by the end of the day, it's all about getting the job done == Ease of entry