For example, we posted a job for a mid-level front end developer. We got a bunch of resumes from people who just finished a code bootcamp earlier this year, when we specified 3 years of front end development experience as the main requirement. Why does someone who finished a bootcamp 3 months ago and hasn't done any professional work yet thinks they should apply for a mid-level position, is beyond me.
Other candidates apply with 0 development experience - their resume frames them as "project managers" or "Search engine specialist" with no development related prior experience anywhere. I feel I wasted my time everytime I go through one of those.
There is no way to automate it with the systems we worked with. We receive the resume through their interface, it doesn't go directly to our Email and doesn't share the contact details directly.
Honestly, if you'd seen the kind of resumes we received you would not think most candidates put any effort at all. Like another person said here, it looks like most of them are spamming all job listing on those sites.
We used to receive inbound from sites like Ziprecruiter and Indeed. Now I'm using the Stackoverflow Talent service to search for applicants that fit our requirements. I don't start conversations with more than 1 or 2 at the same time, so I don't really need an additional tool to manage them.
> If an applicant takes the time to apply to your posting, why not give them a follow up regardless?
I'm not a hiring manager, but as the CTO I do review a lot of resumes incoming for technical positions we are hiring for.
The vast majority of applicants do not appear to be taking any time at all aside from selecting their resume to upload and clicking submit. It doesn't seem like they even read the job requirements, since 90% of them do not meet the minimal requirements we post. Some of them are not even developers, but they apply for a developer position.
If someone does appear to be relevant and did also include a cover letter relevant to the position, I will respond, regardless if they're a fit or not.
For me the biggest pain is the sheer amount of irrelevant submissions, which makes you numb after a while. This is why I don't believe in job postings anymore and mostly do headhunting.
Unfortunately, that doesn't work with dynamic subdomains (i.e, domains assigned and edited by users). Hopefully they'll change their minds in the future - until then, I'll be paying for a commercial certificate
I've been training in a grappling sport (BJJ) for over 9 years. The advantage a trained person has over an untrained one is massive. Even someone who has been training a few months could easily handle an untrained person without anyone getting hurt.
You can see hundreds of videos out there of police shooting people without apparent just cause - just because they "felt threatened". If they had the confidence they could deal with a physical confrontation if needed, I'm certain the amount of unnecessary shootings would decrease significantly.
The real problem is that most officers have such minimal training and conditioning in hand-to-hand combat combat (specifically, grappling), and as a result they panic and shoot-to-kill much more often than they should, or use excessive force to control a suspect also resulting in unnecessary deaths.
Instead of passing stupid legislation (anyone who's used firearms extensively knows aiming for limbs is not realistic, you have to aim for center-mass), they should work on improving ongoing officer training and conditioning so that officers would feel much more comfortable controlling a suspect without killing them.
We are building a monetization platform for open-source, through dual-licensing and customization / integration services. We are a 10 person team, funded and generating revenue.
We are looking for help with marketing, content and community. You must have experience with software development, either in a technical or managerial role, and a strong understanding of the software development cycle. Compensation is market competitive + equity depending on background and experience.
The article is technically well written, but somewhat uninformed which stems from the author's limited experience and what he sees in popular media.
I thought the top comment below reflected what I have seen in my 10 years in the industry, much better:
"
This is a very well written piece, but it's only covering the frothy tip of a very deep phenomenon. I too am a Rails developer, have been coding professionally for 15 some odd years, and I too find what VCs are chasing nowadays to be mostly time wasting crap. But that's not what software, even web software, is really about right now. It's just the glam side of the game.
The real folks making real things happen are building tools and technologies that literally could not have existed 10 years ago. In my personal experience, I've built integrated web portals that show real-time electricity usage for factories, saving them 10-50 grand a month by lowering usage during peak hours. I've built sales management tools that allowed a 2 man company to scale to a distributed team of dozens. Online rental advertising systems to cut out costly newspapers. Medical order management systems.
It's not glamorous, it doesn't get on TechCrunch or Hacker News, but it's real value, delivered by real professionals. And that, more than the stupid photo sharing cruft, is what's really driving developer salaries.
During the late 90's, the joke/threat was "go away or I will replace you with a very small shell script" - the point being that lots of human work could be automated by a savvy developer. That threat has become a promise, and we (costly) web developers are the ones fulfilling that promise across a huge range of industries." - Rob Morris
It's the only thing we're waiting on to switch to Balanced. We talked to you guys before about that (my co-founder, Adam, from Binpress) and it seemed to be progressing but then it stalled. Looking forward to May 22
Firebug gives you the option to toggle all pseudo states for an element and edit its CSS. IMO Firebug and Chrome's dev tools still lag behind Firebug's.
You're confusing "free" in pricing with "free" in freedom. A free trial creates a completely different type of community than free and open code. GitHub could have just provided a closed binary for free if they wanted to go the Sublime route.
You are correct. Besides, raising x amount of money at y valuation, doesn't mean the company as a whole is worth y. Investors typically get preferred stock, which are worth more. Marc Andreessen had a nice tweet chain about that exact topic yesterday, ending with this one - https://twitter.com/pmarca/status/457017580385873921
Some context needed - who is the target audience? investors? potential hires? users? I would make some modifications to accommodate each. I think the product concept translates well and is easy to understand. Since you focus most of the pitch on it, it seems like a pitch for users.
If you're pitching to investors, a few things need to be sharpened / clarified -
* You say "0 marketing spend" - which most investors will call bullshit on that. Typically, what you really mean is that you spent nothing on ads. Unless you consider your time as worthless, you probably spent quite a bit on marketing. Even if you have the most viral product in the world, you need to kickstart it until it reaches critical mass. Investors want to know that you've given some thought on how to scale that operation (and not that you'll spend 0 on marketing going forward).
* Regarding marketing, you briefly mention that user acquisition is built into the product. You need to elaborate a little bit on that, cause right now it's not clear how that is the case.
* Dates on the x-axis of the user growth graph would be helpful. Did that growth happen mostly after the public launch or during the closed beta? most people would assume the latter unless you tell them otherwise.
* At the end you briefly group together your recruiting needs and fundraising goals. Depending on the audience, I would focus on one. If fundraising interest is the goal of the pitch, put a dedicated slide on that, and move the hiring part to a footnote on the team slide. If it's the reverse, do the opposite.
* I would make the contact details at the end way larger, and move it higher. In addition, it's always good practice to put the name of the company, a tagline and basic contact details in the header of every slide - for people who lost concentration, or want to put a note for themselves before you reach the last slide. Btw, it should be in header and not the footer, because sometimes people's heads obscure the bottom of the deck during presentations (depending on how the seats are arranged). That is also why you should move the contact details at the end higher, just in case.
* Again, investor audience only - add a slide about the market / opportunity size. Especially if you're aiming for a series A round, which typically means venture capital.
Thanks for the explanation, we always appreciate sensible feedback on our messaging and product. We are always looking for ways to get our projects more open and accepted by the traditional open-source community. Our default option when adding new products on the marketplace is GPL + a commercial license (which is the option you mention). Most developers still pick only our own proprietary licenses, since they are worried about people abusing it.
We are also in touch with the OSI for creating a 100% open-source compatible license of our own that could be officially sponsored by them. It's been a slow process, but we hope to get it done in the near future. Our own license was created with the help of copyright lawyer that has dedicated his professional life to supporting and advocating open-source. It is a compromise between closed-source / commercial and fully open-source (what we call "commercial open-source"). For many purposes, it is less restrictive than the GPL (no stipulation on releasing your source if you modify and distribute on other formats), which makes it more attractive to businesses building commercial products (for example, iOS application, which cannot use GPL).
It's interesting how you choose to spin it to fit your narrative. That product has multiple licenses, the one that allows redistribution of the source is this - http://www.binpress.com/license/read/id/1567/app/859
The one you linked to only allows binary distribution. This is how those projects support themselves, by offering tiers of pricing depending on the user needs. We just require that at least one of the licenses allows redistribution of the source. So I'm understanding that by your world-view, Open-Core projects are not open-source? or that open-source can only be used if sanctioned by the OSI? I'm afraid that no one has monopoly on that term. It means different things to different people. We call our products "Commercial open-source", which you can find the usage of which on the web and wikipedia as well. Most projects on GitHub do not have a license, which means they are copyrighted by default. We vet licensing for each project on our site, to make sure there are no copyright or licensing breaches, and provide a range of licensing options to fit the developer POV. Not sure where all the hate is coming from.
Other candidates apply with 0 development experience - their resume frames them as "project managers" or "Search engine specialist" with no development related prior experience anywhere. I feel I wasted my time everytime I go through one of those.