Well until you are deep into trait/future/generic territory. Because then you’ll go in big fuck (full type being in a separate file) not being correct somewhere in this shit.
Don’t get me wrong, I love rust. But those area really need some love
Still much better than C++ templates, and I say that as someone who used to genuinely love C++ template metaprogramming. Admittedly Rust traits+generics are far more limited than C++ templates, but very often I find that to be a positive. The list of things that I feel traits+generics are missing is small and rapidly shrinking.
Well, it is theoretically possible for code to cause a compiler to segfault. As for how, well that's a different matter. You'll need deep knowledge of the compiler, or else the assuredness that it can't possibly happen. Because then it will.
Oh God the horrors. The only part of these errors I ever remembered was “basic_string” everything else was the syntactic gibberish you wonderfully demonstrated.
Always remember, the silicon valley ethos of “break things” wasn’t about their applications, it was about breaking industry, society, laws and your ability to oversee or regulate them.
Apparently I’m Neutral Evil. But I consider myself to be Chaotic Neutral.
I’ll fix the problem only when it’s actually a computer problem and when you can explain what the problem properly. I don’t care if it’s a ticket or an email. Though I might not get to the email today and tomorrow I might forget about it, so you might want to put a ticket in that’ll stay the until it’s closed. But the ticket system sucks, so I might not log into it and see your ticket for a few days. If you send an email, I might do it right away, but you might have to remind me about it in a few days because I might’ve forgotten about it.
I don’t care about your job title. If you VP of whatever the fuck and think you’re important or if you were hired yesterday to an entry level position, you’re all users to me. But the issues aren’t fixed based on the order they come in, it’s based on how much effort you put into describing the problem. If you think you’re too important to describe the issue properly, you’re low priority. If you want a meeting to describe the issue verbally, oh you better believe you’re low priority, I’m not your fucking secretary that’s going to take down your dictation. You got a keyboard in front of you, use it. I might eventually get around to asking you for more details about the problem, but only after I’ve fixed all of the problems reported by people that made an effort. Your priority is based on your effort.
Ok so maybe I’m Lawful Evil? But everyone thinks I’m Chaotic Evil because they don’t understand why some people get stuff done right away while they have to wait.
My last job offered free beer after 4pm on fridays.
It was smart as fuck if you think about it. For the small price of a few crates of beer, you got 20+ people talking in their free time, and on the weekend, without additional pay. It was officially off-work but since most of your coworkers were there, there was a lot of work-related exchange going on.
That’s what makes us humans different from computers. We don’t ask how high, we just do it. Now, if it were a C pointer it would jump anywhere from 0 to 2^32-1. That’s why C is more suited for artificial intelligence than it might initially seem. Thanks for coming to my tedx talk
Afaik rust doesn’t have functions like that as they lead to unsafe code that’s impossible to check variable lifetimes for. I think OP created the jump function.
Worked the first six years of my career using no version history tracking or backups at all on one of our main systems. Nobody knew we didn’t have backups and I didn’t know how to use git and figured it wasn’t so important since I was maintaining it alone anyway.
programmer_humor
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.