Re:Code.mil – An experiment in open source at the Department...
by joehan on Friday February 24, 2017 @03:09PM
(#13727359)
Let me add a bit more irony here: github is blocked from my work(USAF) so I can't get to code.mil. All I want to do is be the workaholic that I am and DoD makes it literally impossible for me to do that. You have no idea how much bureaucracy can defeat the spirit of an employee. Most of my friends are leaving the AF for reasons like this. I'll do my best during my time here, but needless to say, I'm out.
[ Parent
| on HN ]
Re:Code.mil – An experiment in open source at the Department...
by jcurbo on Friday February 24, 2017 @05:19PM
(#13728469)
For some reason the AF seems to have draconian web filtering in place, compared to other places I have experience with. In the late 2000's when I was still on active duty, we used to complain about having to look stuff up at home because when you'd go to search for a tech solution and it was on someone's random blog, 9 times out of 10 it'd be blocked. It was extremely frustrating.
Re:Code.mil – An experiment in open source at the Department...
by killjoywashere on Saturday February 25, 2017 @01:01AM
(#13730295)
Fwiw, I'm a Navy physician and have the same problem. Wait until you know, that right now, someone is very sick, and the study you're trying to look up is hosted on a server in some super sketchy non-ally, like Switzerland.
Re:Code.mil – An experiment in open source at the Department...
by panzagl on Friday February 24, 2017 @03:38PM
(#13727661)
The only thing that makes it worth it is that the problem domains are so much more interesting than anything you're likely to run into in industry.
Re:Code.mil – An experiment in open source at the Department...
by engi_nerd on Friday February 24, 2017 @04:24PM
(#13728045)
This is why part of my profile says "reformed rocket scientist". I spent a little under two years working for a NASA contractor on their sounding rocket program. The problems I was paid to solve were relatively un-interesting (find the best ways to fit the experimenter's data requirements into our ancient, antiquated, badly-in-need-of-replacement hardware). The problems the experimenters were solving were actually fascinating, but I didn't get much exposure to their side of things.
Now yes, I am struggling with Information Assurance people and their cantankerousness, but I also have the unique pleasure of being the primary data scientist on this very large project, which is exposing me to new things every day. I just haven't had an environment for learning this rich before.
Re:Code.mil – An experiment in open source at the Department...
by joehan on Friday February 24, 2017 @04:12PM
(#13727942)
You're right, but at some point, I need to draw the line of whether I can actually do the work and be productive instead of fighting the system.