m12r

ParachuteHome | Venice, Los Angeles - ONSITE | Full Stack Engineer

Parachute is looking for a Sr Software Engineer to lead the development of the platform which powers the operation of the business. The engineer will be joining a small and growing digital team. This role will require general software development skills which will improve supply chain, commerce, and back-office functions.

The Sr Software Engineer will partner with Digital Product Management, Customer Experience, Supply Chain, Fulfillment, and Marketing team to build the foundation of Parachute's business. The Sr Software Engineer will be responsible for technical leadership of software platform, from gathering requirement, technical design, implementation, and maintenance with a strong emphasis on usability.

The Sr Software Engineer understands direct to consumer business and will turn complex requests into scalable software solutions. Sr Software Engineer needs to show initiative solving important business problems.

The stack needs to be build from the ground up, so this is the perfect opportunity to make big/important decisions on technology adoption at a startup.

Send a note to [email protected]

Can you?

Microsoft Antitrust nightmare that probably set them back 5 years. Google for invading our privacy, they are still fighting big important battles in Europe. Facebook for similar privacy invasion, the whole beacon debacle.

There are a lot of things that they probably did wrong, but not to the extend that the press is picturing it.

Agreed 100% w/ dvt.

Absolutely aggreed with this. We still have to pay a 5 to 10% task to get the conference call going.

Chime is the absolute good step in the right direction, however we will need need a layer on top to solve for all conference call systems.

There are three pieces that needs to be figured out to make this work well:

1. How do you deal with (non?) presence? Are you joining from the AV hardware? 2. How do you deal with PSTN? 3. How do you deal with other VoIP solutions out there.

I have a few ideas on this, especially on #2.

I assume this is going to be really diverse. depending on the business that you run. I'm more curious about the way this is delivered.

1/ Did you build your own?

2/ Do you a web version, that you check on your phone?

3/ Do you email yourself a summary?

4/ Do you just not check on your mobile phone and why?

Finishing things impossible. When do you know it's finished? When it's dead? It's not bad to start something and table it. The amount of time "that thing" comes back to you is probably the best filter for you get it moving. If it does not come back to you, it probably means it's not important to you, or not important to anyone else. Just use pattern recognition to spend the right amount of time on the right idea.

love the idea, but logins are not dead, you just piggy backed on device/passcode combination instead of email/password combination.

PS: I have always wondered why PINS from debit card are 4 digits, and some random consumer product will ask you for a crazy complex password with at least 8 characters.

why vim creep, it should be titled "ode to vim"