The budget is tiny: a little over one million USD annually for ~200 projects, or around $5-6k per project. Running an inexpensive operation is key to avoiding being excessively dependent on sponsors.
The ASF is incredibly valuable and there's no question that there are potential sponsors out there would would be willing to give a lot more money in exchange for more direct influence. Being a tax-deductible 501(c)(3) -- as opposed to a 501(c)(6) -- in fact makes it easier to avoid that influence because it is so cumbersome for a 501(c)(3) to receive and spend direct donations without running afoul of the IRS.
The downside is that the ASF doesn't have a zillion dollars to blow on marketing and so people undervalue it.
* Grameen Foundation USA: http://www.grameenfoundation.org/
* Kiva: http://www.kiva.org/
* Code for America: http://codeforamerica.org/
I've done work for all of those plus Wikipedia and Mozilla; glad to answer questions.
It's definitely possible to start tech non-profits, but there's a big question of how to fund them. Personally, I favor models like Kiva, where revenue is closely tied to actual value delivered because that creates a core feedback loop that helps keep people focused.
The more common model, though, is pursuing grants, which I think is currently inimical to good startup practices. It's a very long, expensive fundraising cycle and the way you get money is by promising to do very specific things. But if you're doing anything really innovative, then those promises shackle you to a plan that is months or years out of date.
Our slogan is 'Technology for Social Justice'
Our annual report is public as we are a registered not-for-profit & charitable organisation. When I started at Infoxchange 3 years ago our financial turnover was around $3M/yr (after 25 years), we are now looking at around $10M. This growth is for a number of reasons but mainly through a mix of technological improvements (paying down tech debt and technical modernisation) and very positive feedback / recognition from clients that have spread us through word of mouth, advocacy groups etc... We're also winning quite a number of awards including this years 'Google Impact Challenge' amongst others.
I do apologise for our awfully dated website which is shortly to be replaced early next month, while it may look like we perhaps do not practise what we preach so to speak I can assure you that it is, by quite some considerable distance the most neglected part of the org and as you can probably guess I'm quite embarrassed of it: https://www.infoxchange.net.au/resources/annual-reports
Around a year ago I gave a brief talk around my/our journey there over the past few years, while a lot of the content was spoken you can find the slides on my blog here: https://smcleod.net/talk-24-months/
If you have any questions I'll do my best to answer them for you.
plos.org archive.org and eff.org are additional direct nonprofit (charities, 501(c)(3) in the US) examples. EFF is an advocacy org but they do more interesting tech work than the vast majority of startups.
Another interesting category maybe worth considering are for profits with normal for profit governance but some non-fuzzy public benefit aspect at the core of their business. In the context of tech a free-software-only for-profit like Red Hat maybe.
You probably want to put a finer point on "social impact".
Check out Fast Forward, an accelerator focusing exclusively on non-profit tech startups: https://www.ffwd.org . Y Combinator now also has a track for non-profits - https://www.ycombinator.com/nonprofits/ and for example funded https://watsi.org/ .
Feel free to ask questions. I volunteered at Grameen Foundation and have been exploring this space for a while.
- An entity that drives resources towards solving a particular problem?
- An entity that does the above and is self-sustaining?
- An entity which reduces the size/scope/people impacted by a particular problem?
- An entity which solves the particular problem once and for all? (And then dissolves after, I assume.)
Our charity partners love us since we give them an immediate ROI that's way better than traditional channels. Our users love us since we help them create real world impact that they can be immensely proud of.
Our team is made of devs, designers, PMs and non-profit veterans. I'd feel incomplete if I didn't shamelessly mention that we're hiring:https://boards.greenhouse.io/changeheroes/jobs/125117
For more research you could check out groups like the Case Foundation, Tumml (Julie and Clara that run the accelerator are super nice and I think have a great grasp/direction on social impact investing), Wharton Social Impact Initiative (https://socialimpact.wharton.upenn.edu/) is part of the Wharton School of Business and has done some great research in this area, and while he has not written much about social impact investing even Jason Calacanis has been involved in investing in social impact companies (i.e. HandUp).
I'll ping their cofounders, I'm sure one of them will jump in to answer questions if you'd like.
>> Established in 2008, Samasource is a non-profit business that connects marginalized women and youth to dignified work via the Internet
>> Launched in 2012, Samahope is the first crowdfunding platform for medical treatments.
>> Samaschool (previously SamaUSA) prepares people for success in the digital economy.
If only non-profits work with your problem, then ask them what tech solutions they need. In some cases, they don't need technology at all, but rather funding or government support.
I would avoid "feeling good" non-profits that spend grands on noble but futile activities. Most useful solutions are those that people buy, instead of getting for free.
I'd be glad to point at non-profits in the area you're interested in.
Check out B-Corps (For benefit corporations). Read Amory Lovins' Natural Capitalism.
"A non-profit organization is an organization that uses its surplus revenues to further achieve its purpose or mission, rather than distributing its surplus income to the organization's shareholders (or equivalents) as profit or dividends."
There are plenty of ways to raise capital that allow an organization to abide by such restrictions. A nonprofit is not strictly restricted on who it can hire or what products it can make or services it can offer. So, unless your definition of "successful" requires that you distribute surplus revenues to shareholders, then yes, it is possible to start a successful tech non-profit.
You can pay your employees massive salaries. You can raise massive amounts of debt to fund your expansion. You can employ ruthless business practices.
Many businesses do not distribute capital to shareholders until well after the business has matured, reasoning that the capital is better used growing the business. Meaning, the investors have a long investment horizon. Meaning, their initial smaller amount, often accompanied by additional rounds of funding, was enough to get a successful business going. Capital sources can include endowments, public and private grants, or payment for goods and services.
Personally, I believe that non-profits have gotten a bad wrap. There are some amazing companies out there that do not aim to return money to shareholders, that prioritize their product, their cause, or their customers. I'd highly, highly recommend checking out YouTube videos about Patagonia and it's founder, along these lines. You can even mis-use non-profit status. Many people don't realize that IKEA is a non-profit, and that the profits are extracted from its activities through some tax and legal loopholes.
Typically, the relevant issues are related to the raising of capital. But think about how that often turns out. Many founders raising outside capital lose control of their company or see their share diluted, that is if the company is even successful. And if it is, and they maintain control and their share of ownership, it could be a long time before there is any surplus revenue.
On the flip side, you can start a private company and be help accountable to no one but yourself. You can raise all different sorts of capital. And you can determine what social / environmental impact you make. You pretty much only lose the tax breaks.
So you see, it's really a matter of capital management, not of business management. You can reduce your options for raising capital from the get go, or you can choose to deal with taxes and possibly even make those go away, like GE magically does. But there are no impediments to you delivering a product or service to make the sort of impact you are hoping to make.
2) Content. If your app is about fashion, make sure you have gorgeous fashion on your website. I see two half-assed selfies on your website. Get professional photos that make me think: YES I want to look like this. YES I want to look at photos of people like this. And don't fill your blog with SEO crap. If you can't write well, post pretty photos instead.
3) No ads. Ignore all advise about buying ads or hiring an SEO agency. Doing that stuff right is really hard, and if you can't do it yourself you won't be able to afford the people who can do it right. It's really easy to spend all your money on ineffective advertisement. You can advertise after you have some initial traction, but advertising wont help you get a broken product off the ground.
Having built and launched a successful go to market strategy here are my tips for you. Ultimately because it seems like you're bootstrapping and have limited funds since it's a side project, you want to aim for a scalable strategy that will give you a CPI that makes sense for your monetization path (ROI).
Note: I'm not even sure you're ready to go to market so ill assume you are.
1) Influencer Marketing: Do manual reach out and negotiations or hire someone with the network/connections who can help you with this. Since you're in the fashion niche there are tons of instgram/youtube influencers that would promote your app for a fee.
2) Content distribution: Get bloggers or guest posts up about your app on sites/blogs that have massive traffic and engagement.
3) PR: If you're running this as a business then there beeds to be a need in the market for your product that you must reach out to journalists and tell...ie your story. You can use HARO as well.
4) Viral coefficient: Make sure this is engineered into your funnel otherwise you're missing out on reaching critical mass and will steuggle to acquire users sustainably.
If you have questions let me know!
Hope this helps.
It's okay to fail after you've tried everything, but if you quit now to build something new you're just aspiring to get back to this point equally unprepared to take your idea from launch to success.
Working backwards from Sam's thesis, it seems the most logical first step would be to get your app in front of as many "real" people as possible. Show it to your friends, family, coworkers, your mailman, your mechanic, the dude sitting beside you at Starbucks. My 2 cents anyways...
Coming to your site, it was pretty clear how I could interact with the site, but not why I should bother. It might be obvious to you, since you've worked on it, but it's not to a casual browser. Compare to https://www.gotinder.com/ which works hard to clearly sell the benefit of the service.
Name:Thechicnatural with 833,449 subscribers
Name:Wendyslookbook with 633,000 subscribers
Name: Beautybyjj with 506,000 subscribers and many more..
In their profile, they have business email addresses to contact them. They will charge you a small fee and will mention your app and also include a link to your site for their subscribers to check out.
Tip: Often times, they give away a prize to their subscribers after reaching x amount of subscribers. So find a way to spin that to get their subscribers to your app and maybe get the prize through your site when the time comes?. For the example, the subscribers can sign up on your site, show their fashion sense and then win the prize of that youtuber that has reached their milestone?. Figure it out and it should help. All the best.
Your problem here is your going after a rather broad group of people. That's usually pretty nigh impossible unless you got megabucks behinds you. I'd narrow it somewhat and tackle them first. I don't know anything about fashion so I can't help you there.
But if it were, say, an app for people who were buying motorobikes I might first create an app that helped people of a particular brand (indeed, model within a brand) of motorbike as they often congregate and chat amongst themselves quite nicely. Once I completely killed with that brand, I might consider building the same tool for another other brand of motorcycle. After killing a bunch of brands only then would I try to go after the motorcycle market in general.
Your earliest users are most likely to be ones who are already doing activities with regards to fashion -- perhaps check out /r/malefashionadvice on reddit and search for other online interest communities. I would bet there are instagram, pinterest and twitter communities around fashion.
Measure the success of your campaigns across channels, and the retention of users across each. You should decide if you plan to grow users by being 'viral' (fast growth, but user's don't stay long) or 'sticky' (slower growth, longer usage).
Any users you get and keep are likely to be the best advocates and already know similar users, so empower/incentivize them to invite the friends they think would be interested -- ideally in some way that is natural to the product. In the ideal case, the product is so good, they will immediately want to tell their friends who would be interested.
Finding an effective and repeatable marketing strategy can require as much thought and effort as the product itself.
Go to Meetups and talk about it whenever possible.
Move your location to the epicenter of whatever industry you want to build traction in. Fashion oriented -- try New York.
I know of people that have raised money (read $50 investors) for the sole purpose of getting peoples attention.
I'm sure these are not new, but they are routinely passed over.
To be frank, getting eyeballs is by far THE HARDEST PART to launching a business, so explore all avenues.
Personally, I wouldn't use it because, based off of your site, it looks like I either get yays or nays on my outfit. A nay on its own will only make me feel bad about myself, but it won't help me improve.
I'd be more into an app where I could get, "No!! Try a different tie. Bright orange looks horrible with that suit."
Of course, the downside is that then I'd be less tempted to rate others - just judging my behaviour on this site, I'd usually rather just up/down vote than explain why!
But I do think that you are missing a trick: you are pushing the wrong end of the proposition.
If this does fly it will fly not because you are offering a free appraisal of what users are wearing but more because you are giving users the opportunity to flex their fashionista status.
What you might want to do is create a panel of informed and preferably well known gurus to critique the uploaded selfies.
Go the X-factor for style route:
Your top tier of acknowledged experts critique the style 'performances'.
The 'judges' reactions to the style performances might be good or bad in the general but often enough your going to get a performance that has the potential to go viral: fb, buzzfeed, national press whatever.
Follow through on the personal aspect of these stories and create compelling narratives:
"OMG I totally took on board what (take in name of top stylis at Looks Good) told me about my style. I did what they told me and landed my dream date/job/ etc."
If you have any promotional cash to spend use it to recruit a panel of top stylists. Or if your bold enough take the roles on yourselves and spend the money on clothes/ haircuts.
In short feed awesome stories to the major players with big audiences and hope that a few stick. Obviously always point the origin of the story straight back to the app.
PS: Final Para: A simple yes or no from you could prevent them from making a mistake or give them encouragement they need.
Should read: A simple yes or no from you could prevent them from making a mistake or give them the encouragement they need.
We don't have a category for mobile apps yet, but I suspect a lot of our users would love this product. We could find a way to make it fit.
Contact me at firstname.lastname@example.org if you're interested in learning more
1. Why did you create this app and how is it different than your competitors? Do you know what your competitors metrics are?
Taking a quick look at your app, it looks very similar to The Hunt. So I would research who the hunts customers are and go after them. I would also research (i.e. App Annie) The Hunts downloads and revenue numbers and keywords.
2. App Store is very difficult for discovery. How do you envision users finding your app? Is it intent driven or not?
This will help you refine the marketing channel. If you want to buy ads, be very precise and use it to learn more. For example, spend $1-$3 per day and use it to figure out search terms, demographics, intent or not, etc. At this stage you are doing customer research and not performance marketing.
3. Seeding content.
You're going to have to do a lot of work to make it not seem like a dead zone. So invest tons of time on content creation.
4. Once you have the content, expose it. Look into deep links, referrals, etc. You can connect SEO efforts but it will take time to start ranking and you'll have to have a plan and think long term.
Take some time and describe exactly what you think your earliest adopters have in common. These are people who you think will get extraordinary value from your app, the ones who will become incredibly devoted because you are just what they have been looking for, because you are solving a problem they have tried solving for themselves.
Now that you have a notion about who your customer is, go talk to them. Book 30 minute interviews with as many of these people you can. Before you meet them, be vague; just say you're thinking of work on a fashion-oriented app. Start out with very broad questions, so you can get to know them as individuals. Ask about behaviors around fashion. Ask them about problems they regularly experience. Ask them about apps they use, and how they use them in fashion-related ways. Only at the end can you ask them if they have the particular problem you have in mind or show them your solution.
If you do ~25 interviews, you should start to find out a) whether your imagined customer exists, b) who they are, and c) whether some of them feel substantial pain around the problem you are trying to solve. Odds are you will discover you need to pursue a different problem or a different solution. But that's ok; most startups have that experience at some point.
When you find the right problem and solution and are delivering a lot of value to passionate early adopters, then you can start worrying about other users. At that point you'll probably know your audience well enough to have plenty of ideas, but if not, return to interviews. Talk to people about the apps they use, how they learned about them, and what make them go to the trouble of getting started. You'll come up with a bunch of strategies that you can try out on your audience.
On a side note, be sure that your questionnaire is balanced and doesn't lead respondents to answer in the way that you want them to. Remember: The goal is to improve your product, not to pat yourself on the back. Don't let your ego get the better of you.
Next, you need a good product idea. My immediate impression is this probably doesn't qualify.
But since it's built, I'd do things like see if you can get exposure through Pinterest, Facebook, Instagram etc. Try to find some trendsetters willing to use and talk about the product. Seed it to a college or high school.
You'll likely need to offer something tantalizing in return...
That being said, we got into the business because an app the company had invented was too hard to market, so we started marketing apps. There are a lot of techniques in this space -- some low budget, some high(er) budget. Happy to chat if you like. Feel free to dm me @jtm on twitter.
Marketing is easy.
I've come to conclude that no tool for this will ever satisfy everybody's needs perfectly. Part of that is that everyone has different priorities for their task tracking tool. And frankly, some of those priorities are directly contradictory. What's trackable and detailed to a project manager who lives in the task tracker is heavyweight and clunky to an engineer who sees it as a bookkeeping annoyance. My personal todo.txt is exactly me-focused and only changes when I want it to, but it scales to exactly one engineer.
I think you just have to pick something and use it. Changing tools just adds friction and costs you familiarity. Ideally, the people who have to interact with it the most choose the best tool for them.
Currently using Pivotal Tracker after coming from a Jira shop, and it's awful. Others seem to like it, but it's too simplistic for my taste. Even something as simple as "A blocks B" isn't possible, and seems to be by design.
For a larger project I use GitHub issues with tags.
It could be fun to have a global online poll to see who's using what, to know which tools are the most popular, just out of curiosity.
That said, our use case is explicitly tracking backlog work that needs to get done. My philosophy is that any issue tracker that is treated as a database and that disassociates items from assignments will decay into a pile of rot almost immediately. Especially bugs. Don't put anything into the database that does not represent work to be done within the next few days.
So we use Asana as a collaboration tool that brings together stakeholders, information and assets. Typical workflow: Account manager brings issue to attention of project manager, who brings it to attention of developer, who does the work, sends it back so customer can be notified. Task goes away. Another typical workflow is an actual project, with steps to complete and a launch timeline.
The only way, in my experience, to manage bugs is to give them to a project manager. The PM triages: Forget or hide the unimportant ones away in a drawer, and fix the important ones ASAP. Bugs that linger aren't important enough to consider. Sometimes everyone is too busy and the bugs are important but not critical; schedule a single day of the week when everyone puts aside their main work and plow through the bug backlog. We call them "bug days".
For new features, use something else, like Google Docs. But it will rot, too. It's better to do whiteboard sessions that are turn into discrete tasks and discrete projects.
Microsoft Outlook contacts: put the word todo in the comments field. Any notes also in comments. Everything is searchable. Common items come up together on search by keywords.
A todo folder in the file system full of text files backed by a Git repository. This is kind of the equivalent of microsoft outlook contacts for me.
Flags on emails.
Most of the time, as a dev working on a client codebase, i do just fine with github issues.
But for everything else, if you're like me and have a lot of different things to capture and track, I haven't found anything that cuts it. So I'm close to launching a data platform for when you want to have your own workflows, analytics, monitoring and reporting of... anything. So you could use it to get an email every day of your open todos, or to nag you until you workout, or just simply act as a place to keep bits of information.
For instance, I'm the sole developer of my web backend, iOS and android platformy thing and while android studio has good TODO: Integration sublime and Xcode require plugins, it would be awesome to have something that looks at all three repositories and tells me where i have scribbled a TODO: somewhere; or even just for comparing the different method names of my app across platforms -
Perhaps someone knows of some such tool already out there that does this?
I've also heard this argument if you're running a product, though I'm not sure how on board I am with it: don't record user requests. The important ones will be requested enough that you'll remember it.
For short term, post-it notes and legal pads. There's something for me about having those TODO's constantly in my face. I always get them done. And it feels so good to crumple that ball of paper and throw it into the bin. Each sticky is 5-30 minutes of work.
For longer term/planning: Trello. When I'm ready to tackle something, I convert the Trello card into a sticky note, archive the card, and get to work!
Sometimes when I am feeling super unproductive/lazy, and have a buildup of sticky notes, I'll convert all those sticky notes into a neat 1 page legal pad page - handwritten, with checkboxes. By the time I'm done doing converting (and crumpling up all those sticky notes!) I feel rejuvenated enough to work on that second pass.
I love throwing stuff away. When I am SUPER unproductive, I'll tear away the blank part of the sticky note and throw that away.
All issues also get scope and type labels. Type signifying bug, feature, hotfix, etc. Scope saying what piece of the software it's for.
We also use milestones for releases. Each release gets a codename, and that codename is used for the milestone and all backlog and in-progress issues are applied to the release it's meant for.
Right now there's no UI for anything, but we're building internal tools that create a visual of this whole system for us.
It's got a good command line interface, a built-in web interface, it's self-contained, and the model is easy to understand. It's simple enough that I can use it as a replacement for RCS for personal stuff (like a LaTeX document) but it scales to large projects too (it's used by SQLite and Tcl/Tk, for example).
It's also trustworthy, with a solid, portable, and well-tested code basenot a surprise since it was originally authored by D. Richard Hipp. I have no clue why it isn't more popular.
I'm a long-term JIRA user (and even somewhat evangelist). There are probably many much more "modern" issue trackers over there, but JIRA worked extremely well for me for many years. There are a few big problems with JIRA, though (field-level security and limited issue hierarchy).
For my OS-projects I've found GitHub issues to be more than sufficient. That's what I'd call clean and simple.
We use Zendesk to track bugs. It's nice because of its assignment features. That said, I find it terrible about everything else.
Feature requests are currently in UserVoice, however we're about to move over to Aha.io instead as we use that for product roadmapping and it's easier to move a request right into the plan and then push into rally (we use rally instead of jira for sprint planning)
More details in http://xn.pinkhamster.net/download/New_Process_and_Tools.pdf
Been mulling around making a vim plugin like vim-flake to put the todos into the quickfix window on :w
It takes the usual kanban approach that Jira and Trello use, but is contained in a no-nonsense html5 friendly, mobile friendly website. No complaints, free to start, and premium features aren't costly if you need them.
Trello (other kanban tools) - very flexible.Gitlab. Free, open-source, host it yourself.
Jira is a powerful tool, it's also very complicated and expensive. You don't want to blindly jump into that commitment.
has just enough fields, features, and customization to be useful but not overwhelming.
For a team, it's probably not what you need though.
For the free software projects on the web I'm familiar with, many use Bugzilla to deal with issues and feature requests. Also popular, although a little less so, seems to be Trac. They are all over the web - http://bugzilla.redhat.com is one example for Bugzilla, https://core.trac.wordpress.org/tickets/latest an example for Trac.
I don't want to work in Turkey anymore and want to start a new life. a whole new page. want to get rid of everything about this place, my wife, my partners and what's left about my life.
so i ask to you, fellow developers. what should i do, where to start? I looked up a lot of job ads but never applied one. i even don't know what to say or what will they ask ? these are the problems of being an introvert person. i don't know what to write in cover letters.
I'm working as a developer since 2006, before that i was a designer. I need a web site to show my portfolio and I do it of my own. I really like to code and started studying on programming on my own.
I prefer working as backend developer building interesting and complex custom web apps using Django/Flask frameworks and I have professional experience in front end development and linux server administration(configuring web-server, deploying apps)
I don't want to turn this post into a job research letter to list my skills ect. but i really need one.
I know it's a long post, thanks you for reading this far. Happy coding.
These people prefer not to care about people that were not so lucky with their country of birth.
This is me ever since I had my kids. But to achieve this, I am working towards building a life where I have enough financial freedom that I can choose to spend my time however I want. If I want 2 months off, I should be able to take that without worrying about asking a boss or taking unpaid leave.
So I enjoy working hard at building the life that I envision.
No, really, hear me out. The industry has such a high turnover rate, talent and technicians alike. The barrier to entry is very low, almost non existent. This means the market place is constantly flooded with poor quality product.
I have studied and worked in the movie industry, so I have a bit of inside knowledge about the craft. Certainly the same things annoy me that annoy everyone else with bad porn, shit lighting, over acting, bad sound, etc.
Now, don't get me wrong sometimes poor quality work will do, but I'm going on about the search for good stuff.
Maybe it's the synergy of titillation and craft that lights up my happy circuits. But I think the real key here is as soon as I've ingested the work in question, well, the thrill is gone. I won't make any excuses, that's just how the ol' libido runs.
I think what the quote is really getting at is this: can you find a way to be paid to do something you enjoy doing anyway?
Few years ago for me it was mutexes, RAII and similar things. This year it's changing country of living.
What is the following rhyme about?
Thirty days has September,
April, June and no wonder,
All the rest have peanut butter,
Except my grandmother who has a little red tricycle.
A. Family relationships B. Calendar C. Food D. Exercise
Not sure how long it'd stay viable though.
I've had good experience with both Manjaro (Arch-based) and OpenSUSE, though not on a laptop. One thing I have found important is to use a distro which has a good selection of third-party packages. AUR is perhaps to absolute best out there for this, OBS is also pretty good.
Honestly, for the pc I'm currently building, I'll be running W10, with a few linux VMs for hobbies. One of the biggest irritants of every single linux distro I've tried is the f'ing screen going to sleep while watching netflix/youtube/web videos of any sort. I've spent many hours googling for a solution to this, apparently it's one of the great technical issues of our era.
Love me some tiling windows.
Anyway, AskUbuntu on StackExchange is the killer feature for me. Beats a wiki or a forum all day everyday.
I ran Arch awhile ago, got tired of things breaking, then switched to, in series, Linux Mint, Kubuntu, Ubuntu, and then finally Xubuntu, which I actually like the look of. I'm considering switching to NixOS with AwesomeWM at some point, but everything's working pretty well for me under Xubuntu right now.
I use Debian on a daily basis for servers, but I haven't bothered with a Linux desktop since about 2005.
Arch has support for Flash, and despite its rolling-release nature, I've found it to be reasonably stable for a casual desktop user. Arch and i3wm probably also fit your methodology with regards to being "thin", "bare bones", and minimal. You may want to try Arch out, even if you don't end up using i3wm.
I don't have any experience with others, so this might not be an opinion you're very interested in, but I thought I'd add my 2 cents.
I've used Debian for more than fifteen years and I wouldn't go back, at least on desktop. These new distros made me terribly lazy.
In that order. Ubuntu - getting things done. Arch - satisfying the desire for bleeding edge.
The US been in recovery since 2010. First to recover was corporate profits thanks to downsizing and low interest rates. Consequently, the S&P went on a tear [2010-2014]. With corporate profits recovering, companies could start re-hiring and unemployment dropped [2010-2015]. Now that employment is back in healthy territory and the stock market is back where it should be, Americans are feeling a positive wealth effect, so next to recover is real estate. Still juiced by low interest rates, real estate prices will continue to rise significantly in the [2014-2016] period.
I'd be on the lookout for a recession once this real estate cycle plays out, maybe in the [2017-2019] time frame. By then, interest rates should return to the low end of their historic range .
 http://data.bls.gov/timeseries/LNS14000000 http://money.cnn.com/2015/08/11/real_estate/median-home-pric... http://mortgage-x.com/trends.htm
This bubble is of historic proportions and of a way bigger concern that the shape of overvalued startups.
It uses Python's Twisted framework. You don't need to use this for your development, but I would recommend working through and understanding the tutorial. Once you get the concepts, you'll be able to apply them to other libraries/concepts.
Aside from improved efficiency, the idea of giving unemployed persons fair jobs is also a worthwhile consideration. An innovation that allowed disabled persons to work more effectively is another idea. The main reason I focus on efficiency here is because, at least when not monopolised, it is virtually guaranteed to improve the quality of life for humans as a whole. Simply doubling someone's income does not have a guaranteed positive effect on society.
Berlin is a friendly city with a lot of foreigners from EU, Eastern Europe, Middle East, etc so you won't feel like a stranger here.
I'm not from Berlin but my impression is that it's an interesting city to work and live. Has highest concentration of the startup scene in Germany. Cost of living is lower than in other places like Frankfurt or Munich, but salaries are also somewhat lower.
So the whole thing really depends on your personal situation, your goals and the offer that you have. If you tell more about yourself you might get a better advice.
You also want to start learning about VCs, and what it takes to make it through their assessment rounds.
I'm a big python fan, and if you think your library really is better than Kiwi, and will stay that way for years to come, then go for it.
Seriously, after reading his wiki page, he obviously seems like one hell of an intelligent person. But something else struck me, he's been married since 1979 to the same person who is also a professor of physics, plus they have kids that all appear to have done quite well. I'd be more curious to see how they balanced their life and were successful in raising kids that have passion and are doing well, at least from their basic bios.
Everyone probably asks him physics questions, but chatting with him about the everyday things to me could be way more interesting, and wouldn't feel interviewee. But that may just be me. I would want to ask him what he feels is his best accomplishment professionally and personally. That is always interesting to hear.
Ask him about his interests beside physics. Philosophy. Art. Whatever.
But most of all, don't pester him. If he seems receptive to those "big questions", great! If not, just do normal smalltalk.
Don't worry about it -- be yourself.
Also what you need is a remote desktop app. There are quite a few nowadays (from "Remote Desktop" in Windows, to TeamViewer, VNC or etc.). A quite good list is in wikipedia: https://en.wikipedia.org/wiki/Comparison_of_remote_desktop_s... .
Edit: more info on the Wii U game pad link. http://www.polygon.com/2012/11/16/3653294/wii-u-range-test-g...
Plus, the laptop would lose 90% of its mobility advantage, as it would always have to be in the (network-) vicinity of a desktop.
Actually, a Chromebook is kind of like that - a browser only.
(thin client, fat client, thin client - the more things change the more they stay the same...)
Or even using a Motorola LAPDOCK + Smartphone with remote-control app
See Motorola Lapdock: http://www.amazon.com/gp/product/B004M17D62/
There's no need to be so rude. Telling someone they are being "flat-out dumb" is not appropriate discourse on HN.
I heard a great analogy recently that a startup is basically like consulting for a very specific use case of customers in the early days. One of the trickiest thing in building a product users love is figuring out what feedback is fluff and what is real. The best way to determine this is to first see if there are common patterns in the feedback your are getting. If yes, that's a good sign. Next is to see if you can get a few of these users to pay for it.
If they'll pay for it before it's even built, you know it's a real problem. If it's something they will commit to pay for (on paper) once it's built, that's still good but be more cautious. If you get excuses or any other non-comital response, then it's more than likely not something worth building right now.
One cautionary note here is to be careful not to go down a rabbit hole for one customer. You don't want to start building features that are just applicable to one specific customer early on unless they are paying you a significant amount of money. The ideal scenario for building a software product is to leverage feature requests that multiple users/customer have toward the long-term objectives of the product.
num: command not found tr: Illegal byte sequence
Could you funnel bug reports through a form that requires fields to be filled out before submission? If the report is still seriously lacking, use a canned reply asking for more information and close the report if this isn't given. Also, could you require the bug reporter to write step-by-step what QA must do to replicate?
Sounds like you answered your own question, resign move on then watch that ship burn, there is a limit to how much change a person could influence.
Sorry I know it is negative to think of it this way but its really hard to find a team that follows a process you enjoy. If you love testing and think that its the right way find a team that does that, don't waste time trying to convince people with a different mind set.
The problem is between now and then in addition to hoping the pendulum doesn't swing too far the other direction.
Process doesn't have to slow everything down, my guess is you have one of two types of management or maybe both feeding off each other. A, you have young new founders/management that doesn't have experience with good process so they think all process just gets in the way. B, you have some experienced management that only came from or experienced heavy overbearing development processes.
The fact they have hired any type of QA means they do want improvement, but just are failing to see how to get it there. You will always find that QA requires some hand holding, but in the right situation it shouldn't be taking up the majority of your time.
Depending on what your current role is and what you desire to do and whether you like it there all affects what you can do and how to approach it. If you really love it there but are frustrated you can still try and help things get better. Process can be as simple as starting a daily standup on the QA issues and go over them. But to keep the fear down over the "process", don't make it formal yet, just get people together and say hey lets chat about X and Y and try and save us all some time. And just start doing it, don't ask for permission, don't say it is a process. You can influence how things work by influencing the people doing the work regardless of whom they work for etc. You can start small and do little things like this, and when you start seeing results and say you start getting to code 20% more of the time then celebrate that with an email to the group. By doing that you are telling them wow look at how much more productive I have become, oh yea, its from some changes in how we are working. See what I am getting at? Also, you could try another idea of getting 2-3 of the devs together and agreeing that you will each take one week of the month and handle training QA how to test the resolved defects for that week. It also provides a second pair of eyes on defects and cross trains people into other fixes. Or suggest your management hire a development intern for this type of work.
I am not blowing smoke, I have done this more then once. As a consultant, many times I have been asked to come in and fix things, but I am immediately seen as the outsider and people don't want their processes (or lack thereof) to change etc. So instead you have to be creative in getting the teams to buy into the changes without making it seem like you are creating any bad roadblocks etc. And celebrating little wins is usually really helpful. BTW -- doing it the grassroots way takes a lot longer then having someone in management sponsoring the change or demanding it, but honestly, I think the grassroots team way usually sticks better over time.
No, we're not going to prevent and/or stone-wall encryption just so a connection with an average 7+ second latency works marginally better.
As an aside - this satellite connection is one of the worst ones I've seen. Old satellite connections are supposed to be on average about 1 second of latency (and that's considered bad).
You may wish to get Opera browser and utilise their "Turbo" service (it is an optimising proxy, it compresses the page content, removing several round-trips, etc). Should have smooth out the issues a little bit.
By your description it sounds like your current location is temporary (which is fortunate ;P) but that you'll revisit this location in the future, so it might be worth your while to explore different UDP data transfer algorithms once you're back with sane Internet, then test said techniques when you revisit where you are now.
Best case scenario, you might be able to tunnel TCP over some kind of "best effort" UDP retry algorithm that overcomes a proportion of the losses; it should be possible (while complicated) to implement a more intelligent packet-loss mitigation system that handles significantly broken connections better than TCP does.
A far simpler system might be a VT100-esque text terminal running on top of a best-effort transfer layer like those described above. The only problem with this method would be the input latency, although it may fare better than a browser overall (!).
Also, I'm not sure if it's relevant (my understanding of networking is sketchy), but I find it amusing that 188.8.131.52/0's description is "Zerolag Communications" xD (http://bgp.he.net/net/184.108.40.206/21)