unshift
Joined 16 years ago
Joined 16 years ago
my suggestion is to set up yourself a prgmr-like website, do the administration yourself (by hand), and spend a few hundred dollars trying to get some traffic and signups. if that starts to work out then take it from there. realize that more SSDs aren't going to generate any money; signups will.
a new website would be nice, but you don't have the money for one, and it's not clear it's worth trying to get one at this point. the pure ASCII look could actually instill some sort of confidence that your current website does not.
good luck!
a few nit picks: i can't imagine a scenario where i'd want my logger to close stdout (or any other file descriptor) for me.
there is a lot of missing error handling, which is really important for something critical like a logger. what happens when disk space runs out? no timeouts on network operations?
also your SMTP and Gmail loggers don't form valid MIME messages (I can't log non-ascii?). you also seem to just swallow exceptions which is totally not what I would want or expect from a logging library.
keep at it though, the logging module's API (inspired by log4j) is fairly painful.
the API might use hungarian notation, and you might have fallen out of love with it, but so what? it's a pretty decent API and there's no real benefit to users in changing it. they'll all to have to update/rewrite their JS to stay up to date with the library for effectively no reason.
nothing about making software is one size fits all. forcing scrum and pair programming sounds like a really good way to get an enthusiastic team, but guarantees little else.
if i had to come up with a permutation algorithm as part of writing code, you'd better believe i'd look one up so that i'm sure i'm doing things optimally. i wouldn't trust myself to come up with the exactly right algorithm on the first try.
if i had to deal with some weird half-sorted array, i assume i'd be working in the same context as the problem and wouldn't have to make up a solution on the spot with limited details. why do you have a weird-ass data structure like that to begin with? that's the first question i'd ask.
personally i always ask a couple of simple questions (like FizzBuzz) and then talk experience. if you want to see a code sample, ask for one -- written on a computer, without someone hovering over the candidate's shoulder. coding solutions to weird questions on a whiteboard doesn't help anybody.
that tends to be the result of years of people saying "you're lucky to get a job at all" combined with a long search and endless interviews.
and while yes, she did sign the non compete, it doesn't mean it's not bullshit, which is the entire point of the article. of course you can be a hardass and say "she signed it", "should have read it more carefully", "her fault", etc, but now she's on the dole until the clause expires because someone had a hissy fit and threatened to sue her employer. it's a crappy, stifling situation all around which is what the article aimed to point out.
The task is huge and it's unlikely that it will be
completed shortly based only on volunteer work, so we
came up with the following proposal, which splits the
work into several steps and sub-steps, togheter with an
estimate of how much money is needed to complete each
one.