- I don't know how typical teams work, but in my case, new projects always come on top of other obligations. It may take 1 day to add the field, but how many meetings, fires, or other disturbances will happen during that day?
- It works fine for some simple tasks, but it fails at harder tasks. My struggle is to have the discipline to use it a the right time. I tend to become lazier and lazier, deploying code that I don't fully understand.
- > My hire/no-hire ratio is literally 50:1
80% of the candidate I interview pass (leetcode style coding interview, as mandated by the company). This is actually annoying because I'll probably have to raise the bar and start rejecting very good candidates.
- So what these people do if they can't find a job?
- I work in a FAANG as a SWE. I'm not the on selecting candidates, but I do interview a lot of them. I'm pretty sure I've never seen a 50+ year old candidate. 99% of the candidates have less than 10 year experience, and are in their 20s or 30s.
So yes, ageism is real. I suppose the company gets away with it by saying they look for candidates with 3-10 years of experience?
At that stage, I think I would pass Leetcode with 2-3 months of practice, and I don't mind putting the work if this is what it takes. I'm just not sure I'd be given the chance.
- I have a friend who behaves similarly on linkedin and in real life, and he's very blunt. I like how he calls out some crap on linkedin posts, and nobody dares to like his comments, even though I'm sure everybody approves.
Overall, I don't see anyone I know being a cringe bootlicker on LinkedIn. These people are very visible, but probably a small minority of users.
- In my big tech company, you don't want to be dismissive of AI if you don't want to sound like a paria. It's hard to believe how much faith leadership has in AI. They really want every engineer to use AI as much as possible. Reviewing is increasingly done by AI as well.
That being said, I don't think that's why reviewers here were so cordial, but this is the tone you'd expect in the corporate world.
- Maybe R is fine for people who use it all the time? but as SWE that occasionally needs to do some data analysis, I find it much easier to rely on tools I know rather than R. R is pretty convoluted as a language.
- I don't think it took the web to understand that. Trump just made it more obvious.
- > believed in its ideals to do the right thing
Do the right thing to serve their own interests.
- > If so, how do you keep yourself motivated to solve multiple problems a day, especially knowing you are actually never going to work on such problems as part of an actual job?
Personally, it's because I'm not going to use that in my job that I find leetcode entertaining. I don't feel like I'm working when playing leetcode.
- > I am a software engineer with about 20 years of experience
I personally don't think years of experience is a relevant number. I'm a median senior software engineer in a big tech company. Most of my teammates are 20-25 years younger than me and have the same level.
I don't have more experience than them for most of the things we do in our job. Whatever I was doing 25 years ago is barely relevant today.
Basically, I still do what've always been doing: try to work on projects I find interesting, keep learning, try to contribute to the best of my abilities.
- I wonder if it means Meta will move away from their OSS commitment. Wasn't it largely pushed by LeCun?
- > he failed pretty bad at the LLM race
Was he even involved in this?
- > is it about doing, or is it about getting things done?
It's both. When you climb a mountain, the joy is reaching the summit after the hard hike. The hike is hard but also enjoyable in itself, and makes you appreciate reaching the top even more.
If there's a cable car or a road leading to the summit, the view may still be nice, but I'll go hiking somewhere else.
- Pretty much my experience, LLMs have taken the fun out of programming for me. My coding sessions are:
1. write prompt
2. slack a few minutes
3. go to 1
4. send code for review
I know what the code is doing, how I want it to look eventually, and my commits are small and self-contained, but I don't understand my code as much because I didn't spend so much time manipulate it. Often I spend more time in my loops than if I was writing the code myself.
I'm sure that with the right discipline, it's possible to tame the LLM, but I've not been able to reach that stage yet.
- I just don't get these comments about syntax...
Just taking the first example I can find of some auto-formatted OCaml code
https://github.com/janestreet/core/blob/master/command/src/c...
It doesn't look more a soup of words than any other language. Not sure what's hard to parse for humans.
- I personally find OCaml more pragmatic than Haskell.
Haskell has a steeper learning curve IMHO: monads are pervasive and are hard to understand, laziness isn't a common programming pattern and it adds complexity. I find type classes confusing as well, it's not always clear where things are defined.
I like that OCaml is close to the hardware, there are no complex abstractions. The module system makes it easy to program in the large (I love mli). If you avoid the more advanced features, it's a super simple language.
https://en.wikipedia.org/wiki/Proletariat