The Geek problem
For some possible solutions, the links below are absolutely invaluable.
These guys are actually carrying out successfully our principles: "Lessons learned: 1) Keep it very simple 2) Don’t re-invent the wheel 3) Go with proven and solid technologies when you can."
Suggests the mythical desingineer can exist.
"A programmer writes code.
Working with geeks is one of our greatest challenges.
The standard geek culture is to work on a personal project in a language particular to that individual.
+ There are lots of people out there for us to work with _ The project is then a ghetto
The problem is that our path (open industrial standards) is against the dominant techie culture.
What incentive is there for geeks to work with us? How do we tell them what to do?
Solution?: we fish for people who work in traditional industries with open industrial standards.
We need to be fashionable?
Does Gamification help?
Links to look at#
A designer creates visual art.
A hybrid developer designs code, visually.
Think about that. If you go nuts when pixels are out of place, you also go nuts when code is out of place. The same instinct behind your design senses, come into play when you are writing code. Forget that, you stop writing code and start designing code. You inherently understand the technical limitations of your designs, and the design limitations of your technicals (huh?)."
His basic argument is: stop looking for a tech co-founder, and go about earning one.
His withering wisdom includes:
- Start anyway by teaching yourself what you need to know
- Prototype, earn respect for yourself and your idea
- Earn yourself a technical co-founder when you can convince them your way is a better option than theirs and you’re not just some fool with a pet idea, wanting a logo and some pie charts
A good shortcut to that last accomplishment might be someone you know personally, perhaps who you’ve worked with before. Is there a junior or senior developer from a previous gig who will respect you for a previous role and be ready to build their own baby with you?
For good passports to the prototype, it comes down to old-fashioned hard work. Start your own marketing research and customer development, get backing if you can leverage your own network, create mock-ups or wireframes and nail down a realistic description of your minimum viable product.
Finally, a top technical dating tip: you’ve no idea how much more motivating it is to someone technical to look at the shitty prototype you had built for $500 on Rent-a-coder, or painfully clubbed together yourself, and say, “Obviously I can help you build that much better,” than it is for them to listen to a shitty pitch."
How do we get people to use our site rather than Wordpress + huge increase of membership + Make project relevant + Share date means data ("Join the Internet) - We don't have any mean to give support - reliability / cost of servers - ethical: the data will be shared so we have to be transparent about this. Everybody would be spamable by email. So people we host have to subscribe to website guidelines before.
What we need > connection and conversation (failure because of geek problem and because success of corporate tools for now) But activists are using FB on Twitter. We have to think about what options/service push forward to get focus.
What we should do Things that Liferay can do not what we'd like liferay to do. Any idea should come from the existing software.
Task to schedule Sifting through the website, uniform look and feel. Every 3 months we should revisit the site.
non techie: being content producers/trainers and work with corporate tools Tech: working on liferay and fixing. 1. Happy now, no reward 2. unhappy for a while. Potential reward
Options - H/M: use SOME corporate tools (but none of them offer transparency) to organise with alternative tools. Example: integrating google calendar/task list in Liferay.
Rss in now every website has it but it's still necessary. It isn't cause a revolution anymore but it's a stepping stone. (need to move this)
How to make geek do what we ask a> reinvinting new geek culture b>find geek who don't have that geek culture ... How do we work with geek from other culture? (access and bohemian culture)
Let's try this Regular meeting at passing clouds through HackTheMedia structure. Make it bigger than java wide, using the LJC community. Having same HackHackers kind of talkers. Possibly schedule on a dancing night.
Problem with Geek culture:
- They all talk accessibility, simplicity but nobody's prepare to do something about it.
- This is a psychological problem.
Manifesto for reshaping the geek culture Build practical outcomes by writing a list of do's and don't
Open social Using Google gadgets. Sharing data through different social media. speeds up developement as eveybody understands language (java script). People can dev really quickly. It's a faster way to build our infrastructure as it's build in in Liferay. it takes away Our badges system could be written like this. - it's a geek culture problem as it's potentially unsecure and geek don't like it. + we can understand and change the gadget ourselves
How to run Liferay (move this) Grab startup.sh in window start up bash and drop in terminal. And it's loading. Watch the process loading through the system monitor. As soon as activity drops to 0 it means it's running. It runs through Windows as well but might need extra install but Ubuntu already have the Java set up.This will using all the memory on your machine so close other applications. Its has a startup wizard for the 1st start.