1,694 karma · joined December 19, 2017
My favourite one ( still happens ) is having to mute then unmute at the beginning of the conversation otherwise nobody can hear me. It was so common, with people fiddling with their headset, calling again etc that I eventually asked everyone exhibiting audio issues to start with this
Another interesting one is that if you’re not connected properly , you send messages , but never get notified that they never left, and are never notified that you’re not connected.
It’s also a resource hog and will eat your machine for breakfast.
The list goes on and on, it’s very surprising.
Blows everything else out of the water.
https://pernos.co/ ( I’m not affiliated to them in any way, just a happy customer)
It’s essentially IT/data work - the days of sophisticated maths are mostly gone. There always was a lot of code, but these days for most people there’s little to no new maths.
From what I’ve seen, post-2008 the job changed significantly, with more IT, less maths, more standardization - basically the job moved from bespoke everything to super industrialized. You’ll be able to have your model work for one underlying and one product, but what’s really useful is for lots of underlyings and many products - and that’s very hard.
That being said, and that’s important, you must understand the maths behind, otherwise you won’t be able to do anything useful.
‘Sorry I don’t know anyone called ‘your girlfriend’’ The kids find it hilarious
( disclaimer : I know nothing about football !)
Or should you start the rule with ‘you’ve been drinking everyday for a while’?
It’s the real life exchange rate for algorithms and data structures. Basically understanding your infrastructure and its performance characteristics will help you design simpler ( and therefore better )systems
I changed my mind after playing with cursor 2 ( cursor 1 had lasted all of 10 mins), which actually wrote a full blown app with documentation, tests , coverage, ci/cd, etc. I was able to have it find a bug I encountered when using the app - it literally ran the code, inserted extra logs, grepped the logs , found the bug and fixed it.
Where I am, 3 year old is greenfield, and old and large is 20 years old and has 8million lines of nasty c++. I’ll have to wait a bit more I think …
I think it’s unlikely it will succeed at that task with a real world , old, large codebase.
Now, the next release might work !