Hacker Newsnew | past | comments | ask | show | jobs | submit | engie's commentslogin

Synergy worked great without perceptible lag for normal desktop stuff in the late 90s (including across all the steam powered pcs in the school computer room).


I chatted to a Facebook engineer at one of the early HN London events back in 2013, got talked into sending through a CV and I've been with ... Meta ever since.

Very grateful to this community as it had genuinely never occurred to me to apply to work for big tech. Which is obviously dumb, I've been obsessed with the industry since the early 90s, a good reminder that goals and sense of possibilities can be surprisingly blinkered by our environment/culture.


It never occured to me either because I expect leetcode wars and gatekeeping, but maybe 10 ago was different?


How many problems do you need to grind to get hired


A lot more today than in 2013, afaik. I know quite a few people who got hired at Fb back then who can’t get hired there now.

I’d say at least 200 problems, if no leetcode experience prior. Maybe 100 if you’re just refreshing. In both cases, I’d say there’s still a ton of luck involved. You can get interviewers who just won’t hire you no matter how well you do on the problem. I think 100/200 is still low for how the industry is today, to ensure at least one reasonable offer.


Where are the London or UK-based meetups advertised?


This is the key observation - hitting breakpoints in efficiency that let us remove active cooling, silicon area or heatsinks reduce weight, cost & complexity.


Yep. High efficiency is also the key to the crazy high performance we see in high end EVs these days. Going from 96% to 98% drivetrain efficiency only gives you 2% more battery life but it doubles your power output.


Latency can be a key consideration. Async style code can make it a lot easier to fire off a set of requests in parallel and wait for all the responses to come back (e.g. with https://docs.hhvm.com/hack/asynchronous-operations/concurren...), rather than the serial request waterfall a basic thread-per-request model will push you towards.


Being able to move the bulk of building an offshore turbine into a factory could lead to amazing economies of scale. It'll be an incredible assembly line to pull together 10,000 ton of materials but if we need to build hundreds of thousands it might well be worth doing. There should be a gentle stream of these things bobbing out into the sea, ready to be taken by tug to their resting place.


Where do you think wind turbines are currently manufactured? Sure, off-shore makes many of the transportation issues much easier, but final on-site assembly is pretty streamlined already no matter what site category.


I hope being able to assemble the turbine & the "foundations" together in a factory brings better economies of scale than factory turbine with foundations built in situ.


Read tracking is a feature of many/most popular chat clients (certainly hangouts, messenger & whatsapp), and anecdotally it seems to be valuable. Of course, everyone would love to see the read status of other people yet be able to control their own read state (there are endless browser extensions promising this for chat apps, a tremendous self compromise vector). Will it ever be possible to offer this in a federated system or will it be limited to the walled gardens?


> everyone would love to see the read status of other people yet be able to control their own read state

This should just be a first-class, front-and-center feature already. Everybody plays this game. It's so stupid.

Just let me skim my messages at midnight without signaling to co-workers that I'm up and that they should feel free to continue bothering me.

Also better that other people do the same to me so I don't keep sitting there like an idiot waiting for a response that isn't going to come.

Remember status messages? Available / away / idle? That you could set manually? Before Google Hangouts decided that everybody who owns a phone should just be green all the time, which EVERY OTHER CHAT APP decided to copy? So fucking stupid.


* Remember status messages? Available / away / idle? That you could set manually?*

Remember AIM away messages that would auto respond to friends with a custom message if you were logged in but AFK or even sitting at keyboard but wanted some quiet?

I miss it.

So much so that I’ve started writing an auto-responder for slack because despite having a “Presence”/Status feature that I use very judiciously (In a Meeting/On a call/Gone to Lunch/PTO) I’ve found-across multiple jobs-people barge right through them, then follow up with emails asking “are you available for a moment?” when I’m really trying and desiring focus (and also because I’m not signing up to someone else’s hosted SaaS service to do this).


Ye ... you quickly forget how good things used to be. Remember talking in voice chat without SaaS anti-echo and -noise filter lag? Or not having everything spam my notice bar in Android so that I miss sms:es and missed calls?

Things are getting out of hand shitty with these adcentered A/B big data UIs.


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

Search: