Dec 18, 2012

CEO 101: Stop calling people ‘your people’

Just today I saw another CEO saying on Facebook ‘I have amazing developers’. I said to myself, that’s it. I decided to rant about it. Because I’ve been introduced to people like ‘here is MY CTO’ (‘my’ emphasized), I heard CEO’s say ‘I give my developers x,y,z’ as if they are … whatever, you know what I mean.

It bugs me. It bugs me now I am a CEO, it bugged me when I was a CTO, was a developer. It’s wrong, it’s lame, stop doing it. It’s not the same as saying my wife, my children, my cat. It’s bad.

Here is why:
1) People are humans, they are not objects that you own.

2) CEO is a given title, ‘developer’ is earned. Show respect. Just because you could raise money doesn’t mean you have authority over others (nothing means that anyway). Unless you are Steve Jobs, just shut up. To real people, CEO means nothing. It almost is as lame as saying “I’m an entrepreneur”.

3) CEO is not a title for a maker, it’s a management title. When there is nothing to manage, it means nothing. Think about it like this, if your company is less than 5 people, you are a rock band, CEO MUST play an instrument (or sing). A rock band doesn’t need a CEO, so stop calling yourself that. Call yourself with what you do (btw, if you can’t, fire yourself, free ‘your people’).

4) If your company is more than 50, then you are a philarmonic orchestra, and CEO is a maestro. Don’t forget, without Paganini playing that violin, your title means nothing. Paganini, however, is always Paganini. Show respect, don’t call him “your guy”.

Point is, calling other people ‘your people’ is just wrong, condescending, impolite and dumb. We’re not living in medieval times, nor under manorial system, and sorry to break it to you, you are not a king.

I propose,
- My employees – My teammates
- My developers – Developers that I work with
- My company – Our company (think about it, is it really yours?)
- My developer – My teammate
- I manage – I help
- I have 10 developers in my team – I help a team of 10 developers

As a CEO, this is the only phrase you keep intact,
- I ~~make sure~~ help things get done, on time.

If you do that long enough, people will show you the respect you are trying to self claim. Be patient, talk less, and do your job – it will come to you.

Devrim
CEO of Koding

ps: Paganini Caprice No.24 (thanks Bradford)

Dec 11, 2012

Travel the world, and talk about Koding!

Devrim Yasar Home 3 Comments

Yes, we want our users to be our voice. We will buy you flight tickets, conference tickets, book you a hotel room, you can attend to any conference you want, and geek out with developers.

Why? Koding, is a new product, is a new community. But if you are reading this, you probably know that Koding doesn’t belong to us. It belongs to our users, to our community. We developers, are merely makers. We make the product, whereas you make it happen.

Usually, companies hire people with job posts. We try not to. We believe in being genuine, being honest in what we say and what we do.

Usually, other companies hire people to spread their message. They hire a professional whose ‘job’ is to pretend they love the product, go to twitter write lame messages, offer lame apologies, go check facebook like counts, craft crap newsletters and get paid. We say, scrape that. Why would we pay someone who will only learn our product just because we pay? We have so many users that are willing to contribute. We much rather pay our users, help them travel around, have fun and create much better voice for Koding.

You can attend to one or two conferences, or more. You know we have awesome users that build amazing stuff with Koding you can try to organize them, create a meetup around your area or you want to attend to some meetup in another city. You can propose many things, just make sure it makes sense, it’s cool and real, then let us know. You see, our point is offering you to do what you love doing and you get to travel and have fun! :)

So here is the deal, Devrim and I sat down, and thought about the following,

1) Send us what conference you want to attend. This can be anywhere in the world.
2) Send us what you made with Koding, and what you want to talk about.
3) Tell us your experience in public speaking (your previous talks, blog posts) This could be in a language we don’t speak. We will find translators.

We will evaluate and decide if we like the idea of you representing Koding, totally on your own. Better prepared you are, you have higher chances of being accepted. Yes, we will send you t-shirts, and other material to spread around.

And if you are really good, we keep accepting your proposals, we will promote you to be a Developer Evangelist, read more about that here: http://developer-evangelism.com/

Please drop us a note at community@koding.com this will go to Peter (Hi! I’m Peter), he just joined Koding as a Developer Advocate, and will coordinate this.

Talk soon!

Aug 28, 2012

Freelance Developers, you are the future, don’t mess it up.

Devrim Yasar Uncategorized 13 Comments

Future is definitely you. If you are a freelancer, you see the signs all around you. You have a computer, internet connection, cool projects online – well you’re good to go.

Not so fast. Just listen to me for a second. We built Koding while Sinan was in Germany, and I was in New York. Freelancing all the way. Our next team member joined from Kiev, then from Connecticut, then from Portland, then from Poland, Russia and Turkey and so on, and the trend continues.

I want to share with you our ‘best practices’ and our experience working with others, remotely. Here is the list:

1- Don't treat it like it's your hobby. It's your job. Have a set schedule, let the others know when you will be online, become a reliable team member early on. Let everyone feel that you care, and you're there when you're needed. Say hi when you come, say bye before you leave, allow your team members to ask questions, and check the status of your work.


2- It's no longer hours game. If you punch the clock, you lose. Unless you're working for something you don't really care about (you shouldn't do that by the way), count your hours and don't count your hours. Here is what I mean; try to work 8 hours a day. Not more, not less. Your team members will respect you for that. Then work more when needed, when you really want to finish something. 
3- Never count extra hours off from your next days work. You can't work 24 hours a day and not work the next 2 days. Nobody hires you for that. However, if you worked your ass off, never asked anything back, your work was very useful (you weren't just being stubborn on something nobody gave a damn), but company doesn't give you extra pay or paid day off when you need it, stop working for them.
4- Don't work 16 hours, and not show up the next day. Not cool. Immature. You impressed no one, made your mom sad, your spouse angry.
5- Don't work 20 hours every day. You prove you're a robot that makes everybody else feel bad. If you really want to do that, do it in private, go offline, work, but don't tell anyone. You can't sustain that anyway, so better, don't do it at all.
6- Be reliable, stable, show up, find problems, and fix them.
7- Never ask "what do I do next?" if you do this in a row, you're out. By asking that question, you make yourself second class citizen. First, you're making someone work to make your to-do list, nobody is your secretary. Second, if you can't see that there is a barbecue, steak, and people waiting - turn around, you're facing the wrong way. Serve those people. That's why you're hired. Otherwise why would you be sitting there?
8- Find at least 3 things that you can do next, ask "I think we need to fix X,Y,Z - which should I do next?". Be open for option T. Finish every job perfectly, ship it yourself if you can. Prove you can take responsibility from start to finish. Never ever say "Oh, I thought that was this other person's job" because if you do, you're out. If it is indeed another person's job, your job is not to sleep on that excuse, your job is to get that person to do his job so that you can finish yours. Don't take no for an answer when it comes to shipping your products, it will cost you, your job.
9- Take weekends off, I've heard it many times "Oh I will work on Saturday/Sunday to get this done". No. If you constantly are needing to get stuff done in the weekends, you're not doing your job well. Just don't work. It's healthy. And it will help you better discipline yourself, get stuff done on time. If you really really want to work, do it in private. Never brag loudly about what a workaholic you are. Ask permission to do that. "Guys, is it ok I do this in the weekend?" make sure you're telling your peers that it is an exception, not a suggestion.
10- Sign your work, like Picasso signs his paintings. Make sure it couldn't have been done better (if you had a day to finish it, it's ok if it's hacked together, it still falls under 'it couldn't have been done better'). 
11- Present your work like it's not yours. Accept every kind of critique wholeheartedly. Know when to politely dismiss a comment, when to defend your work, when to accept the critique fully. If you miss one of those traits, or excel at one of them, you're out. Try to balance, if you couldn't, apologize as soon as you can. It's ok. Nobody is perfect, but the ones who acknowledge their weaknesses the fastest, are the winners.
12- Avoid perfection. It will delay you, it will make you look bad, it will make you look incompetent while you're working very hard. Ship quickly. Think in iterations. If first shipment doesn't break the next iteration, it's ok. 
13- Don't ship crap because you did it quick. Nobody likes that. There is a good balance there, by shipping quickly and caring about the quality, you will get there. If you care about just one of those, you will lose.
14- Make sure your workspace is as good as an office environment. It's quiet, your mom doesn't call you in the middle of your day, your friends don't knock on your door to take you out. When in doubt ask this to yourself "Could I do this if I was working at the office?". It took me quite sometime to get my wife used to the fact that I can't "just" take out the trash, or take dishes out of the dishwasher. My working hours are my working hours, they have to be quiet, and uninterrupted. 
15- If you're chatting with a teammate, and a neighbor appears at the door, don't say "neighbor is at the door", say "just a sec, i will be right back". Keep those stuff that can't happen at the office, to yourself. Never give the impression that your workspace is inferior to an office. And make that impression your reality. It will prove that you care.
16- Don't tell your team members that you didn't show up because you had to accomodate a guest, had to visit your mom, or your bathroom blew up. Immediate reaction is, the place you're working is not suitable for the job and you're failing at disciplining yourself. If these things are happening all the time, and you don't show up at the same time everyday (unless agreed otherwise), you're out.
17- Don't think freelancing is less work, because no one is watching you. Don't think you can take a time off in the middle of the day, and come back and do your work later. Don't think you can skip a full day without notice, and say you will compensate that in the weekend. You just earned yourself a bad rep. Now you gotta work harder to clean that up. The fact that nobody is watching you makes it harder for you. Because when your peers lose trust, you can't fix that easily. Also, in the past (or now) just showing up at the office was good enough. You're there between 8am to 5pm, you earn your salary. As a freelancer, don't ship anything in a month, you're out.
18- Nothing beats face to face. Meet your team regularly. At least once, at least some of them. Call on Skype, have a video chat, show your face. If a company is sold for a billion dollars, it's highly unlikely that you get a million if you've never met them. There is magic in working together in the same space. That's why Koding got an office and gathered in SF as soon as it got funded. We started iterating 10x faster. Think of it as, when you get closer, you're connected with a gigabit internet vs dialup. When you're together, you learn faster, you get to know each other. You get to know how they joke around, how they talk and interact. You get to know who is devout, who is libertarian, atheist, political, soccer fan etc. So you don't crack an inappropriate joke, or say stupid stuff that can offend some of your teammates. There is no way that you know any of that without spending time, nobody is going to type those into chat for you.
19- Freelancing doesn't mean you're in your cave. Especially if you are serious about the company you work for. You can't marry without meeting. Try it, and let us know if we're wrong. Freelancing is the future, but we will have to meet each other to get serious. Now, in the future, always. Don't think otherwise, or you lose.

20- Finally, be a linchpin.

Let me know if you have suggestions for this list. I will list startup’s responsibilities in another post, I think we’re good on that one :)

Devrim*
*: I just signed my work

Jul 24, 2012

Welcome to new Koding, the next little thing.

Devrim Yasar Uncategorized 37 Comments

This day, marks an important milestone for us. Scariest moment of a startup where we say “Hi! Here is our product!”. We’re finally ready to share what we’ve built.

I want to take a moment to tell you about what Koding is, and why we’ve built it.

Koding is about writing software in a social, friendly setting. We want to bring people together without an office being a requirement.

We wanted you to share, collaborate, employ, make stuff, have fun and feel you are a part of what you’re working on. Not only code, but sharing what you find interesting, asking questions, finding answers when you need them, pairing up with interesting people, are the things we need to get something done, coding, is just a part of it.

We did all that, because we believe that’s how future will unfold. This project will try to push you to think differently in some ways, ways that you may not feel comfortable at times. It is not just about writing code, it is about thinking how teams and companies will be formed in the future. We will share more, protect less, that’s the idea. Our offices will be our devices that we connect to internet with. Teams will be more dynamic, can grow to 100s of people and shrink back as fast. We will be more inclusive of others, and have core team members that we’ve never met in person. That’s how Koding is started, and we wanted to give you an easier way to do the same for your project.

Most importantly, with Koding, people who can’t afford things, will not feel left out. Future needs all of us. As soon as anyone can get their hands on a browser, they’re good to go. They can find work, help others, or learn new things. In our experience of 50,000 people, expect to see very savvy kids, 10-11 years old, teaching you how to do things better. This very part of this project, kept us going even when things got really tough.

It took us three years to build Koding. We hope it resonates with you, and you find it worthy of sharing. Please give it 5 minutes (more if you can) before reviewing it. What you see today, is just the beginning of our journey. You’re looking at 20 per cent of what we have already planned making. We will share good reviews (negative or positive) from our twitter account, and try to learn from you as much as we can.

Last point. It’s Free and it will stay free. Basic development environment that is enough for anyone to learn, develop and test. If you grow out of that, you want us to give you bigger servers, more resources, then you will be able to buy them from us too.

If we can become this next little thing that we dream of, this little thing that helps people do things better, that we will be remembered by, we will feel accomplished. We will not measure ourselves with monetary valuations, we will measure ourselves by the impact we made.

Thanks for reading, and now go, code, share, and have fun!

Devrim

Jun 27, 2012

We want to date, not hire…

Devrim Yasar Uncategorized 37 Comments

You read it right. We want to date, and find a match. For several months we’re in San Francisco, we tried all conventional methods of finding people that we can work together with, we hired, but couldn’t find our 5th member yet. Let me explain why we want to date, not hire…

Because first of all, Koding team, didn’t come together with hires. Sinan and I first made the first site back in 2009, it was our first attempt to make something totally on our own. Sinan and I, had no money and had no intentions of making money using this thing. We made it for ourselves and for everybody else who was suffering trying to learn stuff, getting lost configuring servers. We launched a version that would work for a few people. When we opened it however, we saw hundreds of people rushing in overnight..

So we realized, we needed help – serious help, much earlier than we thought. Our servers were burning, I literally sat down front of the servers and restarted apache nights in a row. That’s the only thing I could do, recompiling php and apache was something Linus could do, I couldn’t.

Users were coming in, we were so happy – and one day, someone created a Linux Group on Koding, and he sent me a message “do you need help?” I replied in a few seconds, otherwise servers would have crashed before I could hit send. I said “yes, but we’re also broke :(” he replied “who asked for money? :)”. That’s how we met our awesome sysadmin, Aleksey. His english wasn’t perfect, and he was also shy about it, so he never spoke on skype with us, for 2 years, we always chatted. When we got funded, he came to SF, we totally didn’t know how he sounded like. Then we met, I gave a big hug to him. His english was actually much better than he made us think, he just called git “jit” that was it :) He’s still with us, and comes to SF rides his bike. Now I can’t imagine Koding without him.

8 months earlier, when we finally decided to rewrite the whole stack with nodejs and coffeescript. I joined IRC channels, and was asking questions here and there. There I met Chris, his answers were quite awesome. I said to myself, how awesome it’d be if we worked together and I asked him if he could teach me Coffeescript for starters. When I asked about his hourly rate, it was an amount that I couldn’t afford at the time if I was to hire him fulltime. We worked half time for a month anyway, it was probably more than half of my salary, if paid in full. It was so much fun working with him. I went ahead, proposed half of his rate, and all the remainders paid upon funding, that was the best I could do. He generously agreed. I was so happy and grateful. Happy because he loved what we were doing, grateful because not a lot of people would sacrifice that much. I couldn’t be happier.

We worked 8 months with that, and he made Koding possible. Without him – we could never be here with this product. We saw each other in person for the first time after we got funding, he came to New York from Portland, crashed on the couch in our living room for a week, then stayed in Airbnb’s, leaving Milo, his dog, that he loves so much, with his sister. A month later we moved to San Francisco together, he went and picked up Milo and we picked our first office together. I still remember, when we met first time in New York, right after saying hi, I just continued from our last chat on skype and said “hey dude – you know I thought about that graph module, I think we should do … ” he said “wait, this is the first time we see each other :)” my immediate reaction was to correct him “No, don’t we know each other for years?” it took me a second to realize he was right. I said “That’s true”, still trying to comprehend the feeling, how close we got, working every day, doing so much together yet having never met in person.

Chris is definitely the best engineer I’ve ever worked with, and I’ve worked with quite a few. Although Sinan and I co-founded and implemented Kodingen (first version of Koding), Chris now holds the title “Co-founder and Director of Engineering” of Koding. He deserves every letter in that title. He co-founded Koding with us, worked days and nights for Koding to be an amazing product that he’s proud of.

Great things in life happen when people come together for reasons other than money and securities. I know that for sure now. We all enjoy those, but great work is not a result of high paying job. It may be quite the opposite.

I know, there are great people who are out there, who we could make a great match. People that want to make a difference. People with great skills, maybe without a resume, maybe with an awesome resume; feeling conflicted doing what their heart desire vs the next opportunity they have at a big company, feeling conflicted, between pay and making a change, becoming someone vs becoming a cog in a machine.

You may be a great UI/UX guy, an amazing C/C++/Go/Nodejs/Ruby/Java engineer, awesome biz dev guy or a sysadmin. We decided that we won’t make job posts anymore. Because we want to date. We want to love your work, and we want you to love our work back. We want to respect you so much that we will never have to tell you anything about when you come to work, when you leave, what you’re working on. We want to respect you so much that you will know what to do next, and you will do it the best with needing no meetings nor managers, and you will tell others what needs to be done when you feel like it.

We are onto something big, and we are only 4, we all code.. We are very proud of what we built with a small team. We also are not in need of help, but we can use some serious help. Not a noob help, not good intended but no-skills help, serious professional help. Come be our 5th member, come help us, like you would help Nikola Tesla, like you would help Einstein if you met him, just like you would do anything if Steve Jobs wanted you to help him when he was building Apple.

Remember, if they ever needed your help with a blog post like this, at the time they needed your help, they would be just like us, nobody, yet. And you’d be just like yourself, nobody, yet. Faced with a very similar decision. If you postponed your decision, and decide not to help then, they would become who they are, whole world would be on their fingertips. You wouldn’t even hear if they ever needed anything anymore. And you, would have had a few more paychecks, still needing to pay the rent, still dreaming about the decision you always want to make, just a few years older this time.

Right. You couldn’t do it with them, come do it with us. Let’s try to carry their vision forward. Let’s give a 12 year old with a cheap laptop in a far away country a chance to learn programming, and become a developer that we need. Let’s make companies who spend weeks on-boarding their new hires, do that in minutes. Let’s let companies hire outside of their offices as conveniently. Let’s make cloud computing available for masses so 2 years later, you and I can build Siri or Google glass, writing code in the browser, executing it in 1000s of CPUs, with a few bucks we can spare.

We don’t want to impress with lame employee-entertainment. No, we don’t have a ping pong table and we are not ‘sooo much fun’ people. We do amazing work together, and we’re damn proud of it. Our biggest joy is when we release, we drink a few beers and celebrate while watching amazing response we get from our users. We love those moments… For other fun, we do whatever we want, whenever we want. We all know that our purpose is not having fun paintballing each other, our purpose is to build something that world will remember us by. That’s why we came together, that’s what makes us happy. Yet we go, do paintball – it’s fun :)

We know you exist, because our team is a manifestation of that. We know you’re out there, getting bored reading job descriptions, maybe thinking about what you can do on your own, then thinking about your family and your rent that doesn’t let you bet everything you have, and worse, you can’t afford to fail, which is a big part of this game.

Now you have a choice in the middle, a project that provides an environment to 60k developers, serving 40k sites already, 13k people waiting to receive their beta invites to their new site, when they send invites, they see more than 70% of people come and join. An amazing stat that only a few startups can see, and many dream of. Which means that they have proved it, and now with your help, they can go big! Or without your help. Either way. It’s totally up to you.

We brought Koding so far, and we’re continuing our dream happily and so successfully. And the best part, this time we’re not broke, we have plenty of money. It’s just that, we want to know when you ask this question to yourself “I can get a great job, but do i want money, or do i want to make a change?” that your answer is the latter. And if that’s the case, no matter where and who you are, let’s have a date.

Devrim

Use the contact link to reach me, i’m on the other side of it.

Jun 25, 2012

So what’s up? Are we releasing?

Devrim Yasar Uncategorized 6 Comments

Being four people at the office makes this blog stare at you with the same post for so long… Sorry about that.

Let me get to the point quickly, I think this week is our final week in private beta. I just wanted to let you guys know.

We sent 4000 invites saw more than 3500 people come back and tested our site. Everything is close to “go”, not close to “perfect” as we wish to see things, but at the end of the day your emails win. You want to get in, and we will get you in.

We will work on the last quirks, we will close the registrations on Kodingen.com at the end of this month, make user accounts work at new Koding (with kodingen domain, also ability to move their files and databases). After that, we will give every Koding user 3 invites to invite others. The reason we do invites is, we still don’t know if we can hold 10k people or more at once. Invitations allow us to test the system properly, and optimize it without crashing it for others.

Alright, that’s it for now. We’re very excited to finally share what we’ve been building for so long.

Devrim

Apr 5, 2012

Public Beta Update – Opening Soon.

Ryan Goodman Home 25 Comments

“Soon”… Koding will be opened to the public! Why the quotes? Well, if everything had gone according to plan, we would have opened up Koding to the public this week while we were attending JSConf (highly recommended by the way) and everything would have been right with the world. Unfortunately, during some extremely long hours of trying to squash a few last minute bugs and get this thing out to the world, we uncovered a few more super bugs.

We are ok with some bugs… this is a Public “Beta” release after all… but these specific bugs would have led to some non-trivial performance issues had we opened the floodgates and let thousands of you into the app. The thought of performance issue severely affecting a user’s first experience with Koding was just too much to swallow, so we’ve delayed the release just a bit.

As of this morning, we’re hard at work crushing the remaining critical bugs. As long as things go according to plan, we’re estimating that within a couple weeks we’ll be fully opening the doors to the public.

For those of you who have requested access at Koding.com, hang tight. We’ve (slowly) started the process of inviting users who’ve signed up, and we’ll continue until everyone is invited.

Mar 14, 2012

Beta Update: New Features, Wider Beta Coming Soon

Ryan Goodman Home 21 Comments

So, it’s been about two months since we started the Private Beta and we think today is a pretty good day to share an update on what’s new. If you have a short attention span, the post title ↑ pretty much covers it, if not read on to hear about new features, our new blog, and our plans to widen the beta.

More Beta Testers Please!

Up to this point we’ve opened the beta to a small group of existing Kodingen users who expressed interest in testing. In the next few days, we’ll be inviting everyone on that list. Shortly after that we’ll be opening things up to more people. If you’re interested, head over to our preview page and let us know.

New Features, Launching Soon

Two months, thousands of commits, hundreds of bugs squashed and 96 awesome beta testers have gotten us pretty far down the road to launch. When we launched the beta, the system had only about 30% of the features we expect to have when we’re done, so we wanted to make some progress there, but our big focus at the beginning was on system stability & performance bugs that were slowing things down. After getting past the biggest of those bugs, we’ve moved on to getting more of our planned features into the system. For the last month or so the team has been working on our next big feature push.

Enhanced Code Shares

Code shares now allow for easy editing & saving so if you want to use or just tinker with some code someone shares, you just press a button to open it up in your own code editor.

Topics Tags

Topic tags are system-wide tags for you to follow the content that interests you & label your own shared content so it can be discovered by users with similar interests.

Inbox

Inbox is your central place for realtime private conversations & activity notifications.

MongoDB & MySQL Databases

We’ve exposed the ability to add Mongo and MySQL databases to beta users.

This is what beta testers can expect to see really soon. Up next we’ll be working on a new App Catalog, additional content sharing types like Q&A and discussions and some interface enhancements to make things easier, more on that later.

What Else Is New?

New Blog, built on Koding!

Well, if you’re reading this, you’ve found our new, responsively coded blog. New blogs designs may not be that exciting, but we thought this one was worth mentioning because it was installed and customized from start to finish on the Koding Private Beta before we pushed it to production.

New Preview is Live

Yesterday we pushed out a new preview of the app. If you are interested in getting in on the beta or just seeing what the new Koding will look like, head on over to the preview page.

That’s all for now. Going forward you can expect to hear from us a bit more frequently.

Jan 16, 2012

The New Koding. Private Beta Has Begun!

Ryan Goodman Home 46 Comments

We are so excited. For over a year, we’ve been working on a completely new Koding, totally built from scratch. Finally, we are getting close to our first big milestone… We’ve started a limited private beta for some of our most active users with a wider beta to soon follow.

In the beginning, Koding was what you could call a passion project… built because we saw that getting started with development is too hard. Developers have to do way too much work and spend way too much money and time to run their first line of code. Even after that, it’s just too hard to work with others. We had the vision of a future for developers where getting started was easy, and you could work, collaborate and run your apps without jumping through hoops and spending your hard earned money. We realized nothing like this existed, so we decided to create it ourselves.
Read on!

Mar 16, 2011

Sorry we’re delayed

Devrim Yasar Home 49 Comments

Hi Everyone,

We’re receiving no less than a few emails every single day asking about the release, encouraging us to release or being angry about the release :) Thanks a lot.

I’m going to cut this short – there are many reasons, but primary ones,
+ we are trying to achieve multi server backend per uid
+ we are leaving wordpress
+ we are moving to a new stack that holds all apps in one

Stuff we tried that didn’t work,
+ c++ multiserver http/socket communications (4 months/3 developers)
+ cocoa style frontend development (5 months 2 devs – we tried this twice!)
+ pure js/css frontend (4 devs 4 months – those are made for sites, not for apps)
+ golang multiserver http/socket communications (this did work well – but then we liked ours more)

I will write more on those later on a different topic but just to let you know, we have spent 18 months with 5 devs on average on this release.

Two things to take out,
+ first, now we know what works and we are about to finalize our current stack (seriously no changes anymore :))
+ second, Kodingen v1.0 works really REALLY well!

I’m not going to make concrete promises here, because we want to do it good. Also, this is a project that runs with our own savings, we really can’t afford much, expensive developers, or even full time developers are beyond our reach. We gotta do it within our own constraints (and it is fun that way!). But of course we don’t want you to wait any longer. We’re annoyed, excited, frustrated, happy, sad more than anyone, and we want to put an end to that emotional turmoil. Good news is, we’re now testing our new release internally, so it’s live on our screens..

Hopefully we will bring it to your screens very soon!

Cheers!
Devrim

↑

1 2