adelevie

9 ms·

1. 1.▲
   by adelevie 10y ago

   I can't give a comprehensive answer as to how we hire, but I can offer my personal experience: I was able to finish my last year of part-time law school when I started at 18F. I was working full time, and everyone was very respectful
2. 2.▲
   by adelevie 11y ago

   18F is hardly the only group within government using OSS to build websites. Also hardly the first (CFPB was at it before 18F existed), I'm sure there are more way before CFPB. According to https://www.govcode.org/repos
3. 3.▲
   by adelevie 11y ago

   > The person is assuming ill-intent on behalf of the speaker. This is where these kinds of issues typically go off the rails. With male-gendered language as the default, I doubt very many people intend to do anything wrong. It's h
4. 4.▲
   by adelevie 11y ago

   Employees who are happy and feel included are going to produce better work (and a better return on the invested tax dollar) than those who aren't. I'd also expect second-order benefits such as helping us recruit from a wider, more
5. 5.▲
   by adelevie 11y ago

   I work at 18F, here's my hot take: It's been pretty well established that needlessly (male) gendered language makes people feel excluded. Actually, that's too nice. That kind of language excludes people. Period. It communicat
6. 6.▲
   by adelevie 11y ago

   https://github.com/18f?utf8=%E2%9C%93&query=fec :)
7. 7.▲
   by adelevie 11y ago

   I should have read the [] manual :)
8. 8.▲
   by adelevie 11y ago

   This is really neat! For work, I've found myself from time to time exploring the tech around PDFs. I find this tech strangely fascinating. It's like a shim on top of something old and ugly that enables integration with much more m
9. 9.▲
   by adelevie 11y ago

   I'd love to see an open source project around scanning the GitHub API and subscribing to alerts for your org's repos.
10. 10.▲
    by adelevie 11y ago

    I like https://fugacio.us/ a lot.
11. 11.▲
    by adelevie 11y ago

    A colleague at 18F built https://www.govcode.org/ . It's a handy directory of U.S. federal government open source projects.
12. 12.▲
    by adelevie 11y ago

    I'd love to see blog posts or any write-ups about your experiences founding an ISP.
13. 13.▲
    by adelevie 11y ago

    No office there, but we have at least one remote staffer in Austin.
14. 14.▲
    by adelevie 12y ago

    > Are the dissenting opinions available? Yes. Keep scrolling :)
15. 15.▲
    by adelevie 12y ago

    I put together some quick and dirty scripts for searching the text of the Order: https://github.com/adelevie/open-internet-order .
16. 16.▲
    if.then.fund(if.then.fund)

    5 points by adelevie 12y ago|0 comments
17. 17.▲
    by adelevie 12y ago

    I'm on a team working on immigration at 18F. Not sure why you assume it's miserable. Anyways, we're using a modern Rails/Postgres/Elasticsearch stack and the work is incredibly rewarding and motivating. Here's
18. 18.▲
    by adelevie 12y ago

    That's a great question. At 18F, we <3 APIs[0][1][2][3][4][5]. Not only are we big believers ourselves, but we strive to help other agencies improve their API practices. [0] https://github.com/18F/api-standards
19. 19.▲
    by adelevie 12y ago

    Is this comparable to IronWorker?
20. 20.▲
    by adelevie 12y ago

    At 18F (a digital services consultancy within the US federal government), we've drafted API Standards[1]. They're a set of recommendations, rebuttable presumptions, and bright line rules that we expect our APIs to adhere to. For a
21. 21.▲
    by adelevie 12y ago

    This is a great example of how privacy is not optional, even in "opt-in" systems such as Instagram and FB. That Instagram does not require you to have a Facebook profile, and Facebook does not require you to list gender means
22. 22.▲
    by adelevie 12y ago

    This reminds me of the wonderfully cool Web 2.0-era startup Dapper.
23. 23.▲
    by adelevie 12y ago

    I sent a pull request with a chapter on diffs[1]. They're important in their own right, but also as a good precursor to the inevitable git/github/version control chapter[2]. [1] ( https://github.com/vzvenyach&#
24. 24.▲
    by adelevie 12y ago

    Check out https://permafrast.herokuapp.com . OP built this as well, and it makes it really easy to read cases without signing into Lexis, Westlaw, or, well ... anything. Just one of many examples of how lawyers can use tech to ma
25. 25.▲
    by adelevie 12y ago

    I'm not the author (but I know him and he doesn't have an HN account--I've also contributed a chapter currently awaiting as a PR). PRs are certainly welcome.
26. 26.▲
    by adelevie 12y ago

    Steve Marx created webscript.io. He's now a Developer Advocate at Dropbox[1]. [1] https://twitter.com/smarx
27. 27.▲
    by adelevie 12y ago

    Thanks for the detailed reply! I turned this into an issue on our GitHub repo here: https://github.com/18F/api-standards/issues/45 .
28. 28.▲
    by adelevie 12y ago

    Interesting re header data. Could you elaborate as to what kind of data belongs in headers, and explain why putting this data in headers should be a bright line requirement or a "sane default"?
29. 29.▲
    by adelevie 12y ago

    If you'd like to elaborate in a way that would be highly visible to 18F, feel free to weigh in on the issues page[1]. I will point out that JSON is recommended as a default, and if there is a compelling reason not to use it in a specif
30. 30.▲
    by adelevie 12y ago

    It's really great to see this on HN. Major kudos should go to Eric Mill, Gray Brooks, and everyone else who contributed[1] to these standards (as well as the White House, whose API standards 18F forked[2]). There is a blog post[3] that