It is what is weird to me. Those leetcode problems seems weirdly designed, some even seems counterproductive. I've juste been offered an interview about easy-medium level leetcode questions. I went to the site and ... the easy questions seems to be fundamental questions that no one deal with in real life. Medium are some common practical problems that were implemented and optimised in standard libraries a long time ago. Hard problems are actually fun to deal with and probably more revealing about myself. What am I supposed to do ? ask for difficult problems only ?
Yup similar experience here. Field and experience should be taken into account when offering leetcode interview. Maybe langage should be added too. In python for exemple there are lot of standard library that implement and optimise the leet code stuff.
The tweets / medium article are a bit incomplete. But they mean at least:
- Authors didn't make decent efforts to build a robust baseline. Worse it seems that they have purposefully built a bad baseline to make their solution look better.
- Authors didn't really disclose full performance. Statistical performance is one thing but time complexity is another. Hopular needs 10 mins on a 500 rows datasets. That's a NO NO for any serious application.
- Authors didn't provide an easy to use interface. You can't really claim SoTA on small tabular data with something that isn't testable by everyone.
Hey a bit late to the party (HN newsletter crowd). This really seems like something my BigCorp could use. I am on holiday RN, so I won't fire my computer to try it. But I was wondering, does it allows easy copy pasting the table into standard MS documents (work ? outlook mails ?).
The whole thing read like a humble brag... "As a powerlifter, I workout 4-6 days per week", " I would have the third-highest new offer on Levels out of over 200 offers on their site" .. .etc.
It was 30 when the price was at 33 and musk wasn't on the picture. Someone's buy nearly 10% on the open market then bidding for a significant chunk of the rest is new info.
I've jsut discovered this approach with python. I usually used google and cookbooks. But I often found myself in position where I tought 'surely there must be a better way to do it'. Reading the standard library really helped me understand how to do some stuff. Best way I found to enforce what I learnt was to rewrite some code with minimal imports.
I work for the government so really know this feeling. I have a funny exemple in mind. Months ago I got pulled into a meeting because 'I know data'. The phrasing alone was a red flag. Lots of high level people in the meeting. Like 10 people, each one payed at least twice as much as me. The goal is to transfer data that is too big for our 'standard pipelines'. They are discussing building a whole new pipeline, contractors would be involved and all. I asked 'stupid questions':
"- How big is the data we are discussing ?
- '200 Go'
- is it recurring ?
- No
- is it sensitive ?
- No
- Why don't we buy a 50$ 1to hard drive and transfer the data manually ?"
Last question was followed by the longest silence I ever heard in a meeting... I wasn't invited the next meetings. I heard it took them more than 5 other meetings to reconsider my solution. An intern has finally been sent to buy the hard drive last week.
