i'm sure this is a very useful product, and i understand that "addict" contains the letters "AD", but naming something "addict" while half the US drowns in opioids seems a little weird
I suspect the down votes are because the word has already been co-opted for years to describe things that aren't issues. Similar for "viral", "infectious", "jonesing", "getting my cookie fix" and so on.
I'd love to ride my bike to work but don't really have a place to put it during they day; ideally, the building would have a large, relatively secure space with bike racks in the basement or something (which it doesn't; nor do most buildings, as far as I can tell). I doubt my bike would make it more than a couple of weeks with seat and wheels intact if I locked it on the street.
Folders are great. I started commuting with a full-size Dahon that I put under the seat, but now I think it's better to have a small folder and a fixed full-size bike rather than making a trade-off.
This is one of the things that makes a city bike-friendly, making it easy to start riding.
San Francisco: My company has a bike parking room on our floor, and some train stations have five-cent-an-hour bike lockers. (All stations have bike racks, but that's gambling with your bike.)
You can buy locking skewers and other "locking" bike hardware that will prevent people from stealing parts. Combined with a high end U lock and a cable through the wheels it's unlikely anyone would steal it during the day in a populated area.
> It is time for engineers–especially excellent engineers for whom demand is high–to start to flatly refuse to do whiteboard interviews.
This might be a viable strategy for people who have a well-established career/credentials/references (etc), but for junior-level candidates still trying to prove themselves (such as myself) I can't see this working out too well.
That's one of the harder parts of the process, and it's partially because of poor expectations on the part of those doing hiring.
To me, it's absolutely ridiculous to expect to hire a junior developer and have them come with a fully-developed set of skills. If they do, that's great. But if you're hiring someone fresh out of school, you've got to be approaching it as hiring someone that you're going to train and mentor. For me, the number one thing I look for in a junior developer is the ability to learn.
Here's an example from early in my own career. I was just finishing up my 3rd year of a combined CS/EE program, and looking for a summer job. I got in touch with a biology lab that needed a developer for the summer to build some (very cool) software to support the neurophysiology experiments they were doing. I looked at the job requirements and thought "well, I don't know most of this stuff, but I'm sure I could pick it up."
The interview progressed like this:
> Do you know Python?
I'd heard about it, but have no real experience with it. I downloaded it last week and started playing with it though, and it doesn't seem too different than other languages I've used.
> How about VisionEgg (neurophysiology module for Python)?
Well, I downloaded it at the same time I downloaded Python. I've managed to get a window to open up, and I'm displaying a square that's got a cool animated habituation pattern on it. (Note: 1 week prior, I had no idea what a habituation pattern was) I do have a bit of OpenGL experience from a class I took, and that's the underlying library that VisionEgg uses.
> Well, so far, you're the only applicant who has actually made an effort to look at the specific tools we're using here. I've got one other applicant coming this afternoon, but unless they somehow have more experience with these tools than you do, the job is yours.
It turned out to be a great experience, and they hired me back on the following summer. I went from being a total Python noob to contributing patches back into VisionEgg. I think most junior positions should probably progress like that. Give me a keen junior developer, and let me shape and mould them into a not-junior developer.
The flip side to this: if you're expecting the person to be productive on day 1 or 2, you'd better be hiring someone with experience. Whether or not they have code they can show you, they should be more than capable of going into serious detail about past projects they've worked on (within the confines of NDAs and such, of course).
> If he says something now, the reactionary portion of the GOP will take the opposite position as a knee-jerk response. It will become a larger news item and the GOP will have inherited the fallout.
Yeah, exactly. It's a pretty savvy way to drive a wedge through the GOP, and you already see the obstructionist crowd (e.g., Ted Cruz) playing right into it.
Great question for such an important lock-in mechanism. Perhaps a 30-day grace period? No media release so far that I can find references the conditions to keep data beyond the free 5GB Cloud Drive limit.
Yes, but for how long? What if my credit card expires and I forget to update it? Is there a 30 day grace period for downloading them or are they wiped immediately?
Kenny Goldsmith [0], the guy who teaches this class, has done a lot of thinking about internet-based poetics... highly recommend his book "Uncreative Writing"[1] for those interested
Thanks. Led me to this... wonder if they've implemented ES6 yet? :P
> Red Star OS features a modified Mozilla Firefox browser titled Naenara used for browsing the Naenara web portal on the North Korean intranet network known as Kwangmyong. [1]
