This survey was based on 258 developers responding from the UK. I don't recommend making sweeping generalizable claims about all developers in the world from it.
If you find the content useful there, maybe consider paying the $5/month to get access?
Sounds like you place enough value that it would be worth it to you, and you can feel good knowing you're helping contribute a small way back to the author (who gets small proceeds based on how long you read the article) and supporting one of the leading platforms for an ad-free experience to read interesting content without all the distracting popups.
This! It is market dynamics. If the content isn't worth it to you, don't click the link (or don't read it). If everyone agreed there would be few readers and people would stop posting there.
Personally I avoid Medium links, I find that it isn't worth it to me. But I guess for most people it is
The main counter argument I see is that people aren't aware that viewing their content is painful for many. If that is the case then awareness is good. If authors are intentionally using the paywall so that they can get paid I think that is good! However if they think it is just an easy place to share information then I think it is good that we are asking them to reconsider.
Can you please prioritize stability of your SaaS offering for paying customers? Our dev team and infra gets impacted seemingly every week with github outages, and it especially seems to correlate with delivery of new features. Thanks!
It actually gets a lot better at categorization the more you use it. It has at least some primitive machine learning (possibly rules engine?). Categorize a transaction once and it usually gets it right subsequently.
I started this right after college after reading "Automatic Millionaire" that advocates for "paying yourself first" and automating your finances. Money goes into checking then automated to online savings accounts, one account per purpose (xmas, vacation, kids college, kids sports, big ticket purchase), money goes to 401k/IRA, money goes to stock account. Only bill I need to remember to pay is credit card (although minimum payment is at least made so no late fees), everything else is automated. Only decisions I make are how to rebalance things if I overspend the money left over, which stocks to invest, and periodic rebalancing to make sure things are on track to reach long-term goals. The real savings is "saving me from myself" :)
Just like the chicken and egg, it doesnt matter which comes first, code or test. The key is that both are written, ideally around the same time and part of same changeset. Refactoring posthoc for testability is tricky and often brings to the surface poor software designs in the original implementation - bad coupling, module dependencies, leaky abstractions, etc.
I think there's something to be said for maybe saying test first. I tend to find writing tests second a little harder. If its a big complicated feature, its much harder to go back and try to think of all the test scenarios needed when its finished, there might be an edge case or a semi obscure case that may have been apparent at writing the code but gets missed when looking back and writing tests. But its preference.
There are a ton of SBIR rules so you'll have to be prepared with your accounting system, timekeeping policies for employees and other legal contracting.
First, check your company's eligibility. If you're VC backed then I'm not sure your company is eligible for the SBIR program. I remember there being some proposed changes but I'm not sure they were made official or not regarding VC-funded small businesses. Also be aware that you are granting the government certain rights to the intellectual property that is generated under contract. You can still commercialize based on that IP, but the government has some rights to use of that software.
If you want a general overview of the program I think you can google for the "SBIR Coach" and he has some free online resources that give an overview of the program.
If you're planning to submit a proposal to an RFP, make sure to very carefully read all the instructions in the solicitation regarding formatting and everything.
Many government agencies participate in the SBIR program. Which agency are you considering submitting a proposal for?
Let me know if you have more specific questions. I worked in the SBIR industry for about 8 years.
Eligibility requirements - note the VC ownership issues vary depending on the granting agency - NIH, CDC and Dept of Energy allow majority VC owned small businesses to apply:
https://www.sbir.gov/faqs/eligibility-requirements
In my opinion, the government "march-in" rights are not a significant business concern. Although technically the funding agency has the right the license your IP if you do not effectively commercialize it, in the real world this has never happened:
http://ipinspace.com/2012/04/11/patent-rights-and-obligation...
I agree that a maniacal focus on correct formatting is essential. My spouse had a grant bounced for a font that was 0.5 points too small.
I think comparing feature for feature isn't the right way to understand why Slack is a disruptive innovation.
Often it's an innovation along some other dimension - process, business model, etc. In this case it's Slack's business model and "platform" strategy. Other tools like HipChat were just that, a tool. Slack is a platform in the sense that it enables businesses and developers to leverage and extend the platform, thereby adding additional value to the platform. This leads to so-called "Network Effects" where as more apps are built on the platform, the more valuable the platform and the more likely others will want to build on that platform, etc. in a virtuous cycle.
