These are updated weekly.
I am one of the founders of kiddom, an interactive learning environment on the iPad. We initially focus on math skills, and all learning happens in a story telling environment. We should be live on the app store in about a week or so in the US:
If you have any feedback, my email is in the profile.
If you happen to have an iDevice, check out Tiny Piano: https://itunes.apple.com/app/id477014214
It's a fun and free app that helps kids appreciate music. Feel free to email me at ronyeh at squarepoet.com if you have any questions.
On the flip side, a friend of mine uses this tactic aggressively when negotiating salary and equity at companies. It's always worked for him and is considered a "cost of doing business" when trying to hire this person.
What's the difference? The former was being hired for a junior position, the latter for a senior position.
It's all about leverage. If you can bring a lot to the table, you can play the "other people want me" card. If you are bringing relatively commoditized skill to the table, then that card just makes you look foolish.
Hope this helps.
> Right Time, Right Place
> Relevance, Comparability
> Don't Bluff
Right time is only when it will make a difference. Upfront is not the right time. The right time is when there is an actual/reasonable offer put forth with a flaw or other "bridgeble" gap, that if it were "at market" would be a non-issue. The other offer is evidence of "where the market is at". This is completely fair use.
Relevance and comparability, though, mean that you should not pretend an offer for X is the market for Y. If you do this (on purpose or unwittingly), not only will it most likely not work, you may raise some eybrows. Classic example is using a comp from one market (like, from SF) in another market (midwest), or between job-titles, or whatever. If you are truly deciding between a career in X and Y, you need to be very careful about this.
Lastly, be very careful unless you are willing to walk from the table. If you are 100% OK with taking the other job, for example. Alternatively, if the point you are negotiating is a definitive deal killer (ie, it will make you walk away) then again, it makes sense to consider bringing what you have to help get a deal done. This will give the other party some ammo to use internally to overcome a barrier, which is in both of your interests, etc.
Use this in addition to the value you bring and other context etc. as you mentioned.
I will say that I have competing offers, and I'll be up front about what I want to make. I think at that point my potential employer has all the information they need.
I make a list of the type of company I want to work with (I want to be paid $X, they should use this technology, I want to solve this problem or work on this project) and then I backtrace it and figure out which companies match those criteria.
Then, I contact those companies. I set up meetings when I can. My goal is to learn:
* What sort of projects they work on * What challenges they're facing (geez, our biggest client needs _IDEA Z_) * What skills they look for in new hires / freelancers * Other companies in the area / tech / market
Then, I do two things
If they mentioned a huuuuge problem / pain point they're facing, I send them a follow-up email talking about the problem they mentioned, what I can contribute to solving it, and suggesting a time for another meeting.
I follow up with any other companies / people they mentioned and set up a quick coffee meeting.
Periodically, I'll check in with my contact. Nothing spammy, just an update about something relevant to their industry / problem.
Rather than fight over the same jobs that everyone else sees on 37Signals / Reddit / GitHub / HN hiring / Craigslist / LinkedIn / Etc, I want to be at the top of mind with the companies I want to work with.
Every job I've had â€" salary or consulting - has come from someone inside of the company calling me up, telling me about a position they have, and asking me if I want to interview. This bypasses the slog through submitting a resume and fighting against 20+ other candidates for a position. This gets me the positions I want working on the problems I want to solve.
Chasing listed jobs is a mug's game for two reasons: (i) you need to compete with a mountain of applications, and (ii) people often list jobs that they aren't entirely serious about filling. Even if you have a strong resume and put 30 minutes into writing a good cover letter for each applications, the odds really are against you in this case.
Factor (ii) is still a problem if you get an interview because many organizations put multiple random barriers ahead of applicants. For instance, if you don't pass some test or flub a question or one of the fifteen people who talk to you just doesn't like you on an animal level you've wasted all the time you've put into the process.
Anybody who's using a recruiter, on the other hand, really wants to fill the position. The odds are in your favor because the recruiter is going to walk if the company keeps putting candidates through the gauntlet and rejecting them.
So how do you get people to call you?
Be active on the web. For me that's meant developing a few side projects and also developing connections and adding some content to LinkedIn every day... Even when I'm not looking for work.
If you get yourself known you can quit wasting time looking at job boards.
To grow your professional network I would recommend to attend to meetups, hackathons, user groups or even better to get involve in the organization. It worked pretty well for me.
I met some incredible people and got some good jobs offer.
I like that they have to disclose ballpark salaries. Makes it easier to get a sense for how the company values developers.
My previous position was via a university career fair when I was still a student.
(Sadly, the same trick doesn't work for boyfriends.)
This meant that my list of places to apply to actually grew every time I went to go and knock a few off my list. I met a lot of interesting engineers this way and generated a lot of leads that I wouldn't have found through HN Hiring or other boards. In some cases I found jobs that weren't posted online until after I found out about them in person.
I don't look. When I want a new job, I stop ignoring recruiters and wait to see what comes along. I've never waited more than a few days to have a pile of interesting opportunities. (I also end up with a much bigger pile of bullshit talent-trawls, but that's beside the point)
I wish I could say this was a function of my being awesome, but I think it has more to do with the job market in my area (PDX). There just aren't enough senior developers to go around.
go to offline networking events.
get to know your local group for whatever you program in. Seattle-python-interest-group has periodic job emails, and more importantly if I asked them for help I would probably get a couple responses.
- careers.stackoverflow.com - prospects.ac.uk (Though you need to have been a student to register) - s1jobs.com (Mostly so I could have at least seen one ad a day) - talentscotland.com - workinstartups.com
I'm a freelancer, and most of my work comes via referrals now. Not always, but it's been the case for the past few years.
Wasn't much different back when I was looking for full time work though. Even though I only worked for 2 companies, I use to get interviews through referrals, or through past colleagues that left and wanted me to come aboard.
Find the type of company you want to work for. Narrow your list down to about 5 of those companies you'd like to work at.
Now sit down and write a personalized cover letter for each of these companies and the role you'd like to play in said organization.
Now email each of the companies hiring depts, founders, etc with said letter and sit back. If you wrote a truly compelling cover letter (you should have if you are actually passionate about working for the company) you will most likely get some sort of response.
Rinse and repeat if no success.
As a multi-time founder and hiring decision-maker I always enjoyed a good cover letter and great interview more than a resume. Even when it comes to technical knowledge the most important thing to me is that if you did not know it you were smart enough and capable of learning it.
If you can knock it out of the park on a cover letter and show why you're excited to be a part of said company then they would be foolish not to hire you.
EDIT: Obviously you should still send a resume as well. But sending one without a cover letter in my opinion is the equivalent of career suicide.
Get involved: speak at user groups and conferences. If possible, step up and manage. You'll get work sent your way, and once you've built up a reputation (like when people come up to you at conferences and know your name but you don't know theirs), you can often drop the idea of needing work on Twitter and get a good response.
It links to a bunch of job sites. No referral links or anything.
The best part is that it also shows jobs that haven't made it to formal listings yet.
It's at http://www.jobquacks.com - regrettably I haven't built in support for mobile yet..
I'm a UI designer
I'm guessing that since the beta isn't ready yet, that's why you don't currently have a demo, but I'd rather like to see a demo or have a trial period before purchasing.
- How is the product tour presented to my end users, is it something I host or you host?- How well will it work with the somewhat crazy HTML/CSS I may have on my product?- Is $3 too cheap for something like this as it's somewhat specialist, i.e. I have to be a web site owner to use it?
Would I use it, not sure really. I don't have any live projects yet that would warrant a product tour.
But it's nice to see work in this area. My only other comment is the homepage colours aren't quite a vibrant as I would have liked - personal opinion.
Those guys help a lot when you've only got 24 hours to get over the hump (ask the Firebase guys).
Also, I may be biased as a hardware engineer, but I only consider hackathons that welcome both software and hardware projects.
"they don't really solve the problem that's in education right now, because they don't make it possible for regular people to be the creators of content"
SitePoint, in Melbourne, offers a grad programme where you rotate between four different companies, 1 month each, Flippa, SitePoint, Wave Digital and Learnable. You get to try your hand at a variety of technologies and stacks, and work on existing businesses.
Note: Some of these are quite start-up'y.
If you are aiming for total beginners - as in, new to programming and not just new to Ruby/Rails then you might have to re-word your About this book section.
You mention TDD, Git, 'default Ruby stack' within the first 8 lines of the book. While these are important points regarding the book - they only make sense to programmers of some kind.
I think if you give away a sample chapter of your book then this will be the first thing they read. You've got to convince the new folks you'll look after them & that they will actually get as far as building their first app. You may want to consider adding a book subtitle. I presume the readers you want to attract might not even know what Rails is! Maybe something like - Anyone Can Ride Rails - A fresh programming guide for enthusiasic beginners.
I like the informal tone as it's reassuring. I also second the what is Ruby/Rails & why should I use them, what can I build with it etc?
One thing I Have never seen is a "why" you should learn Rails and what you can do with it. What kind of web apps can I build? What can I do with it? Why would I want to?
Personally, I don't go for the informal tone, but it wasn't over the top and many books tend to go that way so no problem.
I like that it seems you won't be preaching about side technologies like git or tdd. It is an added difficulty when people add extra complications to a book, especially an intro level book. My personal opinion, don't go preachy on formatting or style either, just use well written examples for people to learn from and they will pick up your style.
One other thing that I just want to put in your head, I'm not sure if I'm even going so far as to suggest it, is the possibility of flexing scope to write perhaps a 50 page e-book, not dissimilar to the Sacha Greif ebook (http://sachagreif.com/ebook/) but for getting from zero to the next book on Rails for absolute beginners. The benefit of this would be that you could probably spend about 20 hours writing it (I'm pulling this number out of my ass, so I could be waaay off about this time estimate) and therefore you've risked a much shorter amount of time, which I'm assuming is your main concern.
Having said all that I don't want to be a downer here, I think its great you're writing a book and possibly getting people interested in programming :)
Great start and I look forward to seeing the finished version. Keep us updated on your progress.
What software do you use to write your book?
The company that can manage that for Comcast is going to be delivering hundreds of thousands to millions of dollars in value. If they didn't pay someone for it, they'd have to employ and manage a large development team just to do billing. Lots of salaries. That's what justifies the price.
If you're a startup with 3 payment plans and sometimes you have to give someone a credit because you had some downtime, your situation isn't even 1% as complex, and you can get by with a $50/month service or a couple hundred lines of your own code.
If you are looking for simpler products focused on small & medium businesses there are plenty of options available as well.
Of course if you are in North America you have Stripe as your first bet and for bit more sophisticated billing plus more options to do promotions, automated notifications, HTML emails, customer support portal, more complex metered billing, grandfathering of price plans (happens!), multi-gateway support etc., you should consider using a billing solution.
Disclosure: I am one a co-founder of http://www.ChargeBee.com, another Subscription Billing solution focused on small businesses.
Shameless plug: If you are looking for options to use payment gateway for credit card + bank transfers for recurring to save $$s per transaction you should try our solution (launching the ACH part very soon).
While doing research I came across Zuora [...]
After I research solutions to a problem, I end up with a list of requirements and a list of solutions with notes regarding each solution (e.g., pros and cons). If you were to post a complete list of your requirements and notes regarding each solution you evaluated, it would be easier to provide relevant feedback.
(If you didn't take any notes, you might want to consider the benefits of note taking in the context of a personal or company wiki.)
Just in case: XMPP and Jabber are the same protocol. Ejabberd is a popular XMPP server (written in Erlang, if you care about compiling from source; not hard to deploy). Google Chat uses XMPP and supports both GMail users chatting on external MUC servers and non-GMail users from another XMPP server joining GMail-hosted chats. XMPP servers usually host Multi-user conference service (aka MUC aka group chat), but it is separate enough that you could just configure MUC-only XMPP server with proper logging settings without allowing any user accounts on the server and connect via existing GMail accounts.
So far I have identified, Jaconda, hipchat and campfire (although I think it is out due to the lake of gtalk integration)
(Sorry for not posting this right up front)
After you did that you'd be much, much more likely to be able to build a successful project on your own.
If you get stuck on technicalities, two good things to try are (a) Google code search (http://code.google.com/codesearch) for examples related to what you're doing (for example, if you were trying to make an S3 connection from Python, you could check http://code.google.com/codesearch#search/&q=s3connection...) and (b) a relevant IRC channel if there is one.
If there are any programmer meetups in your area, try going and asking for help in person. When I was your age and trying to learn programming, I didn't know anyone who could help me. In retrospect, that was the #1 thing that held me back.
This seems entirely expected -- you have a good background in a programming language, but no real training in software design, which is to say, in breaking down a large project into useful components, setting and using appropriate abstractions, and managing complexity. This is unsurprising, since this is an entirely different sort of task than just knowing the syntax of a language.
There are several good options here, like the textbooks _Structure and Interpretation of Computer Programs_ and _How to Design Programs_, both freely readable online. Reading things like ESR's summary of the UNIX philosophy (http://www.catb.org/esr/writings/taoup/html/ch01s06.html) might also help -- much of the UNIX philosophy exists to manage complexity in a huge system.
Another good option is to look at high-quality existing free/open-source software and understand how it's designed and why. If you can, find something you want to change in it and contribute it back. The skills you'll develop in understanding how to find your way in a large software project will serve you well in designing a large software project yourself.
Google Code-in starts next https://code.google.com/opensource/gci/2012/index.html .
"The tasks are grouped into the following categories:
1. Code: Tasks related to writing or refactoring code 2. Documentation/Training: Tasks related to creating/editing documents and helping others learn more 3. Outreach/Research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions 4. Quality Assurance: Tasks related to testing and ensuring code is of high quality 5. User Interface: Tasks related to user experience research or user interface design and interaction"
I did the college version (Summer of Code) and it was a very rewarding experience. I think the code-in can put you in contact with some organizations that might want to mentor you. The Mozilla Foundation has a bunch of projects you can contribute patches and fixes to as well.
If you don't know it already, learn how to use git. I would also suggest the book Programming OpenSouce Software by Karl Fogel (just google for it, he offers it free online).
I started when I was 8, first professional programming job in 10th grade...
The jump from intermediate to "complete" is indeed very large, so expect a journey.
You need to find something you enjoy working on that you evolve over the next couple of years to learn about software engineering and what automation is important etc. This could be a game or an extension to an open source game, it doesn't really matter. It will almost certainly be a failure in some sense, so it's good to get that first failure out of the way so you can scrap it, revisit, etc.
I think coursera would be a great place for you to start, though it may require you to learn a new language (this is one step on the journey towards advanced in X language, I expect it would be octave/matlab) I'd recommend doing the introductory machine learning course and whatever other stuff interests you.
From the quality of your writing, you're quite bright for 14 - so stick to it and don't neglect your physical health and artistic/emotional/cultural education because you need to be free of distractions to reach highest level.
Do you want to program something interesting for you? (then figure out what you want to program, figure out the technologies it would take to make it happen, then learn them, and do it)
Do you want to get better at the trade so that at some point someone will pay you to program? (then go through MIT's OpenCourseWare: http://ocw.mit.edu/index.htm on CS topics to build up your fundamentals, then start reviewing/helping/hacking on open source for a while)
Do you want to use programming as a tool to do other things that you are interested in? (look around at what topics are necessary to understand, learn more about those topics, and go for it)
Personally, I knew when I was young that I would be into programming; when I was 5-7, we did LOGO in school, but there weren't really any programming courses worth anything in my high school (Cobol, Fortran, Hypercard, and Pascal), and I took the two electronics courses that were offered. I held myself back until college, where I did my best to learn and program as much as possible. After college, I went to grad school, continued programming as much as I could (I wrote an editor in Python for Python, dozens of data compression libraries, several distinct MUDs, ...), and got a PhD in theoretical computer science. Since then, I've been working in industry (because the academic market is crappy right now).
So I again ask; what is your destination? If you don't know yet, that's okay. You can improve your skills, your fundamental knowledge, and your technique without taking formal classes (see my link to MIT's OpenCourseWare). Heck, you may even be able to do so without talking with others (though it is hard). Once you do figure out your destination, it's a lot easier to ask for directions to get there.
Reading Hacker News might get you excited, thinking "There are tons of people just like me out there!", but we are geographically distributed; and most aren't like you at all.
I know some of your story. I lived it. I've had a lot of success, and here's how I came about it:
Write a list called "What I want to be making by the time I'm 30", and devote it to memory. Stay abstract and philosophical. Talk to people who know about who you'd need to hire to accomplish those goals, and go learn to be those people. You have time, but not as much as you'd think. It takes 10 years to master a skill, and I'm guessing you'll have at least 4 to master before your list is ready for implementation. Start now. You can do more than one concurrently. The further along you get, the easier it will get. The goal is to master. Maintain a hunger for purity. Don't use something until you know exactly how it works, and why it was created. If you like something, try writing your own version.
It will be very hard at first. Keep that list in mind for motivation. Get jobs requiring your required skills, and always volunteer for the tasks your coworkers are afraid of. You will make mistakes, you will fail from time to time, but every year you will get better, stronger and faster.
Someday (if you stick with it) you'll be able to invent and build things that are yours, and yours alone. Things that matter. Things that change lives. Corporations will depend on you specifically. You will move the state of the art forward and make the world better.
Make sure you never forget what it felt like when you were new. When you'd take out a pen, and draw interface designs for a product you can't build yet. When "This would be so cool" outweighed "This will be so hard to build". Create your own challenges and break through them.
You'll do great :). I'm looking forward to a chance to hire or compete with you some day.
1. There are a lot of free CS courses being put online. Start with the courses at Udacity.com they are the most "friendly" to start with. Then move up to the university level courses at coursera & edx.
2. Find a local user group. Connecting with other programmers in your area gives you a support network to ask questions to.
3. Study algorithms.
4. Write lots of little command line apps. Don't worry about them being useful just focus on making the code good.
5. If you are not already doing it take all the math classes you can.
You are 14 and that is a good thing. If you stick with it and keep learning you will be a badass when you are 18.
Maybe a to do list app or maybe an app that you can chat with your friends on or track your DVD/other collection . . . organize photos or maybe a family meal planner.
Pick something you are interested in and then start trying to build it at a basic level.
There are lots of tutorials out there for the individual components you'll need.
Once you have the basics up and running then start adding features.
As far as the APIs go choose something simple for starters, like obtaining a piece of data you want to incorporate into your app via an API and go from there. Maybe creating a basic HTML5 mobile weather app.
You are going to have to learn some things on your own even in college so don't worry about advanced classes not being available at your school. Classes are typically going to be behind the latest trends anyway. They provide a good foundation but won't cover everything you need.
Some ideas for new things to check out . . . skills to learn.
Learn to develop mobile websites and apps using jQuery Mobile.
Learn Ruby on Rails.
Create some simple iOS apps.
Create a websites for friends and family.
It seems like you want support in expanding, mentorship etc.
There are a couple of options you have. You can see if you can take classes at your local junior/community college in python.
You can try to do what you want, and when you get stuck, go on a python mailing list, a irc channel, stackoverflow.com, a python user group, a hacker space, etc.
You can also decide things are too hard and give up, or put things off. I won't judge you, programming is often difficult and frustrating when I'm doing new stuff.
Anyway, do something else, dive in, or give up.
Start small. Maybe start with a single cloud platform, like Evernote or iCloud. Once you know the ins and outs of a particular platform, and are an expert on that, move on to the next one.
Baby steps, just keep moving in the right direction and DON'T STOP and DON'T BE AFRAID.
You are experiencing a fear of success. Overcome it, and just keep your head down and ship.
Get it? It should be scary. You are doing something new to you.
Watch the movie "Indie Game". If you dont have the $10 to buy it I will gift it to you from iTunes.
Ask questions, you are 14, you wont be bothering anyone. If someone gives you a hard time it is because they are jealous. E-Mail in profile.
As long as you keep at it you'll learn how to swim in larger and larger oceans.
You can ask questions on sites like StackOverflow or in IRC if you get stuck.
Happy to have you guys visit, and we'd love to talk about using the product too.
We're in SOMA. stefano ]a-t[ betable.com
We're based in San Francisco but founded by two Canadians.
For us non-technical folk, you might wish to add a section to your how-to explaining how Kera.io would interact with proprietary data; for example, if our app happens to be financial, would you be able to see any of it? Or is the script hosted on our end?
(This may be obvious to a dev, but not to me, and therefore caused me to send this to our devs to ask)
Seems like there might be a need for the startup map.
That someone can post this on HN and get a bunch of invites back.
Does doing something like this scale? What if everybody just decided to post "hey I'm coming to SF is there a place for me to crash" or "hey I'm coming to NYC anyone want to have coffee?" or "I have a problem writing perl..."
Since there are companies that you are trying to reach, and you must have some idea of the type of company you want to reach, why not put some effort into doing something other than the obvious easiest thing which is to post an "Ask HN" and see who bites?
(For the record I wouldn't feel the same way if a top commenter who spends much time on HN made a similar request because at least they have put time and effort into HN (and I don't consider my karma as anywhere near that point for the record.)
No idea what I'd do with the app, what it does, or why I'd want it. "Customize a tour to a point of interest" is not meaning heavy for me. I've never customized a tour in my life. I don't know why I'd want to. You'll want to A/B/C test lots of headlines/copy, but I'd say this is a pretty rough start.
What are hidden gems? Restaurants? Tourist spots?
Your headline/copy needs to paint a picture to the target user and make someone feel that this is the PERFECT app for them. Who is that? Travelers? Partiers? Geocachers? Bored folks on weekend? I'd start with very narrow positioning and expand from there.
The screenshot is you greatest weapon for communication and the first thing people will look at. It's a busy map with a lot of colorful pins. What are the pins? What do the colors mean? What do the icons mean?
Logo / title -> Link to app store Titles for copy -> Link to app store Big awesome image of app on phone -> link to app store.
Pick the best benefit of the app and highlight that.
For me I'd go with something like.
Impress them with a hidden gem.Wanderous helps you find great places, right next door.
(I actually have no idea what kinds of places wanderous will help me find, etc, I'm assuming it finds great restaurants or something)
Then go buy a hires stock photo of a great example of a place someone might discover on Wanderous along with two smiling people enjoying themselves, multiply the image by 20% black and put your text on top in white along with the image of the app.
The sign up should state that due to demand everyone will have to wait for an account and to reserve their spot they should put in their email, else they'll have to wait even longer to find great places.
I'd recommend focusing on making a really good first screenshot that is representative of what your app does while piquing interest, and figure out a way to get as many blogs/news sources to cover your app release as possible. After that, figure out what kind of searches within the iTune store your app can actually rank for and target those specific keyword combinations. Good luck!
P.S.: Since you're in San Francisco, do you have the Planet Granite Rock Climbing Gym as one of your points of interest?
THEN GO BE A ROCK STAR and happy shipping!
Here's a free one. There's a lot of others too. Just search for "Free App Wordpress Themes" to find some others:
Also, I like the "treasure map" phrasing, makes it sound romantic and interesting! Maybe you can work that a little more thematically into the design? Rather than simple white box, it could be on a scroll, or maybe the background could be a bed of gold coins. Something like that. (Again, not a designer, so take those suggestions with a grain of salt...)
Is there a social element on the app? Can you share your tours? Share your logs? I think that people would like to know that!
What is a "gem"? Who are the people that decide whether a place is a gem or not? Are they restaurants? Sights? Strip clubs?
I also think the 100% free for a limited time is confusing. Is it going to be 50% free later? I would revise the wording there...
I would also improve the design a bit, and change the background. It would be super cool to have something like a "pirate map" representation of NYC or some popular location in the background.
Hopefully this helps, I wish you good luck with your app!
When would I use it? What would I use it for? Why would I use it instead of any other alternative? Answer those in one or two sentences...
"Wanderous turns trips into adventures by using your friend's recommendations to identify attractions, restaurants and more that you're sure to love."
When: when you take a trip somewhere,What: things to do, place to eat,Why: friend's recommendations make for better picks
I don't know if any of the above applies to Wanderous, but you get the idea...
I would suggest create a great video of the app and put it on the website. You can use one of the After Effects template to create the video (http://bit.ly/TR33cL)It will take you 5 hours to learn After Effects and make the video. Or you can hire someone to make the video. But its going to be really worth the effort.
Also if this is your official landing page for the app, I would do something much larger. Add more screenshots and detail on what the app does...you have to lure people in and convince them they should waste 5 minutes of their time installing your app.
Otherwise, cool idea if it hasn't already been done ;)
Also, a little border-radius on the container might make the app come across as more friendly.
They have good advice on there. From a copy and screenshot perspective I think the major points have been covered.
One thing you might want to check is if user has entered a email address or not when you ask for email address to notify.
You're making a reasonable wage assuming a below average cost of living.
Here in the UK a recent law came into force where temporary workers have to be paid the same as colleagues in the same role after 12 weeks. They should also get the same performance related bonuses too.
It's worth checking if your company need to pay your agency a fee if you were to join the company as a perm employee.
In 2007 I earned about 1.300 Euros net (no perks) as a programmer (Fachinformatiker Anwendungsentwicklung) in Germany. So if you don't have a university degree, I would assume your pay to be average.
Just my 2 cents