Readit News logoReadit News
tmarthal commented on Google is winning on every AI front   thealgorithmicbridge.com/... · Posted by u/vinhnx
SkyMarshal · 5 months ago
Why does Google even have these two different interfaces?
tmarthal · 5 months ago
Google seems to do a lot of "shipping the org chart" externally.
tmarthal commented on Why You Should Write Your Own Static Site Generator   arne.me/articles/write-yo... · Posted by u/abahlo
tmarthal · 2 years ago
Such a strange abstraction layer.

Thr author could have skipped a step and formatted using tags instead of markdown and published the html directly, with zero need for any generator. Using scp and html, like it was 1998.

tmarthal commented on Ask HN: Who is hiring? (February 2022)    · Posted by u/whoishiring
CFShopify · 4 years ago
Shopify is a leading global commerce company, providing trusted tools to start, grow, market, and manage a retail business of any size. Shopify makes commerce better for everyone with a platform and services that are engineered for reliability, while delivering a better shopping experience for consumers everywhere. Shopify powers millions of businesses in more than 175 countries and is trusted by brands such as Allbirds, Gymshark, PepsiCo, Staples, and many more. Check out some of our open roles including: Infrastructure Security Engineer (Remote, United States) - https://smrtr.io/7LHxd Staff (Lead) Data Scientist (Remote, United States) - https://smrtr.io/7WzB_ Senior Data Engineer (Remote, United States) - https://smrtr.io/7WzQM Staff Data Engineer (Remote, United States) - https://smrtr.io/7WzWg Data Science Manager (Remote, United States) - https://smrtr.io/7WBb_
tmarthal · 4 years ago
^ those are the job reqs for the central recruiting across the company. Thanks 'CFShopify' for posting. =)

I'm a Dev Manager in the Shopify Fulfillment Network. If anyone is interested in talking about the culture or what working at Shopify is like, feel free to hit me up on twitter @tmarthal or email tom.marthaler@shopify

tmarthal commented on Hire-to-fire at Amazon India?   leetcode.com/discuss/comp... · Posted by u/bobjones334
amazon_throw · 4 years ago
Like I said, I don't doubt that they happen, but given that you've also left the company and seem to have hit one of these areas of toxicity yourself, I'm not surprised you'd think so. Who was your last manager? I'm curious if it's anybody I know?
tmarthal · 4 years ago
> seem to have hit one of these areas of toxicity yourself

Have you considered that the original poster's experience is actually the norm and that your experience is the one that is the anomaly? I was 1 for 2 in organizations with shitty leadership, and the organization that was run properly had zero open headcount. Everywhere people are hiring into is not one of the "good ones".

Check out the old-fart tool, 85% of the company has been at Amazon for 3 years or less. Do you think that if the normal/average organization/team was a great place to be, that there would be so much attrition?

tmarthal commented on OneWeb, SpaceX satellites dodged a potential collision in orbit   theverge.com/2021/4/9/223... · Posted by u/advpetc
tmarthal · 4 years ago
> collision probability of 1.3 percent, with the two satellites coming as close as 190 feet (50m)

LEO orbits have speeds around 7.8 km/s (rounding up to ~8000m/s for quick calculations) - this avoidance detection is saying that the two satellites both traveling at 8000m/s would be in the same 50m box at the same second.

A quick calculation shows that the collision avoidance is operating at least the millisecond level to predict this collision (50m/(8000m/s) ~.005 seconds.

One thing someone once mentioned to me is that space is big and things travel fast. It's hard to believe that the two satellites (most likely each <1m in diameter) came "close" to colliding, when a half second later they would be 8000 meters apart.

tmarthal commented on I'm a Google SWE that's coached 50 through the FAANG interview process. AMA    · Posted by u/coachdarek
michaelt · 6 years ago
> evaluating the tenacity [...] able to work hard—even on things they don't choose to work on.

By that logic, surely every interview practice is justified? And the less related to the job, the better?

I could ask a programmer to build a wooden boat, become a proficient opera singer, or complete four marathons in a year.

tmarthal · 6 years ago
> By that logic, surely every interview practice is justified?

In a sense, they are. As long as the interview practice is well understood by the applicants, it only leads to filtering the applicants that cannot pursue the requirements for that practice. Granted, the FAANG interview process and filtering only works because the SWE jobs are desirable enough.

I understand that the required practices and filtering also lead to a certain type of applicant. This is the main fault of the system (the lack of diversity potential).

tmarthal commented on On Internal Engineering Practices at Amazon   jatins.gitlab.io/me/amazo... · Posted by u/wheresvic1
throwaway504 · 6 years ago
Isn't that a bit disingenuous? Your role at Amazon is nothing like the typical engineer at Amazon. You live in the shiny new world while the majority of engineers are stuck on something that's not too far from the article.
tmarthal · 6 years ago
The median tenure of engineers at Amazon is 1 year. That means that the new engineers need senior and principle engineers to guide them on what tools exist. If an engineering organization happens to have strong senior Amazon engineers then they can guide their teams/org to use the tools that exist, because they do exist.

However, everything (and I mean everything) at Amazon depends on the team (and organization) that you land in. Some organizations do not have senior technical leadership; service ownership is handed off to teams without long tenured Amazon engineers so they do not get exposed to the types of tools to use (nor do these teams get time to discover, learn, and on-board to the tools that do exist). This is how an engineer can have the experience written about in the article.

The article is anecdotal, and definitely not the norm for the "majority of engineers"

tmarthal commented on The Case of the Broken Lambda   veekaybee.github.io/2018/... · Posted by u/josep2
doombolt · 7 years ago
That's a rude awakening but an expected one. It's very easy to write an elegant piece of code in scripting language only to find that some of dependencies who work magic are pretty messy to deploy.

You can usually count on having native libraries for a given activity for Java, so you can just use a JVM-based language (does Lambda support that? I bet it does.)

tmarthal · 7 years ago
Further down the article she mentions that she solved the dependency by "I ended up rewriting the Lambda in Java", noting that the use-case doesn't care about the known JVM warmup times.

The POM packaging and jar based deployment seemed to make the dependencies work.

tmarthal commented on How Bad Are Zillow “Zestimates”?   blog.duvora.com/exactly-h... · Posted by u/duvora
mholmes680 · 9 years ago
point taken, but two observations:

1) its ridiculous to also "fix" the zestimate history. Put the old one in the history, and explain near the chart what rejiggered.

2) The market in my immediate area, as evidence by the comps from zillow and the sales prices in the newspaper, has only increased. The conservative comps are near the old zestimate - this is a suburban area. The wild ones are higher than my private estimate.

tmarthal · 9 years ago
I think what you're actually seeing is the output of a Kalman Filter temporal model. The zestimate is the mean of the filter output, but the error bounds of the filter are more important than the actual mean/reported value.

What happens is that the model uses trends to extrapolate from each "real" data point (in this case, a house sale in your neighborhood). The problem is, and what Kalman Filters help manage, is the uncertainty propagation between each house sale. When it has been a long time from when a sale has occurred, it is unclear what the real/actual price is of a home. This means that on the estimated price the error bounds are large, and zestimate still just reports the mean value of this huge uncertainty.

What then happens is that a house is sold in your area, a new data point is recorded, and the filter re-adjusts itself and collapses its uncertainty/error bounds in the time of that measurement around the measurement. And you get correction. This is why the "old zestimate" is updated.

u/tmarthal

KarmaCake day205March 9, 2009
About
web analytics / math / data / java / python / awesome

los angeles, ca

View Original