48 karma · joined April 23, 2013
>It was fun, it was challenging, it was rewarding, it was amazing.
This cannot be overstated
Especially valuable piece of advice is to find 25-30 minutes of uninterrupted time and aim to knock out one small task. Even if you didn't finish it, note down progress and next steps. Go at it again in the next slot.
Taking notes will both help you track progress and give you a sense of movement. It will also make sure that you can easily regain context in the next attempt.
Apart from helping with faster memorisation, I have noticed that writing a problem down / solving on paper improves problem solving significantly. I always diagram out the problem & solution on paper whenever i get stuck.
True true true. Especially if people are building quirky cool stuff in smaller orgs, its simultaneously a great place to work and has a higher extinction probability.
thankfully production is unaffected.
Bodies that are in stable orbit can have only a specific velocity which is a function of its distance from & mass of whatever it is orbiting. So orbiting satellite's speed can be inferred from its orbital height.
There are ground based tracking stations that can technically measure the speed of any orbiting body.
Also read somewhere that LEO satellites could use GPS receivers to get a fix on their position. measuring change in this position also gives velocity. There a bunch of limiting conditions around max-height and velocity for this to work though.
What the article talks about is 2-phase cargoes, cargoes which are expected to behave as solids but could turn to liquid under certain unpredictable conditions.
Accounting for these scenarios might involve upsetting the economics of said cargo.
Edge cases basically :D
> as long as the route the call takes is via a licensed operator. This is Twilio's problem, not yours.
I surmised as much. Have not been able to speak to Twilio. But Plivo's reps assure me that compliance is not an issue. But we want to be doubly sure. Do not want to be railroaded by legality somewhere down the line
Then, the key thing to focus on would be to get work done:
1. Begin your day by making a long-list
2. Prioritise - 1 do-or-die task, 3 must do, rest are good-to-have. It is important to prioritise, else nothing gets done. Better to accomplish 1 thing every day than attempting 10
3. Once prioritised. lock down. Break down into tasks that take less than 30 minutes. And spend time on a task 15-30 minutes until it is done. Everything else can wait
4. Rinse and repeat
I have suffered this same problem before. Allocating too much time for tasks - getting nothing done. Key is to focus on doing things rather than allocating time. Hope this helps
Most of our experience is controlled by an all-knowing black-box algorithms. The game is to converge all experience into a small set of patterns
An Example - youtube Earlier I could spend hours on youtube and discover everything from new music to weird funny videos. Today you literally get boxed into a list comprising of your history and recommendations that have hardly 1 degree of separation from your history
this. interfaces are not the most important thing in a software but definitely one of the most. you can live with a crappy implementation but your interfaces must cater to the usecase and should only hcange when core premises change.
Everything you read is tracked as read/clicked so that you can search using those filters. Also tagging and creation of own channel(invite only) is allowed.
Examples:
http://filr.io/channel/hackernews
queryparams: pageSize (no of items to return in one go) before (takes an epoch timestamp and returns results before that timestamp)
this is a stream of HN stories that have made it to the front page, in order of the time that they made it to the frontapge.
http://www.ibtimes.co.uk/goldman-sachs-pay-bonuses-hit-12-61...