1,092 karma · joined August 2, 2019
Also how were the data races significant if nobody noticed them for a decade ? Were you all just coming to work and being like "jeez I dont know why this keeps happening" until the LLM found them for you?
how do you know that claude isn't just a very fast monkey with a very fast typewriter that throws things at you until one of them is true ?
> All of that social activity with zero ROI.
Pick one
If you just want to use linux so you can tell someone about it, don't bother using linux and stick to what works for you.
depends who's side you are on
If you watch a guide on how to find diamonds it's really just a matter of getting an iron pickaxe, digging to the right depth and strip mining until you find some.
If I need to access the "archive" I use a SATA to USB cable and plug the drive in.
I avoid large capacity drives (my biggest one is about 200GB) and use spacesniffer so I'm forced to keep the data I store lean.
You can take all the salaries of the world and assume you can automate a percentage of that and you will consistently arrive to a big number.
Sorry, what Europe are you talking about ? I don't think that's true.
My advice is just write more code until you make enough mistakes that have consequences that make you understand why it's better to "write less code".
If you consider how people get better at other skills, let's say 3d printing or carpentry; they make a ton of useless stuff for reasons that might only make sense to them - they 3d print figurines of stuff from games or movies they like, they craft things just to test out a new machine or to give them a reason to buy some gear.
Maybe don't look at your self as a "programmer", look at yourself as a "person who knows programming". If you like video games you might develop a tool that helps you generate strategies for that game or if it's an online game you can make a tool that queries some of the APIs of the game so you can run analysis or alerts on what happens in the game.
All in all we are people who write code that serves other people in the end, so being "good enough" is just about finding people that need the level of code you are able to write.
I think 6 months of experience is a very short time to reach conclusions about what does or doesn't work for you, maybe 6 years might be enough.
Try not to develop an emotional attachment to your job, you will end up earning more and learning more if you switch companies every 1-2 years and that's hard if you let your current position define who you are.
Also check out this list[0] and read about some of the biases if you're not aware of them, it helped me to deal with the way I feel about myself and others.
[0] https://en.wikipedia.org/wiki/List_of_cognitive_biases
PS: also when dealing with online learning content try to consciously consider if it actually teaches you something or just makes you feel like you're learning something. The latter is a waste of time in my honest opinion.
Check this summary out though I typed it out with my hands:
- airplane people use radio based on some standards from the 1970s to talk to ground people
- said airplanes fly over a guy's house so he can receive airplane people messages
- guy filters out human readable parts and has a bot that picks few of them that could be funny
- bot posts it online