250 karma · joined January 17, 2008
Each run generates a timestamped folder with not only the bash script, but also a copy of the configs used to generate it, and all the data that the commands in the bash script needs (json files). I find this style of generator a common pattern for commonly used but frequently tweaked scripts.
Remote: Yes (willing to come to office occasionally)
Willing to relocate: no
Technologies: Java, Scala, Ruby, Python, C++, SQL, No-SQL, GraphQL etc
Resume: https://srikanthak.name/files/srikanth_resume.pdf
Email and other contact info: see resume
Worked on large cross-org projects at bit companies and built stuff from ground up at early stage startups.
Not interested in working on AI/ML or FinTech.
- I ask for a resource - you give it to me - any linked resources (stylesheets, scripts, images etc) are up to me to request
Therefore there is no "ethical" conundrum in blocking ads. The ad industry brought this on themselves by trying to push malware, spam and actively trying to make the web worse.
The water surrounding the vacuum instantly vaporizes and creates bubbles of water vapor. Then these small vacuum bubbles collapse and create small shockwaves that create noise and damage the propeller/screw.
Like a time when there was no crazy ruler.
Also the "cascading" nature of CSS makes it hard to reason about.
They only just came out with the GR III (the II was almost no change and didn't do well).
Their design choices are baffling. You could set up the GR to have tactile physical controls for all the things you may want to change on the fly, but the GR III has a touchscreen instead. It also has a 30% lower battery life (which wasn't exceptional to begin with).
Though I suppose the USB-C port is an improvement.
Political candidates also share names with other people. Name based filtering can silence unrelated people. See how well our no fly lists are at targeting people who just happen to have the wrong name.
For every problem, there is a simple solution that is wrong. Getting things right is often not simple.
I figured I'd give it another go with more experience, so the second time I was hired at L5 (expected to be leading teams). Liked it even less the second time, but stuck around for about 2 years for logistical reasons.
In my experience at Google and other large companies, the team you join ends up dictating your experience. I would be open to a third stint at Google, but would be very careful about vetting the team (especially the leadership).
Having said that, I don't think I like the culture at Google. Especially the second time, it felt very mercenary and there was cutthroat competition. It didn't feel like I was working on a cohesive vision, but just moving protobufs around. I think I preferred Google when Eric was CEO, maybe because it was smaller, but it felt like Larry was running Google with too much emphasis on the bottom line and not enough on product or vision.
Disclosure: I worked at Google twice.
I find myself thinking the exact opposite. When you want to do something quick and dirty JavaScript or Ruby are my go to. When you want to do something right, do it in Haskell or Rust.
The middle of the road options I find are worse for anything.
Unless you want to hire big teams. Java, C#, Go are great for that.
― George Bernard Shaw, Man and Superman
https://www.livescience.com/24694-identical-twins-not-identi...
paper (PDF) : https://www.researchgate.net/profile/Constantin_Polychronako...
- Your "friends" are known and tracked
- The content you view is determined by your browsing history, ad tracking and that of your "friends"
- The composition of the audience that's voting is poorly informed and susceptible to non-critical thinking (YMMV)
On both of them:
- Stories are posted to maximize your outrage/other emotional response
- Content of stories rarely matches the titles
Social interaction and even a like button is not the problem. What the like button does is the problem.
What the interviews invariably show is that a chat client is not simple. It's extremely complicated, especially when you want it to work at scale. If you think it's a "simple" app, go ahead, try to make one - even on a whiteboard.
I can completely understand why instant messaging can get you $700 million in revenue. As for the losses -- they are invested in the future of the company and I think are justified.
"How hard can it be?" is something we ask about "simple" stuff everyday, and the answer if you dig deeper is almost always "Much harder than you think."