We're saving that for when the junior senator from Minnesota does something exceptionally stupid.
I managed to flood it with enough data that it locked up, and required a manual reset. The second and third time that I did it, the network admins were getting much faster about fixing it, but my boss told me to stop doing it.
I have no idea how much it cost
I didn't get fired, as I was testing to ensure that we had sufficient bandwidth for SDO data transfers. (we didn't
You're assuming that they're not effectively leasing in the first place.
My town is small enough (300 homes) that most of the lights are managed by the local power company (PEPCO). We pay them a fixed amount per month, plus the energy cost. When something goes wrong with one of the lights, we report it to them, and they fix it. (citizens can also report them, but it's a royal PITA, as you have to give them both the pole number (which means you have to get out of your car, and walk up to the pole, and try to read it in the dark), and the type of fixture (which of course, we're all experts on, and why the hell don't they have a database of what fixture is on what pole?))
Back when I was a town commissioner, we were trying to get the lights replaced w/ LEDs, but PEPCO insisted that they didn't have enough data to figure out what the replacement lifetime would be, and so they couldn't determine their cost and thus couldn't offer them to us.
So instead, we had to pay to get all of the lamps replaced with high-pressure sodium, when they stopped offering whatever the lights were that we used to have. (oh
I tried reading the article, but either it's blocked, or the site's being overwhelmed right now. (I apologize, but I actually try to confirm things before I rant about them
If the proposal is what I think it is, it's no different than people passing around images filled with text to get past the twitter character limit.
People in the accessibility community realized the problem a year ago, but it wasn't until last week that I saw other coverage of the problem.
The solution for the blind is to come up with a way to encode the metadata into the image
A couple of years back, I was trying to hire someone
The problem with age isn't so much that you have less portable skills, it's that you have a less portable life -- if you have a sponse & kids, you don't want to move the kids in the middle of a school year and away from their friends
If you're single with no kids
(I have no affiliation with booking.com, other than they were a sponsor for many years of the DC-Baltimore Perl Workshop, which I help to organize)
It's not just you -- the article had a quote that makes it seems like there's an unknown sysadmin care bear:
Culturally, we have to make this shift from a mistaken belief that all our data has to be near us and somewhere where I can do and hug the server, instead of someplace where I don't know in the cloud. This is a big shift for many within the department. It's not going to be an easy transition.
I don't know about you, but we don't have our racks just standing their on their own
Any vehicle with airbags in it has a data recorder so that the manufacturer can determine under what conditions the air bag did or didn't go off.
So even if you don't have a dash cam, if you're in an accident, get the data from the other vehicle. Depending on the make & model, you might need to make sure that the vehicle doesn't get driven before the data's been read out.
I was once driving home on Thanksgiving day a few years ago -- taking I66 to the DC Beltway. It wasn't rush hour, so I waited until the sign came up that marked that it was now an exit lane (the shoulder is an extra lane during rush hour). It seems that there was some guy *flying* down the lane
Once we got to the exit (which had two lanes), he shot around me, then pulled into my lane and slammed on his brakes. When I stopped without hitting him, he gunned his engine, we both got back up to speed
I kinda wished that I *had* hit him, as I could've proved that it was his fault for wreckless driving. (although a dash cam would've have hurt -- show that he had no reason for braking, as the road was clear, and that he had intentionally gotten in front of me to try to cause an accident).
You can be a programmer and write documentation, but if you want good documentation, the person writing it shouldn't be the same person who wrote the code.
The problem is that you're already too far in -- you understand the design issues, the quirks, etc. You need someone with a fresh view to write the documentation who doesn't come in with a lot of implicit knowledge of the inner workings of the software.
My boss has a policy that it's the newest or youngest person on the project's job to write the documentation, for that very reason. (the others still review it, but they write the first draft).
Of course, if you go back to the very early days, Fark didn't have the 'boobies' and 'wieners' topics -- those didn't happen until after they got mentioned in Playboy. (in 2000? 2001?)
(disclaimer : I used to work for Drew, and was the one who added the original topics, back when they all had strong 'S' sounds (and I still thing that 'wierd' and 'cool' weren't needed because of 'strange' and 'spiffy'))
Could this be an emerging Earth Sciences turf war between NOAA and NASA? Lately it seems more of a National Atmospheric Space Administration. Mission creep, much?
Nope, it's fully in compliance with the 2013 OMB memo on an Open Data policy. The subheading on that memo is 'Managing Information as an Asset', and there is a real lack of a comprehensive catalog of NASA's data. (note that this is *not* the same as the 2013 OSTP memo on public access to federally funded data, but they're related.)
Even with the re-design of data.nasa.gov, the content behind is is woefully incomplete. When I contacted the creator of the page years ago, he said that they just did some internet searches to find 'data', and then listed them. They were listing websites that mentioned data, not even breaking it down into missions & investigations.
Someone needs to go through and determine for every investigation from every project what data *should* be there, and figure out if it's online, if it's in a dark archive, if the PI still has it, or if it's missing. They should catalog it according to GEMS and possible DataCite (although assignment of 'creator' for the data might be something that needs to be resolved by each science community)
I had tried proposing something to the NASA IT Labs call shortly after the memo came out, but the people running it were blocking our network from being able to submit. I tried again in 2014, and they gave me an alternate way to submit, but they took weeks to get the work-around, and by then I was out of town for a meeting.
(disclaimer : if it's not obvious, I work at a NASA center)
Back in the 1990s, I was working in Kentucky for an ISP and doing assorted contracting work.
I had a case that was rather similar what you're describing, only ours wasn't run that way because of incompetence -- we were connecting up all of the offices of the Department of Public Advocacy, and for one location the state had decided that rather than get a new line to the DPA offices, as they were in the back of a shopping mall that already had some government offices in it, we'd get fibre pulled between the two offices. Mind you, this was frame relay and fractional T1 days, before DSL, so a new drop was pretty expensive. (I want to say it was around $500/month for just the line charges for a T1, not including the port charges to the ISP tht you were connecting through).
So, when we went there for the install, someone had already pulled the fibre -- I went on the 3 hr drive down there, got soeone to escort me to where I needed to go, and plugged in all of our gear, then went and set things up on the DPA side.
All was fine for a year or so, then we got a call that things were down -- we tried everything that we could over the phone with non-IT folks (it's an office of lawyers), so I was sent on the 6hr round-trip with spare fibre patch cables and such.
A quick check in at the DPA offices showed nothing wrong over there, so I went over the other end of the bulding. I don't remember what the name of the department was, but it was a sort of family services type thing (where people got food stamps, stuff like that). I went up the counter and told the person behind the plexiglass that I was with DPA, and we had equipment in their wiring closet that I needed to get access to.
To which she replied, 'DPA is around the corner'. And I said no, I work for the DPA, and I need to get into your wiring closet. And she kept repeating that DPA was around the corner. I asked for her to get someone else. And I waited 10 minutes or so for someone else to come out front. Once she showed up, I spent a few more minutes with the 'DPA is around the corner' response until I *finally* got through to her and convinced her to let me into their closet. (mind you, this would likely have been considered 'social engineering' if I did it today, as I showed them no ID, being that I had none that said I did work for the DPA).
When I finally got to the closet, I saw that our box had no lights on it
So ~6.5 hrs to fix a problem, because the other office didn't care at all about our gear in their closet, as it would've taken them less than a minute to have moved everthing that was plugged into the known-bad power strip.
So I'd have to say -- no way in hell should you run cable to a private office. If nothing else, that office might close or move, and who knows what might be in there next (or if the new tenents want to remodel it).
Admittedly, it wasn't specifically a CompSci class, but when I took our engineering school's 'Intro to Programming' course, we were paired up for the assignments. The only rule was that I wasn't allowed to pair up with Sebastian, as we were the two who had significant programming experience before we got to college.
When I took Numerical Methods my sophomore year, we were paired up in class, but that was partially because the computer lab we worked from didn't have enough computers for all of us. When it came time for the final, they had to book a second lab so that we'd all have computers to compile on. (which meant those of us in the room w/ newer machines had an advantage over the other room, as our code would compile in 1/2 the time)
But let's face it -- group projects are pretty typical in college. And pairing up for labs is normal too
The goal is get the people to learn the materials -- if done right, the two people learn from each other. Yes, it can be a drag if you get an idiot for a partner
If you have two people making forward progress then it's better than one person struggling along and getting nowhere. Maybe I'm being a bit socialist in my views, but there are sometimes when we need to step away from the 'everyone for themselves' typical American attitude and look at the nordic standards for schooling. You don't want your school to get a reputation for being the one that produced someone who screws up in some major way. My undergrad is in civil engineering -- and if I find out I'm in a building that one of my classmates worked on, I'm going to leave
As the government isn't allowed to spy on citizens without a warrent, under normal circumstances, the satellites aren't supposed to take images when over the U.S.
So the government instead buys images from commercial vendors
I'm thinking that there needs to be a line drawn, otherwise all you end up doing is having a way to make an end-run around the legal verdict -- "we'll just spin off a company that does what we're not allowed to do, and buy the results from them".
Why do people link to blog posts that neglect to link to the original source?
A little digging, and it seems on the surface to have similar restrictions as BackBlaze, as it's only for "for personal, non-commercial purposes".
So I can't store my ~3PB of telescope data on there, or even just the jpeg browse images.
(I might be an old fogey, but I remember when you used to link to a blog post to set context *and* link to the original source in the summary, rather than just some shallow 'I've cherry picked the info'. At least Roland and Coondoggie linked back to their original sources, even if Coondoggies were almost exclusively regurgitation of press releases + a links back to Network World))
I've seen a few talks from Stephen Friend. I was at the Research Data Alliance meeting, and he gave one of the plenary talks the day after Apple unveiled the device, and announced Research Kit (which he's involved with).
He mentioned that less than 24hrs after its release, they already had more Parkinsons patients signed up than any published study on the disease.
If the watch can get *any* sort of medically useful data, I'm all for it, especially as so many people have been designating that their data can be used by any qualified researcher. (yes, there will still have to be IRBs to approve research at most institutions, and I assume some sort of gatekeepers from Sage Bionetworks to determine who gets access to the data).
(disclaimer : I did not watch the video. I usually read the articles before commenting (I know, that's against this site's standards)