My job title has changed 5x more than my actual job. I honestly don’t even know what my current title is.
I wonder how many man-hours (and at what average salary) has been spent deciding on title changes that have literally zero impact at my company. I’m sure every change involves meetings full of highly-paid executives.
“I (want to keep my job and therefore I) AGREE WITH YOU 100%”
They collect the big bucks, the rest of us can suck dirt - barely not able to afford a home, food, medical care, etc. Oh wait, sorry, I meant “YES SIR/MAM!”
“Look at you, hacker: a pathetic creature of meat and bone, panting and sweating as you run through my corridors. How can you challenge a perfect, immortal machine?” -Shodan
Yeah, you can technically write object oriented code in C. Or any other language. Just that actual OOP languages provide a nicer syntax and compile time checks.
Rust is kind of a good example of this. It’s technically not an object oriented language, but the trait system brings it close.
Yeah, same in the UK. Really annoyed me that the plumber, electrician… etc were all engineers. In Germany it’s as protected as calling yourself doctor, which ultimately affects how people view the profession and the salaries they command
I mean, it’s a protected term in Canada too but it doesn’t necessarily lead to higher salaries.
My cousin who’s an electrician made about as much as I did as an electrical engineer, and I left electrical engineering to be a software developer because it paid more. Engineering paid more than being an electrical technician / designer, but not by a huge amount.
I left aeronautical engineering to become a software “engineer” for similar reasons, salary and work culture. Actual engineering pays quite terribly in the UK, it’s a fair bit better in Germany or the US from what I hear.
Yeah it’s difficult for me to name my title in English 'cause the word doesn’t exist. I went to a technical high school, not university. (Not college!)
It does not only dictate your professional life/status in Germany, being a doctor, your social as well. Someone I know got a postdoc in germany, no luck finding a place to live until they started asking their german collegues to call and saying “doctor so-and-so is looking for an appartment”. So, he gets one. The guy has a very long full name, so the nametag the landlord is gonna put on the postbox is way to long, but if you cut off the part where it says he is a doctor, it would fit. He insists to cut that part away, the landlord just refuses, says fuck your name and person basically, and cuts off part of his last name instead. Saying you are a doctor gets you first in fucking everything (maybe not lufthansa, then they just say ‘senators’ or something). Extremely class divided social society that.
Hmmm. But all the people around me working in software studied multiple years in an Engineering field. In my case, I studied a 5-year industrial engineering and two masters afterwards; I feel very comfortable wearing the “software engineer” or more accurately “robotics engineer” badge.
No, that’s precisely the opposite of my point. If you drive an Uber, you’re an Uber driver. People are “CEO” or “Judge” despite nobody having a CEO or Judge degree. Your profession is what you do, not what you happened to study in your teens to get there.
I understand your point now and I agree. Your colleagues that studied engineering became programmers. Why do people treat this as if that’s bad? It’s a beautiful profession.
I don’t think it’s bad, in fact I wonder the same. These are my colleagues because it’s the same path I took - I now work developing self-driving cars (I slowly transitioned from aerospace to manufacturing automation to robotics) and it’s the most rewarding job I’ve ever had, and it feels very much like engineering. I don’t care if I’m not a “manufacturing engineer” anymore; I really like my job and I like my title to reflect somewhat accurately what I do, but that’s the extent I care about it.
How come they don’t count? They’re figuring out how the machines should work, for money. That’s engineering, right? (I’m an American mechanical engineer)
In Canada you have to be qualified and licensed to call yourself an engineer. There are people who can use the title “software engineer”, but it’s not the majority of people working in development.
Softwareingenieur darf man sich nennen, wenn man ein mathematisch-naturwissenschaftliches Fach studiert hat, wo Informatik dazugehört. Somit ist Software Engineer oder Softwareingenieur die korrekte Berufsbezeichnung für alle mit einem Bachelor/Master oder höher in Informatik.
That is not entirely true. It’s a bit more complicated. Yes it is protected since the 1970s but it’s more of an academic title. You needed to study something that is “mainly” of technological or scientific nature. Basically befire the Bologna reform every student in Tec. Unis/FHs did get the title Diplom-Ingenieur. So the engineer part was literally part of your degree. This of course also true in case you studied IT. So yes there are many who call themselves IT engineers also in Germany. However it’s more of a philosophical question how much software development is actually engineering or rather craftsmanship.
This is dangerous. The object might not have the crack() method, and this bloats the compiled size by a lot if you use it with different types. There's also no reason I can see to use concepts here. The saner way would probably be to use inheritance and objects to mimic Java interfaces.
Rust isn’t really OOP like C#, Java or C++ - it has structs with functions that you could consider an “object” but there is no inheritance. Instead Rust uses traits which are a little bit like interfaces in some languages.
The way the kernel is using Rust at the moment is to produce safe bindings for modules to be written in Rust, i.e. you can create a module in Rust source which will be correctly loaded up, the code is safe by default and will have access to kernel services via bindings. I expect over time that more of the kernel will become Rust, but the biggest impediment right now is Rust relies on LLVM and LLVM only supports a subset of targets that a kernel could potentially support with another compiler like gcc.
Having a thorough process and an engineer approach in software development is also pretty handy. There weren’t many bugs in the AGC. Yet it was programmed mostly in assembly and people had no trouble trusting it with their life.
No, actually C#'s answer should be: “What Java said - hold on, what Python said sounds good too, and C++'s stuff is pretty cool too - let’s go with all of the above.”
C#, or as I like to call it “the Borg of programming languages”.
I got my first software developer role last year and it was the first time I’d written C#, I was more TypeScript. Now we use both but I must say I really like C# now that I’m used to it.
I think most programmers would like C# if they spent time with it. It is getting a bit complex because the joke about it over borrowing from other languages is on the money. It is a nice language though and pretty damn fast these days all things considered.
There’s too much MS in the language and runtime for me. The fact that it gives my Linux programs DLL files and the fact that by default the SDK phones home makes me run away in horror from not only writing it but also running other projects written in it.
The biggest selling point about functional languages for me is the type system, mainly algebraic/union types (which imo Scala does the best), pattern matching (and imo Rust does this best), and the incredible type inference, but also all the functional features. But I think the best part about F# specifically comparing it to C# is the removal of a shit ton of the boilerplate. Plus data is immutable by default, always a nice touch.
For F#, the special types may not be super relevant when interacting with C# libraries, but in general you can do everything in F# that you can do in C#, including all the OOP. It’s just an added bonus that you basically get enums on steroids and pattern matching.
I find that writing in F#, even if I write basically the same code I would in C#, speeds up my design/programming a TON and makes it significantly more maintainable and easy to navigate. There’s a lot less clutter and you don’t have to worry about the layers upon layers of repetitive boilerplate.
The only downside IMO is that F# can have some terrible error messages. And of course, you have to learn F# syntax which can be a small pain if you’ve never used ML or Haskell (especially when it comes to function call syntax). But if you’re mainly interfacing with C# libraries then it’s no big deal. I started making an application only utilising C# libraries (mainly DB stuff) the same day I started using F# and it went relatively smoothly, although probably because Rust is the main language I used then.
This resource might help, although I can’t say it’s enough to completely learn the language: fsharp.org/learn/
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.