c0mpute
Joined 14 years ago
Joined 14 years ago
Xcode is the most "diff" IDE from other IDEs. I like Swift but just dont like Objective-C. The build tools and ecosystem is too tightly tied (I like to switch between development machines without having to always be on a mac).
Java is definitely painful, but I suppose the bias I have here is that I have developed on it for several years.
The breath of fresh air so far has been React-native and i wish more things get ported over to JS (or like Expo kit).
Are you building a relationship with the hospitals and clinics so that we wont't have to talk to them, but just use your api to get and push our patient's data?
I am in early 30s, which means I am mostly interviewing for senior engineering position. I have been part of teams where we have made offers to several folks older than I am for similar or higher position. This is the only time when age does come up for discussion (is he really qualified to be a senior or not?)
However, some patterns I do notice from time to time are:
- Younger folks are more eager at times to do more.
- Their enthusiasm also comes with quality of work that needs some additional care. But, it is critical we mentor them during these times.
- Older folks are generally more clear on what they want to work and how they want to solve a problem. Experience most likely.
- The really bad situation to be in is when some of the older (senior) folks don't drive and take initiatives and just wade through. With someone senior you want them to be there to mentor, help, guide, keep an eye out on many things, but we have seen a few senior folks who don't make that effort - This is probably the #1 problem I have seen in teams. A sense of agility is almost vital.
- I have seen the same lack of "drive" amongst some younger devs as well.
- End of the day, its not age, its almost the subject scale of how passionate they are about their work that has worked for us. Old/young is really irrelevant.
Sure, its easier to apply it to the mathematics domain and harder to something that many of us might think in OO. I guess it comes with taking small steps (as someone already said in a comment). Also, making conscious effort to keep questioning how functional our code is helps.
I saw this talk on functionatalks.org by Paul Chiusano (author of Functional programming in Scala) http://functionaltalks.org/2013/06/20/paul-chiusano-how-to-w...
If you see he repeatedly asks how can we make it more functional. I think that is kind of thinking we need to practice. Its hard after too much of imperative thinking I guess. One more thing I have heard is read SICP and forget OO for a bit :).
His own example, forget the manager, the players themselves have to be on the same page in so many levels during practice. Don't you think Messi, Neymar, and Alexis (all 3 different countries playing for Barca) would have to practice and know precisely about their timing.
I think the key thing here is the who really needs whom. Most entrepreneurs need YC/VCs and so might have to suck up what they expect.
I see this happen all the time here at startups in Bangalore. Of course if the audience is YC and the investors, it goes without saying what the language requirement is.
Indira Nooyi (Pepsico, CEO and one amongst that cnn list) articulates it perfectly in this video:
http://money.cnn.com/gallery/leadership/2013/07/08/global-50...
Even empirically your dataset consists of startups that target USA markets mostly and hence this conclusion. I am guessing CEOs are good and can come from anywhere, its perhaps "sales" that really needs the idiomatic speak.
So over the years me (and my team) have built up a lot of experience dealing with these for sensitive industries like healthcare/insurace/lending etc.
We are bringing these ideas out as a router to other parsers, but with some key takes that allow you to manage failures. "Failure is inevitable so route for it."
It is called Openreading - https://openreading.ai/ and open core here: https://github.com/openreading-ai/openreading-core
It is still WIP and will be more polished in a month after some more rigorous testing and benchmarks.
If this is a problem you deal with, would love to chat.
Note: the intent is to launch a managed version that provides more durable compute/retries, parallel execution, intent understanding etc but this is for later.