jaspal747

We will surely take that into account and carve it as an add-on. (Postmark did the same recently with their retention-add-on) We are early in the product phase so feedback like yours is very valuable! Thanks again

Thanks for your feedback! The main reason for pricing is storing all the past emails and the architecture to store and process future emails. If you compare the pricing, the overall costs with SES + Pendable should still be far lower than other platforms for comparable sending limits.

excuse my naivete, but do black holes help reduce entropy by capturing/engulfing things around them? Is that the cycle how universe keeps creating and recreating itself?

- Show respect for the reader's time. Sometimes we scan 10-15 resumes a day and can see clear patterns, repetitive marketing pitch, lofty unsubstantiated claims. Unserstand that others applying for the job have very similar resumes and you need to be more direct and stand out from the pack. The job poster's BS detector is fairly finetuned and can quicky pick out BS from true merit.

- What draws my attention is humility and the resumes that speak directly to me. Like a resume narrating a coherent career story.

- Show some solid experience in the core technologies requested in the job posting.

This much is usually enough to prompt me to give someone a call and then know their story and cross reference it with what the resume said and also know more about them.

Put yourself in the CEO's shoes and see the entire company end to end. Then see how your team is contributing to the bigger story. Work on bringing business context to tasks. Help your team members see the business/strategy line of thought behind decisions. Once team members have context to the work they do, they are better motivated and bring in valuable insights. Always appreciate and bring spotlight on them for successes. Always take on the blame and never forward criticism directly to your team members. You are the buffer. Read books on strategy/business to gain greater perspective. Train yourself and your team in second and third order thinking. Helping them come up with all kinds of scenarios around their tasks. Finally, be humble, caring, and be nice to everyone. Cheers!

As a tech lead, you bother about building the features that the business has identified - and building it in the best way possible, thinking long term about the product. While as a business decision maker, you focus on what your users want - else you will be out of business fairly quickly.

Srry about that. Just updated it to regular text.

Few things I would like to say:

It will no longer be about you. It will all be about your team. Make sure you create a great team, nurture them, train them, teach them how to think critically (in doing so yourself).

Ask your team to write out everything they plan to do before they actually do it. Reason with them on what they wrote and what approach decisions they plan to take. Teach them to think long term. Writing before actually doing the task helps get a lot of clarity to them and also helps you in assessing what they were planning to build. (It also makes for a great log of what we did and why we did it. This will be the product documentation for your entire product tomorrow.)

Treat your team like your family. Do not stress them out with too much work. Be respectful of their time and effort. Give them breaks post completion of major tasks. Every second that you let them rest and breathe is a second you have invested in the future. They will recharge and put their best in the next task.

You have a tough job of standing up for the right long-term tech decisions. Stay loyal to your product. Work for your product - not your company. Take tough tech decisions that will stand for the long term stability and robustness of your product. But occasionally make allowance for your business team too.

Sometimes your teammates might shy away from a big daunting challenge - step in and work side by side with them to tackle it. But do this infrequently.

There is a lot to add to the above list but in general the idea is to help your teammates grow, help them think critically, stand for your product - make the tough calls.

All the best!

Can we send two parallel streams of video and audio and then at the receiver, pick each packet selectively? If a new packet arrives in either of the streams, pick it if it is the latest, and discard it if we already got one with the same id..Something one the lines of adding redundancy to compensate for the poor connection?

- Split up the task you have in mind into smaller tasks and assign each dev to them

- Make each of them watch online videos and do independent research and learn as much as they can in 1-2 weeks. Measure them every two days.

- Post two weeks ask them to build a small application in the third week. eg:login functionality with password reset and captcha.

- In the fourth week, ask them to build the entire chunk of work you cut out for them. Push them a little to achieve it. (They might need 2-3 weeks to get it done though)

- Keep adding new tasks and assign new learnings.