Playlist Music | iOS or Android Engineer| http://playlist.com | Palo Alto, CA | FTE or Contract
Looking for iOS or Android Engineers to work on our Live Group Listening app: Jam Music. The app allows people to listen to music together (even if they're not in the same location) and interact throughout. The iOS app (written primarily in Swift) is publicly available and has increasingly good traction. We're working hard evolving the app with many new features. We are also just starting up development of Android (primarily in Kotlin), so that's basically a ground up project.
This is a small team doing big things! Official hiring email is [email protected], but better yet, email me directly at tango at playlist.com if you want to chat informally about what we're doing and why you'd want to work with us first (I'm the hiring person and currently lead iOS eng).
I could read this one of two ways: "a company must have been continuously filing for a minimum of 2 years", or "a company must have filed at least once within the last two years". I have no idea which is right (or if i'm completely wrong on both accounts) :-S
We had an app early in dev, and decided to make the leap from ObjC to Swift. Swift is here to stay, and as with most things the longer you put it off, the harder it'll be later. The integration between Swift & ObjC is good, so existing projects can be converted slowly.
Avoiding the conversion because Swift "isn't ready for primetime" or "the debugger is buggy" seem like excuses people make for "I don't want to expend the effort to change".
This is somewhat true. However, any developer who's got even the smallest amount of development skills will be able to make the leap from Obj-c to Swift with relative ease. Most of what people end up learning when doing iOS/Mac code are the frameworks, and they're functionally identical (except for syntactic difference of course).
On that second point...if the recruiter or hiring manager balks at the request to position yourself to be a manager or lead in the future, pack your bags and keep on looking.
My two suggestions are: learn everything you can about being a good manager and leader where you are now. Use the time you have as a "new (manager|lead)" in a company that knows you're a "new (manager|lead)" to be the eager newbie (just like you probably did when you were a newbie dev). Find the managers and leaders who you think are good and who have traits that you aspire to have and learn them while you can. Being a good technical manager and leader takes some of the skills of being a good dev, but a whole other set of skills that you generally don't need when being a dev. Finding a good mentor (even if they don't know they're mentoring you) is something you can more easily do at your current company.
When you do look for another job, be up front with the company you're talking to. You may want to interview for a Senior dev position, but tell the recruiter that you want to parlay your experience into being a manager or lead. At my last company, we hired a couple of folks like this, and they almost all turned out to be good managers and leaders.
Currently, the energy density of NiMH batteries is anywhere from 1/2-3/4 of LiIon batteries, so I wouldn't bet on them being used as traction packs for EVs anymore. It'll be interesting to see if more research is done on NiMH after the patents expire though.
Consider how this would have played out if they didn't shut down the links and then someone hacked an "important" document? It would have been way worse overall.
Not notifying the customers was not a good move however.
I've been talking to friends, and one friend who had a startup said they went for the big guns (Wilson Sonsini, Orrick, Fenwick & West, etc) since they thought it would look better to VCs when they went to get their Series A. That's a criteria I hadn't thought of. What do you think of it?
I think jaegerpicker hits it on the head. If the organization is a good one, with a good culture, kids vs. no-kids won't be a problem. The dichotomy between the two can definitely shine a light on deficiencies in the culture and/or management.
Looking for iOS or Android Engineers to work on our Live Group Listening app: Jam Music. The app allows people to listen to music together (even if they're not in the same location) and interact throughout. The iOS app (written primarily in Swift) is publicly available and has increasingly good traction. We're working hard evolving the app with many new features. We are also just starting up development of Android (primarily in Kotlin), so that's basically a ground up project.
This is a small team doing big things! Official hiring email is [email protected], but better yet, email me directly at tango at playlist.com if you want to chat informally about what we're doing and why you'd want to work with us first (I'm the hiring person and currently lead iOS eng).
Thanks!