gibsjose

Very well written and well thought out comment. It gave me a new perspective on the traditional conception of partisan politics.

If you’re looking for something more lightweight in between vanilla GDB and a full GUI frontend, I would highly recommend GDB Dashboard: https://github.com/cyrus-and/gdb-dashboard

It’s just a single file (replaces your ~/.gdbinit) that wraps your GDB session with a nice TUI using the Python API. I’ve found it to be a nice middle ground.

Love the idea. Please try to add Madcap (https://madcapcoffee.com/) to your list of coffee producers; they are one of the best coffee roasters in the US, in my opinion. They already have a traditional subscription model that ships all over the country.

Magical is truly the word to describe Docopt. I use it for all Python code I write and have also used the C and C++ variants. I would highly recommend Docopt to anyone writing command-line utilities.

I'd love to hear more about this. Could you expand on how you measure your insulin response and as a result how you avoid erratic energy levels?

As one of the engineers affected by this (Goddard Space Flight Center) I could not disagree with you more strongly.

I really like the concept. One small improvement I would recommend is to allow cards to be swiped in any direction, specifically up or down. Depending on how you are holding your device, it can feel more natural to swipe up to discard, for example.

Not only that, but it took a solid minute of frustrated tapping to successfully hit the 'I agree' checkbox. Using chrome on iOS.

Did you reply to the wrong comment? I certainly never suggested they shouldn't be learning math or that the program was a bad idea.

It is quite fascinating to imagine inmates passing their handwritten Vigenère encrypted secrets using Diffie-Hellman key exchange.

Yeah, that's more correct

Turns out we are funded. PACE may be funded as well actually, but there's no clear indication either way. I was at the all-hands a few weeks ago where it seemed to be a bit more grim but lately there has been some talk of PACE surviving.

Agreed. Most major satellites are now designed with potential reservicing in mind, at least to some degree.

While it's not entirely impossible that some classified mission has done some basic reservicing of a DoD bird, I know from working on Restore-L that we will be the first ever to do what we are doing, namely autonomous rendezvous and capture of another satellite in LEO and reservicing.

The X37 does not have the mechanical tools or sensors required to perform the kind of reservicing Restore-L is doing.

Refueling satellites will absolutely be a thing :) Restore-L is going to do just that in 2020-2021, and do it autonomously to boot.

I work on Restore-L and believe me, there is a huge need for on-orbit satellite refueling and reservicing. The vast majority of satellites reach their end of life due to depletion of fuel, not due to electrical problems or sensor issues. This will be a huge business one day.

Yeah, the SSPD (NASA office behind Restore-L) started with the Hubble reservicing missions

On-orbit satellite servicing and refueling has not been performed as of yet, but we are currently working on it: https://sspd.gsfc.nasa.gov/restore-l.html

I was rejected from Google when I first graduated from college. Now I work at NASA and I'm very thankful I didn't get that job.

Saying that the hiring process is flawed isn't the same thing as saying everyone is special and deserves a job there.

From my anecdotal experience, I felt that they focus too much on algorithms and give the same interview to every candidate regardless of their experience or desired job. I made it very clear I wanted to work in embedded systems and write code for microcontrollers and they asked me questions about graph theory. Algorithms are not everything, especially for a company with such diversified technology opportunities. If I'm working on search, then sure. But embedded software? Can't they take the time to focus the interview even the slightest bit?

Not a big deal though. I know they have an endless supply of candidates and thankfully we as software engineers have a pretty good selection of places to work.

There was a time when we weren't exactly sure which client we were going to refuel, but as far as we know, it will be Landsat-7. I believe NRL and possibly others are working on reservicing more "hush-hush" clients, but I can't say for certain for that very reason haha.

My group's mission at NASA is highly related: https://sspd.gsfc.nasa.gov/restore-l.html

We're going for LEO reservicing. It's quite a challenging mission, especially since our client was never meant to be reserviced let alone rendezvoused with in the first place.

I'm curious to see the data collected on guesses. Some were quite difficult to guess, like hashes per second with bcrypt not knowing the cost factor, but I guess we can assume some sane default.

I would have really liked to see all these numbers in C, and other languages for that matter. Perhaps add a dropdown box to select the language from a handful of options?

This is right up there with \usepackage{amsmath} as a truly must-have package for any real scientific paper.

Haha I'm at GSFC so I'm somewhere in between, but we still have to deal with 95/495 traffic, which is a real drag.

You certainly have a point, and I definitely was generalizing.

My social circles consist mostly of international folks who work in various agencies and laboratories, and a few who work in private industry.

My biggest fault with DC (and most of the east coast to be honest) is just the difficulty of starting a conversation with someone. It seems like a lot of people walk around with their heads down here (either glued to a phone or the pavement) so as to avoid making eye contact. Folks here also give me strange looks when I say "sorry" all the time.

But hey, different cultures and different strokes. Not saying one is objectively better, but I definitely know which one I prefer personally.

Although I don't think this is feasible or even necessarily the right thing to do, I personally am dying to go back to the Midwest.

Coming from beautiful, friendly, cold Northern Michigan, I'd be ecstatic to get out of the DC area, but good luck moving the other 10,000 NASA employees.

It's a different culture in the Midwest. Some good, some bad, but overall I personally prefer the ability to have friendly conversations with strangers back home than the (generalizing here) awkward, egotistical, self-interested metropolitan area here. The first questions you are asked in DC are inevitably "Where do you work?" and "What's your title?". That being said, DC is a beautiful city and there's a lot of great things here.

But still, I'd much prefer to be camping on a beach on Lake Michigan...

While this seems mainly useful as an academic exercise, the `printf "#include <unistd.h>" | gcc -E - | grep size_t` bit to easily grep in header files was worth the read.

Second this. It showed up as Times and I almost dismissed it entirely.

May I suggest 'Menlo' as a backup?

It's nice you made your Trello todo list public, but why not make the game open source and use the GitHub issue tracker so we can also open issues and feature requests?

As a NASA flight software engineer who has created and worked with coding standards for critical software, I would highly recommend Gerard Holzmann's (JPL) Power of 10 Rules [http://spinroot.com/gerard/pdf/P10.pdf]. This is a set of the 10 most important (and thus highly restrictive) embedded flight software rules. It gets straight to the point and, at only 6 pages, is much easier to apply to actual software development than this ~400 page tome.

EDIT: Another great point referenced in the Power of 10 rules: a requirement is only valuable as long as you can enforce it. With some exception, if you can't enforce it with a static analysis tool or something of the sort, it might not belong in your coding standards.

No worries; thanks for the reply.

Have you had experience with DACA + 245(i)? We're hoping that doesn't complicate things much.