148 karma · joined July 11, 2010
Seeking an internship or entry-level position. I speak PHP and Python.
I've been a computer enthusiast since 1987; on the internet since 1994; creating and hosting websites since 1997; with my own dedicated servers since 2004. I've been programming in PHP since 2004 (not full-time) and Python since spring 2009. I'm competent in HTML and CSS; I do alright in Photoshop.
I interned in 2009 with the US Forest Service, writing a Python front end to a framework also written in Python; and worked on a couple of web applets in PHP (with JS that I did modify a little) that displayed smoke and weather data.
I have previous technical experience - helpdesk, web design, some programming. I'm working towards getting my Bachelor's in Computer Science, but it's slow going.
Seattle is a bonus, but not a huge deal.
So just be careful if you try it out.
I'm a recovering Minecraftoholic.
I still definitely change lanes more than most drivers around here - although I do my best not to cut anyone off, and I actually let drivers in here... something definitely not done often in Dallas.
It also helps that I went from a 90 minute commute (each way) to usually a 10-15 minute commute here (depending on where I've worked). Smaller towns do have some benefits...
I looked in the forum to try and see if I could figure out how to maybe add it myself - but I see a whole lot of posts looking for help with no answers - and I didn't find anything that helps me figure out how to get started maybe adding this functionality.
I poked around in the various files included with the program, and I don't see where the definitions are... Meh.
It's a pity - this looks fantastic, but it won't work for me.
I've seen this [appear to] work in Seattle. While I was there, I tried it, and it appeared to work.
However, while I lived in Dallas, I was aware of this idea, and tried it there - and no way. People cut in, people tailgated - it completely doesn't work.
So I think it partially depends on the nature of the city's drivers. And there is something special about Seattle.
>1. A fixed commenting period for each post of 24 hours. Permanent link to this item in the archive.
>2. Until the period expires, none of the comments would be visible to other commenters. Permanent link to this item in the archive.
Seems pretty clear to me that for 24-hour period following a post, comments can be made, but are invisible. After 24 hours, comments are made visible, but can no longer be made.
#5 on the blog makes this more clear - #1-#5 really explain this concept.
As an aside, I hate the idea. :shrug:
If I choose HTML as the document type, I can style some PHP elements - but CSS in particular is just standard foreground-on-background...
Otherwise, this looks like a replacement for PSPad, which is my current choice.
Well... by that measure, any statement regarding the future is a prediction.
"I'll see you tomorrow!" - but maybe an asteroid will hit overnight....
Live in South Korea, die of fan death?
But on topic: I think the thing that infuriates me the most is when a support person clearly doesn't read what I write to them. I can't count the number of times I've had to reply and say, "Listen, I know you have canned text to make your job go quicker, because most people haven't researched their own problem before coming to you, but if you'd read what I actually wrote, you'd realize why your response was completely unhelpful."
That's usually followed up by another batch of canned text. ARGH.
TypeKit tracks how big the font files are. Each font might only be ~20-30K - but that's one weight/style. If you use multiple weights and styles, that's 20-30K per each. It's easy to rack up 3-4 weights, and of course I want italics on some of those == 4 weights times 2 italics times 3 fonts = 20-30k times 24 and now we're talking half a meg or so...
If I'm demoing 18 fonts on a page, even at a single weight and style - that's approaching half a meg right there.
I think using an image is the right call.
But if you want to see TypeKit in action (I get no benefit from pushing them - I'm just a satisfied user), here's a couple of sites I'm using it on:
What really annoys me about it is that they don't limit the characters in the text box - you can happily paste a novel in there if you want. Just when you go to post, an error that you're over the limit (at least they do say by how much).
It's clear that they use JS on the box (if you don't wait for the page to load, the box won't auto-expand as you type) - why they don't implement a simple script to stop typing beyond the limit is beyond me...
I love being able to defer emails until a specific time. I use it for the smallest things - deferring "poke" messages on Facebook to slow down the poke war - to any email I need to remember later, but don't have everything I need at present.
So, sorry this isn't specific feedback at this time, but hopefully it'll still help. ;-)
When I open a story, it seems to skip to the comments - I have to scroll back up to read the story (Firefox 3.5).
I'm only asking because ten seconds is actually quite a long time at an intersection, and it fascinates me that such a concession to bike safety would be made - and work.
Search bar is supported in about:config, but the others aren't.
So far, the beta looks good to me. But I'm dying without the rest of my extensions.
So, blow through about $4.3 million in money from your scam, pay back $10k, and oh, they can't scam people using the scam they used that was already illegal.
I'm seriously in the wrong business, with the wrong ethics.
That being said, I think this is a good attempt to encapsulate HTML5 into a short statement (which should, as others have pointed out, really be broken up into multiple paragraphs). I'm not so sure it is a good encapsulation; but certainly a good attempt.
There are several companies I disable: Winamp, for a while, was updating WAY too often; I used to have trouble with Quicktime - but, in my humble opinion, that software is just... ugh. bloatware and badly written. Thank goodness we've moved on from it as a standard... Adobe's updater is another one I turn off - I really dislike the companies that add a "quickstart" app to my startup - I don't need update checkers from ten different companies stealing my resources....
But there are some smaller names that I do think get it right: Filezilla - even though they tend to update more than I'd like, the update process works pretty well and doesn't take too long; uTorrent is another, as well as VLC does okay...
I definitely think that different classes of users will have different experiences. For Gramma and Grampa, autoupdating is generally better, because they never will. For us geeks: well, we can turn it off for companies that don't do it right; and we talk about our experiences - companies develop reputations...
The way I configured it, it checks for updates to addons every few hours, and if it finds one, installs it silently. The next time Firefox starts, it's ready to go - basically, it does the same thing as a manual check, install updates, but instead of clicking the "Restart Firefox" button, just leaves me alone.
I hope that's basically how they do it... it really would be background - except for those that don't restart Firefox every week or so... but at least for me, addon memory leaks still cause me to restart Firefox every other day or so (I have -- oh, this is great! I just counted - I have 42 extensions installed. hehe)
It was grainy, but not only was the speech intelligible, the music wasn't overly painful (i.e. it was grainy, but only a bit more than a bad record).
I printed out but subsequently lost, and haven't been able to find anywhere - there was an article about Kraft cheese inserted into a floppy drive. It was meant as a joke, and wasn't public... but I wish I hadn't lost it. (IIRC, the basic advice was "don't do this"...)
I'm not tooting my own horn in saying I didn't participate - I'm no noble man, but one thing I will not do is cheat in college. I was, however, very disappointed to learn that apparently such cheating is rampant.