sparkslabs
add password / add passwords
* https://github.com/search?utf8=%E2%9C%93&q=add+passwords&typ... * https://github.com/search?utf8=%E2%9C%93&q=add+password&type...
add secret / add secrets
* https://github.com/search?utf8=%E2%9C%93&q=add+secret&type=C... * https://github.com/search?utf8=%E2%9C%93&q=add+secrets&type=...
I've been waiting 5 months for my order to ship and despite confirming my order 4 or 5 times, it's still not shipped, despite repeated emails from them stating it would ship in July, then August, the September.
Utterly incompetent company from my perspective and anyone who orders from them should be aware that they're little different from a scamming company. I they do ever ship, I'll be utterly shocked - as far as I can tell, they've taken the money and run.
Wouldn't be surprised to see them go bust before shipping anything.
This sort of announcement where they say they'll ship new orders quickly before actually shipping the ones they can't be bothered to deliver - and can't be bothered to update people when their orders will ship adds insult to injury.
They've come across as I say to me totally and utterly incompetent. Buyer beware.
For a selection of good reasons as to why using github like this is a bad metric take a look at:
https://blog.jcoglan.com/2013/11/15/why-github-is-not-your-c...
(There are lots of good counterpoints to the arguments there in the hackernews discussion of that post here - https://news.ycombinator.com/item?id=6738952 - but personally I still think it's incredibly dangerous to start assuming that you can really measure experience from github.
After all, do you also include repositories forked, but not worked on? If so, it'd be incredibly easy to game this...
As a toy it seems kinda fun/neat, but as a tool... far less so.
(ie The vast majority of claims in that article are nonsensical)
However, given in practice it's essentially contract work it's about 30% less than average contracting rates.
If they manage to get paid work equivalent to working full time though, they'll be earning a fair whack more than me, so good on them.
Whether it seems reasonable or trustable probably depends an awful lot on where you are based.
This point is emphasised again later when he finds a new team in his org when MDD is failing. That team has a new manager (with 15 years dev experience), working with a new team and a new methodology QDD. Again, the team attributes success to QDD, not the people.
ie the success is down to people, not the process.
If you realise MDD (and QDD) is completely made up, that will probably explain things somewhat. Also subsitute MDD with Agile, and realise that Agile was created under similar circumstances and you'll probably get the point.
:-)
Implementing Actors – Guild Internals.
Readable concurrency in Python
How about a pen that also doubles up as a touchscreen stylus?
Guild – Pipelinable actors for python
http://www.sparkslabs.com/michael/blog/2014/03/07/guild---pipelinable-actors-with-late-binding
Blog post on a pipelinable actor system for python. Allows latebound outbound actor methods as well as inbound, allowing you to do things like build pipelines of actors. Very much a work in progress. Comments welcome.