HN user

jags-v

27 karma
Posts1
Comments23
View on HN

The short answer is it depends.

Insights you may gain at YC may help you either pivot or improve the current SaaS you have either from an offering or operational perspective.

Most importantly folow your gut feeling because that's what got you to $8.5k MRR. If there is even a 5% chance to improve your product or increase your revenue or both, you should take it. Define your success metric and proceed accordingly.

Hope this helps you :)

Fabric Group | Australia - Melbourne

At Fabric we bring together a network of consultants and engineers to help solve business problem. We are always on the look out for creative Technologists who are keen to learn on job. We value Object-Oriented and Functional Skills.Our approach leans heavily on devops, agile and lean principles.

Skillsets/Platforms/etc.: C#, Java, JS, AWS/Azure, Python, Node.js, React, Angular

Requirement: 3+ years of programming experience.

Interview process: Take-home coding assignment, Pair programming interview, Technical Interview(s), Leadership

Roles :

We are currently looking for the following roles

    Mobile Developer - Senior and Lead Consultant 
    Full-Stack Developer all levels (Preferred .Net/ Java/ Javascript)
    Software Developers Consultant (Preferred .Net/ Java/Javascript) 1-2 yrs exp
    Quality Analyst Senior and Lead Consultant (Test Automation)
    Business Analyst  1-2 yr exp
https://www.fabricgroup.com.au/

Contact: jagannath(dot)vaikuntham(at)fabricgroup(dot)com(dot)au

Please send email with 'Hacker News' in subject line.

- Raise this issue with the people who decide the pools and pay . The team did everything possible , if not addressed properly , one should not expect them to go above and beyond the norm.

- Communicating to the team that you tried, is not good enough, because that is the least that is expected of you as the mananger ( if sounds rude, i am sorry , not the intention).

Potential Solution :

Making a case to the higher ups , showing them that retaining the great team is cheaper than hiring some one else over a period of 2 to 5 years would be helpful. Show them the impact on delivery of features,etc.

if this did not work, ask why so that , it does not repeat again or you can set expectations saying , this is what you get for what you are paying.

I am assuming , there is no equity involved in these discussions. Equity will change the whole dynamics of this discussion.

Potential Solution # 2:

The rewards need not always be monetary. If you can replace that , with something they want , say sponsoring their Apple WWDC trip or DisneyLand tickets or something , in a way that is not a HR nightmare, would be something to explore. That being said, it is tricky and will not work always.

Cheers.

Cevo | https://cevo.com.au/careers.html | Devops Engineers , Test Automation Engineers | Melbourne , VIC , Australia | Full Time | ONSITE | careers@cevo.com.au or ebony.worth@cevo.com.au | We are looking for some of the most talented technologists in the market who are truly passionate about what they do, all while working on some of the most interesting work with awesome clients.

I do think that any attempt to provide access which is limited & curated should be shouted down , because it is totally disastrous in the long term. There are other business models which are currently in play , which can be considered, such as

- Aircel has free access at a speed of 64kbps (very slow) but still the user has access to the entirety of the internet , not a walled garden.

- There is a different model, where user view an ad on a per day basis and get a certain data limit in return. Mozilla has implemented this. This gives access to entirety of the internet.

I think the question is incomplete(at least I think so).

Its not about automating the UI tests for regression testing,but to ensure that regression testing is effective.Most of the times,this is driven through the UI, which could be flaky.

As the test pyramid paradigm states , having a lot of UI tests, depending on the functionality & complexity could be an anti pattern. Essentially , a lot of the functionality can be tested using by writing unit tests & integration tests and the end to end business use cases should be automated through the UI just to ensure it works.

If it is possible to drive the state of the application using an API or URL, to the target state and then we assert elements to check the UI.

This enables faster feedback and is less flaky.This is how we approached testing in our team.Depending on the objective , we would use Selenium ,JUNit , Cucumber or corresponding ones in a given programming language.