If you worked on something serious, it used an RDBMS or some other better-than-csv database for data storage and retrieval. Don't discount your database skills. Look for jobs requiring experience on that flavor of database, and talk up your skills.
I come from a Sybase SQL Anywhere shop. It never ceases to amaze me how stuff that can be elegantly expressed in a couple of queries in Watcom-SQL typically takes four times as much code in MySQL's dialect. I love Sybase's support for the ANSI standards, subqueries, Java/.NET/C/PHP/Perl stored procedures when they are the right tool for the job (ever needed to resize raster images in an INSERT trigger coming from some third-party application?), and great drivers. I shouldn't have to spend 10 minutes trying to figure out why MySQL doesn't support the standard casting string concatenation operator by default (||), or why subqueries don't work like they ought, etc.
Having used Postgres, all of the worthwhile MySQL features are there, most of the SQLA features are there, and the pain level is much, much lower in Postgres than MySQL for someone coming from a full-featured commercial RDBMS.
What really sucks is all of the applications that are so coded around MySQLisms that they don't run on ANSI-compliant engines.
I don't think Facebook is competent to decide whether or not a church's refusal to recognize the legitimacy of homosexual couples is hate speech, or whether or not the state of Israel is a terrorist organization, etc.
I'd rather them stick to standards that are not so subject to interpretation, like no depictions of one person's genitalia in contact with another person where either person is not of the age of majority. Let the nation states decide what those ages of majority are. Those sorts of standards are much less subject to interpretation.
-fr of course.
My first programming language (5 years old, 1985) was Apple BASIC. Online interpreter:
When I was in 3rd grade, we programmed in LogoWriter. Looks like there is a web-based LOGO interpreter here:
Next, I learned PASCAL.
None of that stuff is OOP (although imperative is still a very important paradigm).
Once you want to move past kiddie stuff, I'd set her down with a C# IDE (the free-as-in-beer Visual Studio edition or the free-as-in-really-free MonoDevelop) and some YouTube tutorials.
Andi Graph is the bomb... you can switch between any TI-8x ROMs. The only thing I miss about it is the tactile keys.
I own a TI-85. Therefore, I have no remorse about using the TI-85 ROM on my Android devices, as I'm not letting anyone use my calculator at the same time. I paid for the software.
In conjunction with BlueStacks on my Samsung ATIV Pro 900T, I can even project and take screenshots of the whole calculator without any special TI hardware.
I'm a parent of four precocious kids in a small college town in the mountains of NC.
We have taxpayer-funded public transportation here. 12 years old and up are allowed to ride the bus alone (to go to the library, etc). Would I let my 7-year old if he were allowed? No. Would I let him go with his 12-year-old brother who has a way to stay in touch with me? Probably.
I don't think the issue here is automotive safety. A fully-automated car should be safe enough for kids to ride in by themselves, or it shouldn't be on the road. I think the bigger concern is, when is it okay to let your kids out in public without supervision? 72% of the people who said flat out "no" did so because they have the impression that parents should be attached to their children at the hip, or because there was no option for, say, 15 and up. Maybe kids should be able to earn the freedom of being out without their parents with good grades above a certain age, etc. The survey sucked. There should have been an option for unlicensed adolescents but not younger children, etc. Parental consent and discretion should be part of the equation as well. We're the ones responsible for our kids, and with that responsibility should come some discretion on our part.
On a side note, I think autonomous cars will reduce the need for us to go out for non-social things. I mean, aside from losing the ability to pick the best produce, I certainly wouldn't mind telling my car to make a run to the grocery store for me. For me, shopping is just time I'd rather spend with my family.
Most of the non-OpenSSL instances of TLS implementations out there are probably SChannel.
I would be shocked if Microsoft hadn't had equally severe bugs, and further surprised if they could fix them as fast.
POS Ready 2009 *is* Windows XP SP3 with a cheaper license ($99).
If you can get your hands on it, it's supported until 2019. Since end of support is 2019, they should still be providing security updates...
They may be killing XP, but not it's lesser known twin.
Put bar code labels on everything with the asset identifiers.
Make a simple web app that authenticates to the LDAP server (you don't even have to write the auth part - Apache will handle that for you). The app will have two basic functions: start using asset and stop using asset.
They will touch one function or the other and enter the asset ID to generate a log entry.
Write an iOS native wrapper app for it using UIWebView and ZBar, to let them scan the asset tag using the camera on their phone.
Leave a $170 iPod touch in the lab for anyone who doesn't have an iPhone, so they don't feel left out.
If desired, automate sending nag messages to people who forgot to log stopping the use of something. Give them a way to enter corrections with a web form.
Provide your bean counters with a suitable report, preferably something that exports to their favorite bean counting app's format (I'd probably use the free Crystal Java Runtime just because I know it).
It can be made generic enough to get app store approval.
Cost to implement: 2 weeks of my time - negotiable.
There is an upside to logging stuff like this besides satisfying the beanies... you also have data to justify new purchase requests.
This is a parroting of a marketing-derived press release. Move along. I think I'm going to move along. Thanks for the memories, Slashdot.
You do realize, in the post-Snowden era, that the NSA probably already forwarded your Slashdot submission along with your social security number and those of your 8 closest relatives to the RIAA, dont you?
That's about the silliest thing I've heard today. A television screen, even in 1984, was probably a computer monitor. Granted it was NTSC, but around that time most televisions were switched over to digital tuners (which are computers).
I mean, I'm a computer programmer, and I spend my day working in Visual Studio, vim, and NetBeans (depending on what I'm doing). By that logic, I never see a computer either, at least not the one I'm working on. I spend most of my day in an RDP session on a retired tradeshow 27" iMac. I have to touch xcode once in a while, but I mostly keep it for the real estate.