Fork me on GitHub

we had a legal last name in our of systems which was “null”

🔥 3

"Zero of House Null" is going to be the title of my cyberpunk SF novel

Stuart10:06:36 , there whole series on technical interviews is quite good

🤯 5

Aphyr is clever AF. Especially his work on Jepsen fascinates me: (also yay Clojure!)

Drew Verlee16:06:28

Aphyr inspires me.


same link 🙂

Drew Verlee16:06:23

Slack is making it hard to copy the link. I was trying to post the one before.

Drew Verlee16:06:21

> The interviewer—Criss, his badge says—is young, as is customary in the Valley. Wearing a hoodie which, judging from the lack of branding, cost at least three hundred dollars. He resembles no animal in particular, which gives you pause. Usually you're better at that sort of thing.

👕 2
🐒 2
Drew Verlee16:06:17

Oh, here is my favorite bit. > “Are you really unable,” you ask, voice as calm as stone, “to imagine eight powerful women in the same room without them trying to kill each other?”

💯 2

What’s the difference between a Software Engineer and a Software Developer?

Jeff Evans20:06:33

one of those terms is extremely controversial


I'd love to see some engineered software one day 🙂

☝️ 10
🎯 3

Job titles are often impossible to compare across different companies so any “difference” between SE and SD only matter if they are both titles used within a single company. Lots of companies have two sets of job titles: the internal job grade system that HR/payroll use and the “vanity titles” that other departments use.


Where I’ve worked for the last decade, I just retained the same job title I liked from previous companies dating back to 2000 when I joined Macromedia as their “Senior Software Architect”, but my HR-facing job title has been all sorts of things (and, to be honest, I don’t even know what my internal title is these days!).


Titles can be quite useful inside large orgs to figure out who to talk to. Between companies it seems less useful.


I worked at a startup for a while that didn’t really have job titles and so they decided I would be “Chief Software Architect” because they wanted to give me a “C-level” job title for when I was interacting with clients 🙂 Another startup made me “CTO” by virtue of there only being two of us for most of the time and the other guy was “CEO” because he was the founder 😛

👍 3
😅 3

Ah I didn't realize I was talking to a CTO 🙂 🙇


You should have a byline with Clojurians Admin in the title, that carries hefty weight!


After six years as Macromedia’s Senior Software Architect, Adobe acquired us and I was told “we don’t have architects” so you’ll have to use a different job title!” 👀

🤯 3

I did for a while semi randomize my titles when responding to emails, like Archwizard of Computing and Baron of Bytes and things like that


"If you could try turning the program off and then on again, that should solve the problem. Best regards, Emil Aasa, Archwizard of Computing at XXX"


I don't think that was well recieved


Adobe used “Computer Scientist” and “Senior Computer Scientist” for some of its roles (I was the latter, at least internally for HR purposes), and those are pretty absurd job titles. Example on Glassdoor:,31.htm


(I left Adobe back in 2007)

Jeff Evans20:06:11

A certain quote about the relevance of computer science to computers comes to mind…


i guess the underlying question is really: Are We (people who write software/programs/code) Really Engineers?


I know that in some countries, “engineer” is a reserved title and implies some sort of certification and licensing. In the US, though, engineer and developer are pretty much the same.

✔️ 3
☝️ 2

Yeah, in France you need to go to a certified engineering school to get an engineer title. And for a school to be certified, it needs to follow a certain curriculum. I don't quite remember what was in it, but it requires a certain number of hours in math, physics, etc. Regardless of what kind of engineer it is (IIRC) As a result there's quite a few "programming" schools that don't deliver an engineer title, but instead a "Level A" which basically means "yep this guy studied programming for 5 years"


I think Software Engineering as a term got a bit of a bad reputation 20-30 years ago, being associated with a lot of counterproductive things like waterfall development and being required to write extremely detailed design documents before you're allowed to start coding. Agile and XP and Lean came along and showed us that we could work much more effectively, even on big systems, if we threw out some of the formal things that we used to do. But more recently a lot of people, notably Dave Farley (of continuous delivery fame) have argued that we most definitely can take a rigorous engineering approach to writing software, making hypotheses and using real data to test those hypotheses and guide our work. There's a talk that Dave Farley was doing a year or so back that explains this much more eloquently than I could: So for me, perhaps a software developer is someone who doesn't want to be associated with waterfall development and the software crisis, and a software engineer is someone who got over all that.


Or it's just what you put on Linkedin since that's what others that write software put?


☝️ also this (because I also don’t quite fancy writing “archwizard of computerisation” on LinkedIn)

Thomas Moerman17:06:52

I once was allowed to pick my own job title: "lambda wrangler". Needless to say, the amount of linkedin spam kinda disappeared.


Software Engineers get to wear a cooler hat

🚂 5
Robert Mitchell20:06:54

user> (compare "Software Engineer" "Software Developer")

🎯 6