I'm pretty sure whoever designed this control usually makes gender selectors for websites...
Poly Bridge has a language SLIDER.
so they won without placing any bridge pieces? that sounds hard.
Sadly, no: they've moved to a much more sensible drop-down
name length: [slider 1-10]
letter 1: [slider a-z]
letter 2: [slider a-z]
letter 3: [slider a-z]
1. the leaderboard contains videos. these are just mp4 files of the game being played
2. the leaderboard contains the data for the bridge designs, and it's being rendered in-game
and even though people aren't hacking 0$ wins into the leaderboard now doesn't mean they aren't cheating. They just do it with physics, not RAM hacking
They made a "bridge" which is a bit of dense road that falls and crushes the car, but since cars can't "crush", the physics engine ends up squirting them out like a watermelon seed
1. it's talking to cloudflare
2. it's using TLS
3. it's probably about 750 kilobytes for one playback
and #1 and #3 mean it's probably just videos. tiny videos.
does it compress the videos in the client and upload them to the server?
or does it upload the solution to the server and let it render them?
More from foone
Everyone likes to forget this episode just because it's terrible, but we were really sleeping on inherent comedy in a unfreezing an investor 300 years in the future and having them discover we've transitioned to a moneyless post-scarcity utopia.
it's like a classic twilight zone episode.
in fact, it IS a twilight zone episode.
The Rip Van Winkle Caper, Season 2, episode 24.
Four criminals steal a million dollars of gold bars, then put themselves in suspended animation for a hundred years to hide from the law.
they wake up, then start killing each other from mistrust, then the last one dies in the desert, as he offers a gold bar to the driver of a passing car, asking for water and a ride into town
the confused driver walks back to his car with the bar, and his wife asks what the gold bar is.
he says something like "It's gold... they used to use this for money, before we figured out a way to manufacture it."
He tosses it away, and drives off.
— Star Trek Minus Context (@NoContextTrek) January 28, 2021
it's like a classic twilight zone episode.
in fact, it IS a twilight zone episode.
The Rip Van Winkle Caper, Season 2, episode 24.
Four criminals steal a million dollars of gold bars, then put themselves in suspended animation for a hundred years to hide from the law.
they wake up, then start killing each other from mistrust, then the last one dies in the desert, as he offers a gold bar to the driver of a passing car, asking for water and a ride into town
the confused driver walks back to his car with the bar, and his wife asks what the gold bar is.
he says something like "It's gold... they used to use this for money, before we figured out a way to manufacture it."
He tosses it away, and drives off.
More from Software
@JuliaLMarcus @Iplaywithgerms This paper gives documentation on software (with causal reasoning, assumptions reviewed in appendix) for a parametric approach to estimating either "total effects" or "controlled direct effects" with competing events and time-varying
@Iplaywithgerms Total effects capture paths by which treatment affects competing event (e.g. protective total effect of lifesaving treatment on dementia may be wholly/partially due to effect on survival). Controlled direct effects do not capture these paths
@Iplaywithgerms More detailed reasoning on the difference and tradeoffs between total and controlled direct effects and causal reasoning in the point treatment context provided here along with description of some estimators and
@Iplaywithgerms If you are familiar with more robust approaches like IPW or even better TMLE for time-varying treatment, these are trivially adapted to go after the controlled direct effect by simply treating competing events like loss to follow-up (censoring). e.g.
@Iplaywithgerms Examples of IPW estimation of the total effect of a time-varying treatment described in Appendix D of this paper:
https://t.co/RNhcgTBMkb
And here
https://t.co/rMWmwFBWwV
Others in reference lists of above papers.
@Iplaywithgerms Total effects capture paths by which treatment affects competing event (e.g. protective total effect of lifesaving treatment on dementia may be wholly/partially due to effect on survival). Controlled direct effects do not capture these paths
@Iplaywithgerms More detailed reasoning on the difference and tradeoffs between total and controlled direct effects and causal reasoning in the point treatment context provided here along with description of some estimators and
@Iplaywithgerms If you are familiar with more robust approaches like IPW or even better TMLE for time-varying treatment, these are trivially adapted to go after the controlled direct effect by simply treating competing events like loss to follow-up (censoring). e.g.
@Iplaywithgerms Examples of IPW estimation of the total effect of a time-varying treatment described in Appendix D of this paper:
https://t.co/RNhcgTBMkb
And here
https://t.co/rMWmwFBWwV
Others in reference lists of above papers.
Developer productivity, y'all. It is a three TRILLION dollar opportunity, per the stripe report.
Eng managers and directors, we have got to stop asking for "more headcount" and start treating this like the systems problem that it is. https://t.co/XJ0CkFdgiO
If you are getting barely more than 50% productivity out of your very expensive engineers, I can pretty much guarantee you cannot hire your way out of this resourcing issue. 😐
(the stripe report is here:
Say you've got a strategic initiative that 3 engineers to build and support it. Well, they're going to be swimming in the same muddy pipeline as everyone else at ~50%, so you're actually gotta source, hire and train 6, er make that 7 (gonna need another manager too now)...
...which actually understates the problem, because each person you add also adds friction and overhead to the system. Communication, coordination all get harder and processes get more complex and elaborate, etc.
So we could hire 7 people, or we could patch up our sociotechnical system to lose say only 25% productivity to tech debt, instead of 42%? 🤔
By my calculations, that would reclaim 3 engineers worth of capacity given a team of just 17-18 people.
Eng managers and directors, we have got to stop asking for "more headcount" and start treating this like the systems problem that it is. https://t.co/XJ0CkFdgiO
When people often have to spend weeks just to get a local development environment up, there is a lot to improve. \U0001f641
— Daniel Schildt (@autiomaa) December 20, 2020
If you are getting barely more than 50% productivity out of your very expensive engineers, I can pretty much guarantee you cannot hire your way out of this resourcing issue. 😐
(the stripe report is here:
Say you've got a strategic initiative that 3 engineers to build and support it. Well, they're going to be swimming in the same muddy pipeline as everyone else at ~50%, so you're actually gotta source, hire and train 6, er make that 7 (gonna need another manager too now)...
...which actually understates the problem, because each person you add also adds friction and overhead to the system. Communication, coordination all get harder and processes get more complex and elaborate, etc.
So we could hire 7 people, or we could patch up our sociotechnical system to lose say only 25% productivity to tech debt, instead of 42%? 🤔
By my calculations, that would reclaim 3 engineers worth of capacity given a team of just 17-18 people.
