5 ms·
A developer job? It sounds like support/sysadmin. A pay pal transaction not completing due to a network outage is an ops issue not a dev issue. Also, what's t
by fleitz 15y ago
A developer job? It sounds like support/sysadmin.
A pay pal transaction not completing due to a network outage is an ops issue not a dev issue.
Also, what's the pay? When you talk to actual developers the biggest issue is the problems finding out what the job actually pays. I hate talking to recruiters that won't tell me what it pays. When you don't tell me what it pays that clicking sound you hear is me clicking the back button. It's a job, I go there to get paid, not take shitty pay to hear platitudes about how we're doing what we love.
If I want to take a chunk of my salary to have people go blow smoke up my ass I'd rather see a professional of my choosing.
As far as the gerbil thing is concerned, it's called producer/consumer. You use a message queue (SQS?) to store the work and you use the gerbils to 'consume' it. You store the state of the books in something called a "database" and you store the "master book" encrypted publicly on a CDN. The server puts a message in the queue telling the gerbil how to customize the book along with the URL for the master and the key to decrypt it. For pragmatic programmers they sure go out of there way to obscure that it's a simple producer / consumer model using SVN and a bunch of caches as a message queue / database monstrosity.
As for the coderay thing I'd rather just use the F# syntax parser from F# and decorate the AST as F# is my favorite language and it would take a couple hours to do it that way. As a pragmatic programmer I don't much care to implement a half assed parser in another language.
- deleted 15y ago[deleted]
- phillmv 15y ago>A developer job? It sounds like support/sysadmin. "Devops" is the way to go these days. Surely they must exist, but I've yet to encounter a <30 person company with a fulltime sysadmin. It's usually "Joe" or "Rackspace". Yes, this is often suboptimal, for sysadmining is hard. > It's a job, I go there to get paid, not take shitty pay to hear platitudes about how we're doing what we love. Dude, it's a job opening at PRAGPROG. If that doesn't immediately tickle your fancy, this may not be the job for you. Admittedly, it probably isn't the job for me either.
- count 15y ago'Devops' is nice, but I'd be you end up getting shitty SA work and shitty code rolled into one package, instead of great versions of either...
- deleted 15y ago[deleted]
- deleted 15y ago[deleted]
- donw 15y agoTook a very quick look at Coderay. If I'm not mistaken, it looks like a Regexp-based parser/compiler, rather than any sort of parser with an actual grammar. To be honest, while my inner nerd shudders at this, it makes a little sense as some of the languages in that list (Ruby) have only recently had formal grammars defined. That said, I think it would take me more than ten minutes to implement a scanner for F#, which I don't know, using Coderay, which I also don't know. I could probably get it done in about a day, maybe two for debugging and testing. There is no way in hell I would spend that kind of time on a job application, and as a nerd that has gone into management, I wouldn't ask an applicant to do so either. What has worked well for me in the past is to ask for either a link to their GitHub repository, a code sample, or have them solve a quick five-minute problem over Skype or IM. If the interviewee passes that bar, we then do something more in-depth during the interview as a pair, timeboxed to about half an hour. This has proven effective at weeding out the untalented and unworkable, without asking potential hires to sacrifice a huge amount of their time.
- tptacek 15y agoRuby does't have a grammar? MRI Ruby, the oldest and creakiest of its implementations, is parsed with a 6000 line Yacc grammar.
- donw 15y agoIf I remember correctly, Matz didn't approve a formal grammar for the language until a few years ago, with the idea that any language that can run rubyspec is Ruby. E.g., the language was defined not by a formal specification, but by implementation. Then again, my memory is known for being incredibly unreliable; I could be wrong on this one.