Well, he was pretty good, he let us take the decisions completely so we never paid anything for it other than in time. Moreover, we weren't flush with cash or anything so they wouldn't have made much anyway.
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).
:-) - Strangely, I am looking forward to this. I think it just comes down to the fact that I am very comfortable with JS and node ecosystem and prefer that over all other mobile platforms atm. I also think maintaining one (almost ~80%) codebase for both platforms is a significant advantage.
Xcode is best for things like managing certs, not actually working in. The intellij version is pretty good; it integrates well with the build system and debugger.
I find it curious you bring up Expo as i've found that is the most opaque and user unfriendly IDE i've used in some time; i don't get why they don't just leverage VSCode and quality tooling over Yet Another Goddamn IDE.
Curiously, I feel the opposite way–Xcode's support for managing certificates is pretty awful (it's gotten better recently, but it still occasionally gives cryptic errors for no discernible reason). For actual programming, though, it works pretty well as long as it doesn't crash.
To clarify - Expo as a framework, and not XDE. I think they have made Expo eject a bit cumbersome but works with some wrangling. I like the the Expokit framework in general but don't want to be tied to the Expo's release chain.
If you mean XDE, it's not meant to replace VSCode or Sublime or anything. XDE just gives you buttons for common actions that you would normally do via the CLI.
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?
We are building relationships with health systems across the country, but we can't remove the need for you to talk to them. What Akido does is make integration a non-issue - we turn integration into 'plug n play' from the developer's and hospital's perspective. What this means for you is that your sale to the hospital or clinic decision maker becomes far easier!
Please do note that the health system maintains all control over who has access to data -- this is VERY sensitive data, and it's extremely important that access is tightly controlled, logged, and auditable. (Akido handles all of that for the hospital)
Personally, my experience in the valley (being hired as well hiring people) has been not been guided by age. My experience has been with the startup since it was at 50 member to well over 100 now.
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.
As somebody who has written a lot of Java code before (read imperative) and now have had the opportunity to write more JS (which makes it a bit easier to write Functional) and also Scala, I think the process to "think" functionally takes time.
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.
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 :).
Communication is a primary requirement in a team sport and especially football.
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.
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.
That statistic is meaningless. As pg said explicitly, the problem is not being foreign. The problem is having an accent so thick no one understands you when you speak.
I don't think I disagree with what you have mentioned and pg has concluded. My point was, it is possible to find a dataset where the audience actually doesn't need to stop the speaker because they can tune in to the way english is spoken.
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:
it is possible to find a dataset where the audience actually doesn't need to stop the speaker because they can tune in to the way english is spoken.
Of course. But again, what does that really tell us? To be effective, you need to be able to communicate with a large variety of people, not just a carefully-chosen subset of people. As Indira acknowledges, it is your own responsibility to ensure this- not your listeners.
I've met people in America with accents almost this unintelligible: http://www.youtube.com/watch?v=I5XyecKONu8 (although typically their mother tongue was of Asian lineage so the sound was different)
