Tweet
That defeats one of the primary purposes of functional programming. Why would you do that? 
-
-
A few of my co-workers (fortunately not my boss) want code to adhere to the functional paradigm just for the sake of having it adhere to the functional paradigm. I have this conversation a couple of times per week:Originally posted by Ben Kenobi View Post
Other Programmer: I'm going to refactor this code to make it more functional
loin: What other benefit would this have?
Other Programmer: None
loin: Okay, then no, don't refactor the code
Other Programming: But it'll make it more functional!
loin: No
Other Programmer: But...
loin: No
Other Programmer: ...
loin: No
We've got better things to do with our time than to rewrite some code just to see how many bugs we can introduce<p style="font-size:1024px">HTML is disabled in signatures
</p>Comment
-
Kuciwalker may or may not have basically done exactly that when he migrated his code to java 8
If there is no sound in space, how come you can hear the lasers?
){ :|:& };:Comment
-
Well, to be fair, all of those bugs were the same two bugs, 1. a syntax error in his first class function declarations, and 2. writing twice to a stream. Which he did like 400 times each.Comment
-
I'm starting to suspect that I'm just not a programmer. I mean, yes, with a little help I can learn to program, but in the same sense that I learned to play Sudoku. I can do it, but I'm not especially good at it, and I can't say it's anything I can summon up the enthusiasm to do for great lengths of time. That just leaves the question of what I do want to do with my life . . .Comment
-
You got a CCNA right? Being a network engineer doesn't really require you to learn how to code much or at all.
But yes, unless you have a bona fide computer science or software engineering degree, you're going to have trouble keeping up with the kind of software development loin is talking about.
Loin, why does your company use Scala in the first place, out of curiosity?Comment
-
That's kind of a mystery, we've got some Scala/Haskell/ML/etc programmers now, but when I joined it was mostly Ruby programmers who all of a sudden decided to rewrite the back end in Scala. (I was a Java/C# programmer whose last use of functional programming was Lisp in grad school, not counting some Linq programming; they switched from Ruby to Scala about four or five months before they hired me, and we've still got a few legacy Ruby services that we're slowly deprecating). I'm assuming it was a matter of the CTO saying "hey, Scala sounds interesting, let's use that"<p style="font-size:1024px">HTML is disabled in signatures </p>Comment
-
Yeah, I got a CCNA, then found out everybody wants that plus tons of other certs, five years of experience and a security clearance. So I've tried to learn other stuff--HTML, CSS, JS--but I have to say, none of it's at all intuitive or interesting for me. Just a long, long slog. I've known people who spent decades doing jobs they hated. I really don't want to be one of those people. I don't think I can be one of those people; programming/networking/computer stuff in general changes too quickly for me to do it while holding a gun to my own head to make myself continue. You learned this stuff in high school (if not earlier), and presumptively liked it. I'm thirty-one years old, it frustrates me to learn it, and once I've mastered it I hate the sight of it.
Right now I'm a sort of office jack-of-all-trades at a misfit company that makes three kinds of small devices. I actually feel some kind of interest in the bits of light assembly work they've started me on. Not sure what kind of money there is in that in the long run, but I'm gonna stick with it for a while and see where it goes. I've only been working there for a week, after all.Comment
-
Ugh. Had a phone/online interview today with a company that's programming in Scala. The developer conducting the interview was a douchebag who asked a bunch of bull**** trick questions.
In Scala there's a "map" function that takes a sequence of stuff, applies some operation to each element of the sequence, and spits out the new sequence with the transformed elements. For example, given
val oldList = List(1, 2, 3)
you'd say
val newList = oldList.map(e => e + 1)
and now newList is (2, 3, 4), i.e. each element of oldList plus 1. As a shorthand, you can say
val newList = oldList.map(_ + 1)
I have never used this shorthand if I thought it might cause any ambiguity at all in my code, so of course I get a bull**** question about what would happen if some idiot introduced ambiguity using the shorthand.
dev: What would happen if you said List(1, 2, 3).map(e => println("Hi"); e + 1)
loin: You'd print "Hi" three times and output List(2, 3, 4)
dev: Okay, how about if you said List(1, 2, 3).map(prinltn("Hi"); _ + 1)
loin: I'd assume you'd get the same thing, but if that were the case then you wouldn't be asking me this question so...
[plugs it in to my Scala interpreter]
loin: Huh. It prints "Hi" once and outputs List(2, 3, 4)
dev: Why?
loin: I have no idea
dev: That's because [some stupid reason I don't give a **** about]
loin: fuuuuuuuuuuuuuuuuuuck
There were four bull**** questions like this ("what would happen if you did this stupid thing?" "I don't know, I've never done that stupid thing and I would berate anybody who did"). Waste of ****ing time.
This is my first interview with a Scala company (I only started sending out resumes on Friday), but if this happens again then I'm just going to write off Scala altogether and focus on Java / C# companies<p style="font-size:1024px">HTML is disabled in signatures </p>Comment
-
Lol. I interviewed at capital one. They asked me a couple of easy programming questions and at that point forward just wanted me to talk about how I basically made almost all of my own design decisions at my last job, they seemed to care a lot more about the fact that based on my classwork and experience that I don't need to be babysat.
I now have an offer from them, so that's cool
That makes two offers so far
If there is no sound in space, how come you can hear the lasers?
){ :|:& };:Comment
-
The company I'm at isn't being managed well and my immediate supervisor is pissed off about it, so I sent out a few resumes as a backup plan in case he quits. If he quits then either a. I get promoted to his job, b. the other senior back office programmer gets promoted to his job, or c. the front office manager also takes over the back office manager role. None of these is a good outcome - I don't want to be a manager, the other senior back office programmer is too nit-picky about stuff that doesn't matter and not assertive enough about stuff that matters, and the front office manager is an *******.<p style="font-size:1024px">HTML is disabled in signatures </p>Comment
-
I still don't understand what your aversion to management is.
I figure it's pretty much the only place to progress a programming career after you hit Senior Developer or whatever.
If there is no sound in space, how come you can hear the lasers?
){ :|:& };:Comment
-
I am a manager, and I liked my previous position more. I like my new salary more, of course, but I'd rather be a tech lead if I could keep my salary.Graffiti in a public toilet
Do not require skill or wit
Among the **** we all are poets
Among the poets we are ****.Comment
-
Fair enough. I haven't exactly ever been a manager, so I don't really know what it's like.If there is no sound in space, how come you can hear the lasers?
){ :|:& };:Comment
-
By the way, Elok, even if someone says they want x years of experience, go apply anyway...the worst they can say is no. I've gotten interviews at plenty of places where I didn't have anywhere near the "required" experience.Originally posted by Elok View PostIf there is no sound in space, how come you can hear the lasers?
){ :|:& };:Comment
Comment