@Rachel Neat. Yeah in some ways that can be less stressful than working for a software shop where if you don't sell your product then you may lose your job.
... OTOH management tends to look at you like you are a cost on the spreadsheet
lol but they know a whole lot of stuff that I don't know :)
And I think that's part of why I like P.SE so much.... I learned a lot from it, especially it's early days where not everything had a clear-cut answer or was only tangibly related to programmers
To me, SO = solutions to programming problems I'm stuck on P.SE = solutions to furthering my knowledge as a programmer
Wait there is one part of my job I hate.... building custom reports for management >.<
@Rachel Call me a masochist, but I actually like writing custom reports for management. I find it therapeutic to take tables with hundreds of thousands of records, and write SQL that compiles statistics on the data.
I like to think of myself as a Data Prospector, mining for gold.
I just like statistics and making charts of things
Oh it's not that I mind. It's the formatting that drives me crazy... such as "can you have the headers show # of days instead of months", or "can you make this number highlighted in blue if it's over X"
I really hate Crystal Reports and Excel's VBA, which is usually what I end up using for reports. I guess to be fair, it could be a lot worse.
@Rachel Oh yeah... that does suck! I usually just do an Excel pivot table and be done with it. Thankfully our management are all Excel power users which is NICE.
Whenever I need to make something pretty I just give it to an intern lol
Yeah.... I've never had an intern so I wouldn't know the downsides. All I see is the glory of telling them how to do things, and having them do the actual work :)
Only part that really scares me is having to figure out what they're doing when reviewing their code...
@Rachel I advise against it. I love my little guy but it was a mistake. They are wild animals and aren't meant to live in cages. You figure this out fairly quickly.
that being said, I try to give him the most comfortable life possible considering
@MikeL It's close to being closed already, with 4 of the 5 close votes needed. I think the biggest difference between the two questions is that one is asking why a specific programming language was used, while the other question was asking why a specific character was used. We can answer questions about programming languages, but we no experts on the creation of programming languages
(And FYI, I voted to re-open the 2nd one because I found the answers lead to useful information about other languages. It currently has 3 of 5 reopen votes needed)
@Rachel Thanks for the info. I just feel we need to be consistent. I flagged two similar questions recently that both got closed. I see TO edited the Java Android question but I feel it's the same type of question as the semicolon one. "Why something was done this way" although interesting, really is not the purpose of this site.
@MikeL I suppose the biggest difference is the answer the question is looking for. If the answer can be found in an programmer's expected knowledge base (such as why choose one language over another for a specific task based on language specs), then it's on-topic. If the answer isn't found in a programmer's expected knowledge base, or could be better answered by another profession, it's off-topic.
I'm tempted to ask on the UX site, "Should programming languages use semicolons as statement terminators?". But I can't decide if it's constructive or trolling.
user2334
8:01 PM
Save for the accepted answer, I thought the semicolons question was pretty good. Programming history has always been an overlooked aspect of Programmers's scope.
Public restrooms designs usually pay great attention to hand washing, providing facilities like wash basin (sing) - sometimes with touch free, IR operated taps - soap and hand drier or paper towels.
But when leaving the restroom, in too many cases (IMHO over 90% in United Kingdom) the design of...