[lordnacho]

My 2 cents:

- The security job is more hardcore. It's a branch of software that you probably will find hard to learn about on your own, with lots of little juicy details. Airline software, I'll bet most devs could figure out how to write if they understood the domain, and there are probably fewer pitfalls. But I'm no expert on either.

- Your subjective experience will depend a lot on the individual people you meet and work with. You don't have much other than gut feeling on that.

- Tech, I wouldn't worry. There's always going to be a whole bunch floating around. Once you get in the zone, you can pick up a new language/framework quite quickly.

- Don't worry too much about your decision. It seems hard to choose, but that probably means the outlook is similar for the two. Otherwise it wouldn't seem hard.

[mattmanser]

Oh come on, he's be using javascript and kendo UI to make graphs. That's not hardcore security programming.

That's the very antithesis of hardcore programming. Apart from tearing your hair out at the shitty kendo API designs.

The security job sounds like a boring job to me from his description, sounds like they'd be using him to animate a bunch of graphs on their website or something.

OP, there's almost nothing worse in programming than making graphs.

[GFischer]

"there's almost nothing worse in programming than making graphs."

Reports? I was offered a significant pay raise to work exclusively on reports. I declined.

[greg_data]

Graphs are fun, CHARTS are boring.

[mattmanser]

Haha, that's a more accurate assessment!

OP, it's so hard to know what a job is like from a tiny second hand description, so don't take my words too literally, it might be fine and more involved, but as someone else said in the thread:

there is a possibility of getting a bit more into

Is code for:

we're going to dangle this thing in front of you for a year or two and then conveniently forget we ever said it