Looking for some short term/in-out contract work for at least the next couple of months. I can help take down some old tickets or implement new features on a wide range of projects. Personal ones, small business, saas etc.
Primarily work with Python/Django, have dealt with frontend (angular 1 and a bit of angular 4 now, vue), bits of Node, d3, devops, SQL.
Github/resume: http://github.com/paimoe/paimoe
Email: hn @ [github username].com
Remote: Prefer no
Willing to relocate: Only to above places
Technologies: Python, PHP, JS, HTML/CSS, minor ops, Angular 1, node
Resume/CV: https://github.com/paimoe/paimoe, full CV available if needed
Email: [email protected]
Remote: Prefer no
Willing to relocate: Only to above places
Technologies: Python, PHP, JS, HTML/CSS, minor ops, Angular 1, node
Resume/CV: https://github.com/paimoe/paimoe, full CV available if needed
Email: [email protected]
Hey guys, first 'proper' startup. https://www.sheepbackups.comI've tried to design Sheep Backups to be very simple and straightforward, as well as a good focus on restoring backups (including test runs, fully listing the steps the restore will take etc). The goal is to be as user friendly as possible, as opposed to blanket saving hard drives where things may have changed, or you only want to...
Remote: Yes
Willing to Relocate: Yes, looking to move to UK/Berlin/English speaking
Technologies: PHP, Python, Javascript, some Angular/d3, also been doing work managing servers/processes and lately some wordpress work
Resume: https://github.com/paimoe/paimoe
Email: [email protected]
Remote: Yes
Willing to Relocate: Yes, looking to move to UK/Berlin/English speaking
Technologies: PHP, Python, Javascript, some Angular/d3, also been doing work managing servers/processes and lately some wordpress work
Resume: https://github.com/paimoe/paimoe
Email: [email protected]
Gets interesting at 3 mins. There's also an explanatory series.
I think the problem is as mentioned, often American ones are much different. It seems more like a free for all circle with a random bunch of roads exiting and entering, with no lanes marked. Also construction obscured the view to the left.
I did come across a few "normal" roundabouts at least, but they either don't exist or are terrible.
Not 100% sure on how to solve the "legally binding" part if the other party declines digital signatures, but it'd be a good way to get the contract written and agreed on.
"Goose - A JS library for 3D graphics" --> "Goose"
Yeah thanks guys.
As an example, Requests (http://docs.python-requests.org/en/latest/). If you've ever done URL fetching in Python you can immediately see the value and cleanliness of it.
A couple of projects I've come across don't have anything like it, and only have more of an API reference. I understand it may be early days and documentation hasn't yet been a priority, but I really love to see the advantages of the library, particularly if you compare it to the old way of doing things.
There's a lot of `if (IS_MOBILE)` around the place, to not download a large amount of extra stuff on mobiles.
I'll assume you use Git (if not, replace with your workflow). A super simple fabric script might simply be a `git push`. Instead of typing "git push origin master" in order to push to github/bitbucket/wherever, you'd run "fab deploy". Not going to go into the fabric specifics, but deploy() would pretty much just call git push.
Anyway, that may have confused you even more. My point is, start with something incredibly simple. After you've added git push, you can add to your fabfile.py to ssh into the server, and run git pull. Then add in something to run south migrations. Then collectstatic. Eventually you'll build to something that you can simply run, and everything will be updated and all good.
> Card, PIN 1234 -> bank -> access John Smith's account -> access "1234" setting (max transaction of $50 otherwise declined).
> Cart, PIN 2345 -> bank -> John Smith -> 2345 is only valid on weekdays
I originally thought of it as a way for parents to loan kids their cards, give them a temporary PIN to use.
Might make more sense to adapt it into the CVV system (or a new system), where each specific CVV would correspond to a setting you determine. They can be created by you quickly and securely with a bunch of constraints.
But then I realised I had no idea how CCs worked, and assumed I'd either have to get a bank on board, or a CC company to implement it, and gave up.
I'm sure I'm not doing 100% of what's possible to be able to sit back and pick and choose whether I want the 150k job or the 180k job, but almost all of these "recruiters suck" posts apply to a small minority of people, those near the top of their profession.
Maybe I need a "Do you make shitty weekend projects that end up going nowhere? Let us know" site.
Also, there was something posted a while back that did music albums, but I think the guy was shutting it down/open sourcing it.
Either way, glad to see I'm not alone.
I'd say if it's a side project/more wishful success, go with Rails. At the very least, you'll learn something new and improve your skills. If it's something that absolutely needs to work now and is a bit more complex, use your existing CI knowledge for now.
But at some point (perhaps now) I'd just bite the bullet and go with Rails (or Django of course, but either would be a step up).
http://steamxl.com - Chrome extension, coming along slowly, but haven't spent too much time on it. Still learned a lot from it.
Currently the goals for it are to implement and use redis in a production site, learn to make a chrome extension, and just to get another thing launched. Possibly also to install/config a server from scratch (on Linode).
"Full stack" dev, currently getting http://www.minecraftsaver.com going. It's a desktop wxPython client and Django site. Used AWS for the first time with it (EC2 to render maps, S3 to store, Cloudfront for cdn).
More projects @ paimoe.com
I used wxFormBuilder: http://sourceforge.net/projects/wxformbuilder/
It's pretty much a point-and-click sort of thing, but after the initial drafting/mockups I tweaked it by hand (small things like names/strings, as well as adding the events). I used Python 2.7 - not sure about 3.2.
If you need any help send me an email and I'll do my best to help. I've managed to compile/run it on Windows ok, and as far as I'm aware it's possible to compile it for Mac/Linux. I just have no Mac to test.
Either I'm coming across wrong or (sort of unlikely) they just aren't too great of an example.
I use TortoiseSVN, I'm not sure if you do. But when I want to commit in SVN, I bring up the commit tool, select the files I want to commit, write a message in the box, and click commit. But I have to do it all in one go. I can't close the commit window if I forget something, otherwise I have to make sure I copy out the message to paste in again, select all the files.
With Git, the staging area is the same as this commit box. It's just a bit more stretched out. Instead of selecting files to commit, and doing it then, you add files to the staging, and commit the staging area. It's a different way of doing it, but I've found it much better for myself. Instead of doing it all in one go, I can add to staging and keep working. Usually I keep open all the files that have changed so I remember which ones to add.
Regarding the remote repository, you still can have it remote. Simply instead of "commit" being the last action you do to push it to the remote repo, make sure "git push" is. I use bitbucket for this, so I know it's "safe" in case of computer death or something.
I have one more project using SVN and I want to move it to Git, for just me, I don't work in a team or anything like that. I like the staging area, it feels "lighter" and that commits are much less drastic, and diffs/logs are MUCH faster since it's all on your computer. Also, `git add -p` to craft your own commits.