249 reputation
13
bio website erikengbrecht.blogspot.com
location United States
age
visits member for 3 years, 9 months
seen Dec 26 '13 at 16:23

May
8
awarded  Nice Answer
Dec
31
awarded  Yearling
Jan
22
comment Introducing Scala to a Technical Manager
I would be careful with DSLs. Some people have very negative reactions to them. I also wouldn't bring up XML. On one hand I've written some Scala XML code that was simple and elegant that I think would have been an ugly mess in Java. On the other Scala's XML library can be a wellspring of WTF moments, so I'd be conservative and not bring it up.
Jan
22
comment Introducing Scala to a Technical Manager
Well, last time I tried it I was maybe two notches above ad-hoc scripting, and it exploded. I think it was a character encoding issue or something like that (I was on Windows). Or maybe it was line endings (again, good ole Windows). I don't know. All I had to go on was a stack trace that didn't point at an obvious answer and I was on company time so I couldn't spend time debugging it. Java's IO libraries just worked, even if were ugly in their imperativeness.
Jan
22
comment Introducing Scala to a Technical Manager
Every time I've tried io.Source I have regretted it. Use cases like what you show are oh-so-tempting, but it's Source is oh-so-buggy so it's not worth it. Just my opinion.
Jan
20
comment What does the suffix after software engineer/developer job titles mean? (e.g. Software Developer III)
I think there's a standard somewhere. I know our HR department subscribes to a database the consolidates salary info. Normalized titles make it easy to look up "a person with this title in this region with this education and experience should get paid this amount." Never mind the extreme inconsistency within the company, much less among companies.
Jan
20
answered What does the suffix after software engineer/developer job titles mean? (e.g. Software Developer III)
Jan
1
awarded  Teacher
Dec
31
awarded  Supporter