Hacker News new | past | comments | ask | show | jobs | submit | tydok's comments login

Ask more? The book is expensive. If he lowers the price, say to $10, the sales will probably increase 10x.


I highly doubt sales would increase by 10x, or even 2x.

This book isn't trying to sell itself by saying "hey, buy me and you'll be entertained for three hours, which is a better value than a movie ticket".

This book is trying to convince potential customers that it will help them graduate from junior engineer at local_company to senior engineer at FAANG. It's no coincidence that the author mentioned right here in his opening post that he landed a senior role at AWS. (I realize that's not a dream for many, and the whole FAANG thing is aggravating, but enough people think this way.)

If you (as a potential customer) aren't convinced, then you have no reason to buy this book even for $10.

On the other hand, if you are convinced, then the upside is so large that this book is worth buying even for $500.

Not many people will be on the edge pondering "I really think this book could help me triple my salary and status but that's worth $10 to me, not $40".


[flagged]


> your pointing to his job title as if he's some genius

No, that's just you projecting.


Then why does him being a "senior level faang employee" matter so much? This doesn't qualify him for anything.


I did not point to him being a senior engineer at FAANG, I pointed to him mentioning that he's a senior engineer at FAANG, as evidence that the book is marketed towards people who also want to become senior engineers at FAANG.

As mentioned in my original comment, I fully realize that plenty of people couldn't care less about becoming senior engineers at FAANG, and am not making any claims about the intelligence or qualifications of the author or the quality of the book.


It depends on the price elasticity of the product and that's a known unknown.

So every product starts as high as possible to discover the price. Because there will be time to lower it.

(Increasing the price afterwards never works, because early adopters are more elastic)


> How far should we go in making things generic ?

Never make things generic apriori.


> which is probably some trivial math...

The clock hand problem can be solved with the Rule of Three

https://en.wikipedia.org/wiki/Cross-multiplication#Rule_of_T...


Yeah, but perhaps the 90% of each 5% is common to all users.


Firstly, a client will have 10 outgoing video streams at most, not 100!

Secondly, if we consider receivers bandwidth, a client can encode 2 or 3 video streams, e.g. low, medium, and high quality video.


I think he's saying the server would have to handle 100 streams. 10 clients * 10 streams each.


Still, isn't it one stream per client? Why 10 streams each?


If you're all connecting directly to a streaming server (instead of using something p2p), the server will have 10 connections for inbound video feeds and then 10*9 open outbound video connections to send each video to each client connection.


> 100 outgoing video feeds. Not many machines can encode 100 video feeds in realtime

The server will send 9 video streams to each connection, but it has to process only 10 video streams since it will send the same video data to all clients, if we ignore client bandwidth.


> if we ignore client bandwidth.

The parent post explicitly took the client bandwidth into account, that's why it was 100 instead of 10.

But your point about 10 vs 9 still stands. Still, 81, and if you bucket into 3 tiers, that's still 27. Which at least scales linearly instead of quadratically.


Exactly. It scales linearly, not quadratically. I forgot to mention that since clients do the "original" encoding, the server actually does less work (regarding resolution tiers).


agreed. do not agree with OP that all 100 require transcoding


I wonder if OP meant "1 outgoing and 9 incoming" streams.


The fundamentals are about positional elements and strategic principles.

For example: Relative value of the pieces, Control of the center, Pawn structure, Tactics, Initiative, Tempo, Opposition, Keep the position balanced, Develop multiple ideas/areas (strategy), Control open lines (files/ranks/diagonals) and crossings


Yes, it's indeed a property, not a problem. The problem is the accidental complexity which has the tendency to increase and requires constant effort/energy from us to keep it low.



"I have yet to see an interesting piece of code that comes from these OO people [...] It claims that everything is an object. Even if it is true it is not very interesting"


We use double buffering to avoid flickering, but still we have to clear the back buffers.


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: