palakchokshi

That's a marketing headline. A little clickbait-y. That's fine you're a marketing hustler after all. Let's break down your numbers:

$99.75 in expenses (not counting time spent getting sales or building website)

5 total sales resulting in $450 of sales

108 hours of work done by you. We don't know how much time it took your brother to create the podcasts. Let's assume he didn't do the 6 podcasts perfectly in the first go.

30 days of total case study.

$350 in "profit"

Divide your profit by the hours you worked on it. $350/108 = $3.24 per hour.

Now let's consider setting up the website was a one time cost so moving forward your operating expense is $30/month to host the website and the podcasts[edit]

Let's take the hours your took to get the sales and divide those by the number of sales you got. 90/5 that comes to 18 hours per sale. Your average sale value was $450/5 = $90. Let's say your put a bare minimum hourly rate for your time of $10/hour that's $180 spent getting a $90 sale.

Now unless you get more visibility and are super savvy in promoting your podcast your ROI just doesn't pan out.

Let's see what your $1000 budget gets you in 3 months. Might be a good post to regenerate interest in your podcast. :)

That's a bit snarky no? considering you don't put in labor costs and time costs it's a bit ingenuous to say you built a profitable business. At a "profit" of $22 a day you could not pay your rent and food. Your customer acquisition cost at this stage is much higher than what the customer pays you.

This is anecdotal but in my experience a better signal is whether the candidate codes with best practices in mind. Give a moderate complexity design problem and watch for use of best practices/design patterns (good commenting, SRP, DRY, DI, IOC, etc). That tells me the code that person will write can be understood and maintained by someone else. After all the person who wrote the code is not necessarily the person who's going to maintain and enhance it for the lifetime of the application.

The one I love is when they ask questions that are completely unrelated to what the position is for. e.g. I applied to a startup company that sold used cars online for a senior web dev position. Their junior dev asked me about a maze solving algorithm.

I knew the VP of engineering through one of my contacts and sent him an email asking him how a maze solving algorithm relates to web development. To his credit the VP apologized and set up another interview albeit with an even more junior developer who asked about finding loops in a linked list.

sigh

Thankfully I didn't take the job because the company shut down recently.

Show the cards first. After a card is picked and before you take them to customization ask for the address to ensure it can be delivered.

wouldnt't atypical day be atypicalDay and a typical day be aTypicalDay? following camel case nomenclature the function name seems to suggest a typical day and is aptly named.

That's good to know. In my birth country growing up I remember my mom used to buy a couple of days' vegetables from a roaming vegetable vendor. The vegetables were fresh and available at the doorstep in the morning before lunch preparation began. Since we were vegetarians we didn't see or know if there were meat vendors that did this too but my guess is there weren't since these "mobile" vendors didn't have refrigeration on their push carts.

This is a thought experiment on my end:

What if there was a mobile(not cellphone) grocer that frequented locations where people might consider buying from the grocer?

A grocer truck (like a food truck) could frequent train station parking lots as designated times allowing commuters to shop a couple of days' groceries. A grocer truck could frequent central locations in a neighborhood at designated times to allow residents to walk up to the truck to purchase groceries.

Upsides:

grocery when you need it without trips to the supermarkets

purchase less but more often than a once a week trip.

convenient location and timing to do grocery shopping

no parking hassles if the model is a walk up to purchase groceries.

downsides: limited choice (can be mitigated if grocer has a mobile app)

limited supply (again if there is an app and you can preorder the items are kept aside for you for a limited time before being sold) Perishable items cannot be set aside indefinitely.

limited pick up options (grocer can field location requests and can add a location if there is enough demand for it)

All this might have already been tried but I don't know of it. What other downsides do you see apart from the fact that some people would rather order from a restaurant than cook? This would not be for those people who don't want to cook.

This is in theory a good track to start with. However there is one small hole in the theory. Self reporting by security companies on breaches is very tough to impose. We have seen what self regulation/reporting did for the banking industry. If security companies sidestep accurate self reporting on breaches they have no incentive (in fact they might be motivated to let things slide for economic reasons) to create rock solid security solutions because they know there is an insurance company who will absorb the hit.

However if you had an independent entity that rated the security companies' products that might work. Or the insurance company has a division that rates the security products and provided different rates based on which product a company decides to use.

It's as if the author has been living under a rock for the past 20 years. If he is willing to take Trump's words at face value I can't reconcile myself to the author's views. I mean Trump's priorities are good? That's what he is saying. Look at his track record at screwing people over after making promises that were "good" (Trump university, unpaid contractors for his casinos, etc.) What gives the author the confidence that Trump won't screw Americans once elected? Didn't expect this from someone who created such a thoughtful strip as Dilbert.

Fundamental research takes time. One cannot discard such research as "all talk". It is the basis on which better results will be achieved and the possibility of a useful computer will be realized.

Do also consider the side effect of outsourcing, cheaper products for Americans. If some jobs are not outsourced our products will cost 30%-70% more. There are other benefits too. If everyone who is complaining about outsourcing is willing to pay that much extra then sure, stop all outsourcing. If not, then acknowledge that outsourcing has it's benefits.

True that Apple's App Store search sucks. I'll give an example: search for Get@ and see the results. Now search for GetAt and you'll see an app called Get@. If you allow @ symbol in the app name then your search should return that app when searched for it.

This is interesting. On one hand it discontinued the iAd product and allowed Developers to go to third party Ad networks. On the other hand it provides a better experience for the user by serving ads when the intent of the user is clear and generating revenue off of it.

I think if Apple prices correctly it has the potential to reduce in-app ads considerably at the same time increasing revenue for Apple because most ads in apps are to download other apps and if relevant apps are served up via Search Ads it could be a better business model than iAds.

There are well established processes to vet someone who might be handling sensitive information. There are security clearances that can be obtained. The fact that someone is from a foreign country should not be the basis of discriminating against them.

Secondly if Palantir works on highly sensitive data it probably requires applicants to be US citizens. So essentially it is probably discriminating against Asian Americans and not citizens of other countries.

According to Pew research any effort to spread the word to register to vote for anyone below 69 years of age would be skewing democrat[1] [1]http://www.people-press.org/2015/04/07/party-identification-...

I'm sorry but the guy said it is definitely a partisan endeavor, which I don't think it is. It is merely an effort to educate young voters for the need to register to vote. This demographic has been historically known to have a low voter turnout with only 46% of eligible voters[1] having voted in 2012 election.

[1]http://www.pewresearch.org/fact-tank/2016/05/16/millennials-...

I'm sorry are you saying that there are no student republicans? that's a very misinformed opinion if you believe that.

Someone please correct me if I'm wrong in assuming this but it seems a company like AirBnb would only raise private capital instead of going IPO because it's financials suck. I mean if you were doing really well and had profits that you were pumping back into the company you would want to IPO to raise money for lower dilution right? A private round might cause much more dilution than an IPO. Maybe I'm missing something.

Thanks. Just curious as to why this was not caught during submission. The URLs are 96% same except for the bit after the #

The key point here is ownership.

Now there are multiple ways to define and transfer ownership. The primary reason for the split of dev and operations team was so that dev teams are not held back maintaining systems when there's more dev work to be done. However the split only works when deployment is a weekly or monthly activity. For Continuous deployment the dev team should be on call till the knowledge transfer can be done.

Where I work we have a split and our process works (in theory).

1. Developers go through the build, test, deploy process

2. Before deployment the dev and operations team meet and the dev team walks the ops team through the code, key changes, key functionality implemented.

3. Ops team poses their questions e.g. what assumptions were made, what are the possible values for a particular config attribute, etc.

4. Once Ops is comfortable they understand the changes the dev team turns over the application to the ops team.

5. This knowledge transfer happens in an hour long meeting with key stakeholders from both teams present.

6. This process is for weekly or biweekly deployments.

7. For a brand new project/product the dev team does a complete walkthrough with the ops team over a period of 1 week and the dev team provides a 6 weeks "warranty" period for the application where in the dev team is on call.

Just a theory but what do we know of dying stars getting a new breath of life due to nearby supernovae? Seems like the star died and material from nearby supernova seems to have drifted into it's neighborhood and jump started the star.

Well these are applications not granted visas. If a company wants to spend the application fee for that many applications then it is their choice. However it does not mean it will be granted a majority of the visas.

However in light of the fact that now a lottery is in place maybe this is tantamount to buying more lottery tickets to increase your chances of winning.

Another value add archetype might be the "sounding board" partner. This is the person that listens to you vent, provides moral support, gives advice on non-product related issues like personnel, politics, power plays, helps with strategy and negotiation, etc

Indeed I forgot about the Wannabe VC :) All jokes aside you are absolutely right that these are the guys you want to avoid like the plague because they are not invested in your success or even your journey.

From my experience I've found there are 3 types of VCs:

1. The Product VC

These are people who built a great product(s) and exited and became VCs. They know the roller coaster of making a product successful. They can provide great advice. They can identify with the struggle and provide support. They are informed about the industry because they are inherently curious people and like to know about products. They also know what kind of person will most probably succeed in navigating the turbulent waters of a start up and bring a great product to market. These are the VCs to listen to.

2. The "I won a lottery VC" These guys made a product that for some reason (right timing, right connections, right team, product/market fit) became hugely successful quickly and they exited. They had an idea for solving a single pain point and it was the right pain point to solve. With their new found wealth they behave like @johnwheeler's Shoe Button prince. Suddenly they feel like they can pontificate on any industry. Unless your product is in the same industry that the VC exited from take what these guys say with a grain of salt.

3. The Herd VC

These guys are the spray and pray variety or follow the herd variety. Both these strategies will lead them to seem like they have the Midas touch because a few of their investments will hit the blockbuster league. If you ask them what made them invest in the blockbuster they will spew the generic things. These are the guys whose money you take and ignore their advice because they really don't know what they are talking about. Their well of knowledge is shallow and wide so in your industry it won't be deep and narrow.

Not if as part of sign in the app asks permission to get that information. That is how all oAuth logins from FB to Google to LinkedIn to Github work. You ask for permission to get exactly what you want and once granted the app can get that information without violating any TOS or getting banned

That's an awesome "real world" example of where this could be used.

Never understand what's going on in someone's mind when they try to do this. This only raises more questions instead of allaying doubts about your company's core technology

he probably encoded HODOR HODOR HODOR multiple times in that video at the end.