lucun

lucun t1_j7eoif3 wrote

Alphabet likes to hide costs and net income of segments unlike how granular they break down revenue. Might be a good thing since it can shield those segments from greedy investors and competitors. It's also hard to breakdown as I've heard they do have engineers that do work affecting multiple Google segments at the same time, which makes it hard to attribute costs accurately.

4

lucun t1_j7enx13 wrote

You're better off just reading the earning report yourself than trusting reddit to do that for you. The YouTube $29B revenue in the chart is actually YouTube Ads. The Playstore and Other $29B in the chart includes non-ad revenue from YouTube and many other things.

YouTube is tricky since Alphabet sort of hides YouTube's total revenue and net income.

7

lucun t1_j29tmdw wrote

One thing is that a bullet, when fired, accelerates down the barrel over time, applying a lower force over time. However, when it hits a hard target direct on, the velocity comes to an immediate stop, which means a suddenly negative acceleration, jerk, and very high force (F=m*a). This is why hollow points tend to have better stopping power than FMJ that go right thru a person.

Also, the recoil of shooting a high caliber handgun or rifle does leave some soreness in the hands/shoulder.

7

lucun t1_ity08i6 wrote

From the graph's OP:

>Also for the language categorization, only the TITLE of the job offer has been analyzed. This means that for example, a title of "Backend developer" would be discarded, since it does not contain any language or stack valid on it. Analyzing only the title also filters out offers that require many languages and are fuzzy.

I get the negative pickiness about this sub, but he's really not being picky. The data is bad, suboptimal, and misleading. Most companies do not list job postings with very specific "language x developer" and sometimes put languages in the job details, so OP's very limited sampling method is a flaw. The last thing we want is a bunch of new CS students hyper focused on learning Solidify for the big money, but only to learn that most companies don't even know about that language or even allow answering technical interview questions with Solidfy.

4

lucun t1_itxyroh wrote

Depends on where you work at in the stack, but normally yes higher level languages are everywhere and assembly is very uncommon. I've only had to code in assembly once in my career, and it was for a very specific piece of equipment to do an overly specialized 200% performance optimization that the C++ compiler wasn't intelligent enough to do for an overly specialized use case for that CPU.

1