159 karma · joined July 8, 2018
"Level headed" and "sober" people are not immune to the effects of incentives and conflicts of interest. Researchers are dependent on grants, on invitations to conferences, etc., and so are liable to follow trends (tariffs bad), and p-hack to support the mainstream narrative (as they do in this analysis with P values > 0.01).
> German academia is actually full of sober, level-headed, nuanced people
Thanks for the laugh. I hope you realize how pretentious this sounds. In actuality, Germany's GDP is about 1/6th of that of the US, so these German academics don't sound very bright for how "level headed" and "sober" they are.
The claim of this analysis is a significant backpedaling on the narrative they've been wrong about regarding the effects of tariffs. Instead of trying to reposition the goal posts on the effects of tariffs, it would be far more productive to simply acknowledge that the original dire predictions of tariffs did not manifest.
On one hand, LLMs do require significant amounts of compute to train. But the other hand, if you amortize training costs across all user sessions, is it really that big a deal? And that’s not even factoring in Moore’s law and incremental improvements to model training efficiency.
It doesn’t really matter how you manage changes to feature flags, but using version control gives you a couple of nice benefits:
* gives developers the opportunity to describe their change
* let’s you roll back a problematic patch
* blame and bisect problematic patches
Ideally, you should also be able to see your feature flag changes in prod much faster than it takes to cut a release. You need this in order to be able to quickly roll back bad features.
> What feature flag tool do you use?
See https://engineering.fb.com/2017/08/31/web/rapid-release-at-m...
Ad hominems are against TOS.
Answering the question is irrelevant if it’s the wrong question to begin with. And for the wrong circumstances (ie if this is a family vacation) can be counter-productive. It’s far more productive to zoom out, ask why the author is asking for advice to study react on vacation, and address that instead. Consider this as you advance your career past recent college grad / swe1 :)
I don't see the problem with developers using flags for configuration as a stopgap until there's a better solution available.
Not necessarily. At the large companies I've worked at (>200 people), a UXR will drive the interview process with users, starting with compiling a list of questions from engineers, then conducting the interview sessions with users in which engineers can sit in, and then disseminating the insights and setting up a meeting to make the insights into a actionable engineering projects.
Working with UXRs is a dream, as they're trained to conduct interviews in an impartial way, leading to insights that are less biased and higher quality. Contrast to when I worked for startups and I or someone on my team would interview users, very often the feedback would end up contaminated because the interviewer would ask the wrong question, projected their biases into the questions, or even worse into the insights.
2) Zero downtime on a day 1 launch at the scale is a very impressive technical feat. If it had been rushed or released prematurely, this level of app stability would not have been the case. If I had to guess, this would be the reason why Bluesky hasn't been able to release to the general public
In terms of the app being a foundation that will be built on and cannibalize Twitter, I'm very bullish on the future for Threads!
You can "deactivate" your account and delete all of your posts individually, which is effectively equivalent to deleting your Threads account.
> For moral reasons, I don't want to hire someone who worked at Facebook.
That's quite a hostile and closed minded take, but an understandable cope for someone who could never hire a FAANG engineer in the first place.
Job searching while unemployed can be nice, but it's better to be safer than sorry and have a future job lined up.
Another thing to keep in mind is that not many companies hire during the holidays, so the best window you'll have to conduct your job search is now. Otherwise you're likely going to likely have to wait until January to begin job searching.
I used what I learned from reading the articles on their site to implement my own input prediction and rollback netcode for my personal side project. It's a pretty useful resource, and helps organize my project in other ways too such as informing me of ways I can structure event messages, handle input valuation, etc.
Remote: Ideally no
Willing to relocate: Yes
Technologies: Professional: Typescript, React, GraphQL, gRPC, Postgres, Rust; For Fun: Go, Kotlin, Python
Résumé: fermidirak.github.io/resume.pdf
Email: manuelebryan[at]gmail[dot]com
I'm a full stack developer with 3.5 years of experience. My area of expertise is in frontend and in frontend tooling. In the past, I've worked on frontend infrastructure teams as well as product teams at startups and early stage companies. I like working on ambitious projects in interesting domains.
I also find that Leetcode translates really well into the code I write in my freetime (a roguelike. Real work is boring fullstack crud). I personally hate reaching for libraries in my side projects, so being able to have these data structures and algos at my fingertips and being able to implement say A* or a weighted rng function or something else on the fly has been super handy. I honestly don't think I would be able to implement a vertex fragment shader w/ lighting without the skills I've picked up from Leetcode grind.