325 karma · joined October 2, 2010
The official docs were vague and examples pretty bare, so I made a inspector/debugger app to understand the reverse proxied container env that you cannot ssh to.
This could unlock cost effective Python services for you.
- big enough for standing desks - most noise isolation headphones will clean up your audio for meetings - add whatever solid color backdrop or virtual backgrounds to clean up your video - built-in air circulation to/from windows
for example:
- movie-title title1.mp4 "my awesome movie" --style=lower-left
- movie-cat title1.mp4 clip1.mp4 clip2.mp4 clip3.mp4 --transition=blur --output movie1.mp4
- movie-upload youtube movie1.mp4
Edit: formatting
Listen to this podcast where the author describes the project: https://talkpython.fm/episodes/show/32/pypy.js-pypy-python-i...
It's open sourced via BSD 3 clause: https://github.com/koenbok/cactus
I especially liked the "deploy to s3" feature, IMO the cheapest way to run a highly scalable static site today.
Alternatively, a "deploy to GitHub page" would be neat as well.
I would work on extending Cactus if it was a bigger problem personally, but so far what's released fits my needs already.
My recommendation is - if you don't have the knowledge or patience to build one yourself, you should not ask one to be built for you, because it will break and you're gonna have an unproductive day/week while you wait for help to arrive. Not worth the headache and lost productivity.
Hackintoshing should be strictly treated as a hobby.
My Hackintosh built in 2012 for less than $800, it has:
- Core i5 3.4 GHz (still competitive with Mac CPU specs sold in 2014 and into 2015) - GeForce GT 640 with 2 x DVI + 1 x HDMI for a triple monitor setup (much better than anything in Mac Minis and some iMacs) - 2 SSD drives for main OS - 2 x 3TB magnetic drives (sync'ed to Amazon Glacier)
Note that two years after my initial build, faster CPU options and graphics cards can be swapped in with incremental upgrades as my requirements increase.
I'll post separately in this thread tomorrow about my recommendations and experience running this machine, but it's hands down the best Mac money can't buy, with room to grow.
I don't do it because I don't want to give Apple my money, I have to do it because Apple won't take my money.
-
P.S. IMO, Hackintosh only makes sense for desktops. While the various methods could get it to work for laptops, no manufacturer comes close to Apple's build quality. That trackpad is just amazing.
I'm not affiliated with the developer, just a big fan.
I used to automatically provide feedback of why a candidate did not pass the interview, then I had a few sour encounters where the candidate just did not react professionally. For example, one candidate bemoaned the emphasis on CS fundamentals in our interview. In that case, the candidate was coming in from a mostly front-end webdev background, but our tech stack extends far below the typical webdev "full stack", where knowledge of OS/Networking/Compiler fundamentals is helpful in everyday design decisions. As a small team, we bias towards generalists for now, so while the person might be a great fit for his skillset in another organization, it just wasn't a great fit for us at that time. I tried to explain this, but I received a wall of text complaint email back. I had taken an hour out of my day to write immediate and specific feedback about his interview, and all I got was pushback. This is probably why HR stands between engineers and candidates.
1) does the company provide a product or service that makes a world a better place? (e.g. Nest, Tesla would qualify)
2) are my potential colleagues great people that I will enjoy spending time with and learning from? (it's miserable to work for miserable people)
3) will the company pay me a market wage such that I can provide for myself and my family
I'm sure similar tools exist for the emacs/vim communities.