I'm hiring for a position on our Linux Kernel Validation team which performs CI/CD on upstream Linux kernel branches, with a particular focus on long term stable branches.
I primarily wanted to note that I used 2^X notation in the math, in case it was confusing for folks. I used KB/MB/GB to be consistent with the language AWS uses on their S3 pricing page (https://aws.amazon.com/s3/pricing/).
If you write a AWS-native service that uses S3 as a back end (a very reasonable thing to do), it may create many small files in S3. It would be unreasonable to incur the costs to retrieve them and tar them up, and it also does not make cents to "click the box" to have them archived to glacier.
How will you avoid being sued by artist's representation (i.e. record labels, RIAA, etc)? I would also be highly concerned about validating the recipient of the money, especially since they're unlikely to reach out directly.
The best you could do is purchase music from the musician though the least-fee-laden service available, so they get the most money legally possible.
I've been working on a Git migration inside a fortune 50 primarily windows shop for about 6 months.
This line caught my eye:
"Some of its benefits fit well with the trends we see in software development: loosely coupled systems, distributed teams, lots of component reuse, incorporation of OSS, etc."
It's not a new trend. Nevertheless, I'm smitten that MS has acknowledged and embraced the model.
For us, the biggest issues with git on windows are:
1) SSH inconsistencies (cygwin/putty/msysgit/securecrt/etc) - I support users that use any combination of these.
2) Git implementations (cygwin/msysgit/git extensions/etc) and UIs all handle git and SSH differently. Users will typically have multiple copies of git installed and used, depending on context.
3) Support for HTTPS mode is inconsistent and in some cases non-existent. None of them can cache credentials.
To summarize; multiple git environments + multiple SSH environments + limited https support = pain.
For the first time I've recently been seriously considering going paperless at home.
However, every great solution involves uploading my scans to online services.
This is something I'm not comfortable doing with my sensitive data (i.e. tax records).
Has anyone found or developed tools that can be run locally to organize my files? Something like evernote? I'd like to just scan and shred, and not have to fuss too much with naming files, manually organizing files, etc. A good pdf search interface is a must.
Solar panels, sublevel required under toilets, multiple tanks, electrodes.. It will need to be simplified and miniaturized dramatically to be viable - but it seems possible.
It sounds like the solar panels are oversized, and mounting it on a motor is particularly gratuitous. They mentioned batteries, but I don't know why they would be necessary. Couldn't the waste be queued up until daylight to be processed?
However, it's clear they're simply proving the technology. The question is, can it be manufactured and packaged efficiently and compactly.
Popularity begets popularity. I evaluated a ClearCase replacement in early 2012 for a large company, and Git is clearly the "nobody ever got fired for buying IBM" SCM.
I looked at hg. It is easier, especially for the windows users. However, git was already coming from a few different directions and hg's simplicity was not enough to tip the scale.
We are now mid-migration. If git devs are listening - this is my biggest nit:
$ apropos git | grep ^git | wc -l
159
I do believe an alternative "porcelain" will eventually supplant the core git commands, making it more user friendly.