-
Notifications
You must be signed in to change notification settings - Fork 0
Peopleskills
Please put down the skills you'd be prepared to donate to SkiffHack!
@almostobsolete (twitter) / @almost (github)
General programming in Python, Javascript (browser and server side), Ruby and PHP (if I really have to!).
I've worked with the Twitter APIs before. I also quite enjoy designing and implementing APIs myself!
@j4mie (twitter) / @j4mie (github)
Python/Django, JavaScript and, if I must, PHP. Can probably help out with deploying the apps too.
Not technically a Skiffer, but I organise the Brighton Python User Group and generally hang round the Skiff occasionally. Happy to help out.
@mikepea (twitter) @mikepea (github)
Linux systems & application stack, security, networking. Puppet & provisioning/deployment. Arduino and basic electronics. Very noddy C, PHP, Perl, Ruby and Shell coding. Monitoring systems: Graphite, Munin, Nagios.
Also not technically a Skiffer, but I'm a director of the Build Brighton Hackspace, and so am happy to help out. And probably poach some of the code for our benefit too ;)
@tysonsavage (twitter) / @tysonsavage (github)
Websites and apps in Python with Django, really basic Javascript - mainly just hacking together cosmetic UI or simple form stuff with jQuery etc. - but am really enthusiastic about changing that! PHP is v rusty, but if its a life or death situation I suppose could echo it together.
I'm pretty good at spotting & robbing quality code and mashing it together in a dodgy state just well enough to make cool things work :)
@stevepurkiss (twitter) / @stevepurkiss (github)
Drupal, because no matter what language you use, it's far quicker, easier, and cheaper to maintain to piece together apps from tried & tested collection of 10,000+ modules providing generic functionality than sitting there re-inventing the wheel. [citation needed] ;-) <- ho de ho watch this space ;)
I spend most of my time now helping people architect and plan systems by using good old marker pens and paper on which we map out user requirements and decompose into contexts and features from which we can then build a system. Doesn't have to be in Drupal in case any nay-sayers reading (see snide comment above made by someone re citation), but you'd be a frikkin idiot not to. To be quite frank I don't care if you do use Drupal or not, good luck, we'll see who builds the best, most useful shit on the day eh...
.oOoQ