deepthought42

Get started. Starting a company is hard, even good companies can take years before they start to pay off. So get started, do some market research, build something useful, use no-code tools to build an MVP...but most importantly get started.

This might not be what you want to hear, but I honestly think that worrying about accounting is a waste of time given that you are still in the planning phase. My suggestion would be to build the product, get users, and pay an accountant to worry about accounting in the early days.

Thank you for bringing this to my attention! I'll be sure to work on a fix for this over the next few days.

Hey all, I created this service to help front end web developers and QA teams alike to easily create and maintain their user interface tests. I know just how difficult UI tests are to create and maintain and just how much time is spent automating things when you would rather be building your product. With Qanairy, we aim to make the process both as easy as possible so you can focus on the work you really enjoy without sacrificing quality. I would love to hear what everyone thinks of this service.

We have a process that allows you to create test users that can be used for authorization. As the discover runs, the system will capture the forms that it finds and needs you to classify. All you need to do is tell us which forms are login forms and the system will continue discovering tests using the login credentials you provide. If you have a complex site with many different user roles, simply add test users with different roles and Qanairy will use each of them to generate tests.

We use a suite of tools, essentially pivotal for tracking work, trello for tracking user feature requests, heap and mixpanel for tracking usage and funnel progression, botkeeper for bookkeeping along with quickbooks, sentry for tracking errors and segment.io for piping data to 3 party services from our various systems. For user testing we use vempathy, and for market research we use surveymonkey or google surveys.

We recently released a handful of new features that improve the system functionality and accuracy when creating tests and we would love to hear people's thoughts on the service and what the might like to see included in the future.

The new features released include automatically naming the tests, improved accuracy around which elements are actually actionable when creating tests, and reduced test generation time by 10%.

We should be working for all recent browser versions. If you have an ad blocker in your browsers it may be causing the issue. We have had other users report that their ad blockers were preventing them from accessing the service. Would you mind giving it a try again and providing the javascript error if you see it again?

I'm sorry that you experienced this issue. We aren't aware of any issues with 429 status codes. Would you mind providing the browser type and version that you are using?

Congrats on crossing the 1000 users mark! Reetro looks like a really cool tool. There aren't many good retro tools, I'm definitely going to have my team give this a try.

I designed Qanairy to use artificial intelligence and machine learning to automatically generate and maintain user interface tests for online websites and applications. If you have ever been responsible for scripting automated tests for a user interface, you are well aware that the process sucks and maintaining tests is a nightmare that never ends. With Qanairy, our goal is to make UI testing more enjoyable and less time consuming. We are currently in public beta, and we would love feedback on what we can do to improve the service.

When I first started with RL I went through David Silver's course. I still think it's my favorite set of materials aside from "Artificial Intelligence: A modern approach by Russell and Norvig" https://www.youtube.com/playlist?list=PLbWDNovNB5mqFBgq7i3MY...

We use a variety of tools, and often when we add a new tool it's because we review the integrations for segment and discover a service that we can leverage. For a good starter setup though, I really enjoy segment, sentry, mixpanel, and heap.io. We use a few other services, but when it comes to troubleshooting for customers these are our main goto services.

ya, we use a small custom listener to capture the errors and wrap them in a segment track call.

I'm not sure how familiar you are with segment.io, but it's a super easy data piping service. So we use Segment to define all of our events across our stack, front-end, middle-ware, backend and then we just connect segment to sentry using the integration they provide. FWIW, we use segment for all of our data piping needs...errors, interaction tracking, traffic analytics, etc. This way we can not only have the errors show up in sentry for us to review, but we can also review in other services where in an event stream any given user ran into the error for easier debugging.

We pair Sentry with Segment, which makes handling events super easy instead of writing custom code for logging evens.

Starting a company takes time. Customers aren't just going to flock to you because you put a product out. I can't tell you if you should quit or not, but if you want to know why you don't have more paying subscribers, you should try asking your existing subscribers what made them want to pay for your service, what they love about it, and what they would do if it no longer existed. I'm sure somewhere in there you will get some interesting answers that will guide your decision on how to move forward.

The best way to get better at building things is to build more things from scratch. You're last sentence though suggests that maybe you aren't that interested in getting better at building things and instead you want to get better at shipping product, finding market fit and doing the stuff usually associated with starting a business. If that's the case then building more things probably won't help you. Those skills aren't really engineering related. If you want to be better at shipping product for example, then the best way to do that is to get better at planning and to practice regularly deploying your product. Finding market fit requires a lot of talking to people in your target audience and shipping a product that meets those needs.

Essentially, if you want to get better at building things, then simply build more things. if you want to get better at everything else, then step away for your computer, talk to people, make connections, and put your work out there for others to see early and often.

Nikola Tesla as a brilliant engineer and scientist. At one point he was even one of the wealthiest in NY, he didn't get there by being a "loser poser" he got there by making sales after he created his invention. The first installation of AC generators in Niagra falls didn't get there because he accidently fell into it. Make no mistake, Tesla had to be damned good at sales and engineering to get someone to put so much money up and take such a huge risk on Tesla's AC technology. Don't get me wrong, it helped that he had patents, but there was definitely sales involved.

The best way to initiate a project and turn it from an idea into a prototype is to start. It's literally that simple. Building a product is hard, but the only way it's going to happen is if you start. Other than that, the steps are the same as starting anything else. Determine what you think is a good first step to take, then do it. Then pick the next step and do it. Keep doing that until the product exists.

It's hard to say what you might learn from this experience given your explanation. Some things that I would point out, is that there is no such thing as an original idea, however this is such thing as a differentiated idea. If you are building something that someone else already has, then they will win no matter how much money you raise. The other bit I would suggest is that investors like to believe that their investment will provide at least a 10x return. Unfortunately, it's really hard to tell which ideas will go huge and which won't, so they tend to work from a baseline set of metrics such as monthly recurring revenue, users, sales pipeline, go to market strategy, and also verifying that your goals are all reasonable. I'm not sure how much of this applies to you, but I would say that if you really believe that you have something special then keep going. Less than 1% of companies in the US get VC funded, I imagine that the number is even smaller in your area. Don't get discouraged.

I had the distinct displeasure of working in a number of mumps derivatives for my first professional programming job. It's way too easy to write terrible code and even easier to write something that appears to work, but actually doesn't. What's even more terrifying is that these archaic languages still power a significant number of hospitals here in America. Hospitals haven't felt safe ever since.

I think the author got the terminology all wrong. They say don't hire a rockstar but what they mean is don't hire a really talented asshole. I love how they give an example of a talented person, whom for all we know was mis-managed and had all of the work piled on her because management was incapable of hiring a decent team. I'm not sure where the authors perspective comes from, but I've certainly worked on a team where most people couldn't code the simplest of things, and the few of us that were good were pressured to make up the difference and deliver despite the teams shortcomings. In the end the advice is as simple as hire really talented people, but be ready to manage or mentor them in how to manage. Don't hire really talented people that are massive jerks.

I'm in the process of creating an enterprise startup. We haven't locked down a sale just yet due to not having a completed product yet. We have learned that organizations tend to be a bit risk adverse, so no demo means no sale. However we are in discussions with a couple organizations. What I can say is that these discussions have only been possible because of industry connections. I do feel that if it weren't for having worked for these companies in the past or working with the individuals coordinating with their respective companies that we probably wouldn't even have gotten a call back.