SoapUI seem like it is too tied down to xml.
does anyone have suggestions?
546 karma · joined July 6, 2011
SoapUI seem like it is too tied down to xml.
does anyone have suggestions?
I am founder and CTO of a startup, and I have hired and grown a few teams. Contact me directly at cto @ nosql dot com.
Some general advice: It is ok to hire individuals remotely, but do not start with time and materials. Pay for work product. Get a lot of quotes and hire multiple people and keep the best Use the full SDLC tools to ensure quality: git, tests, stories, Ui mocks, etc It is ok to choose a cheap database or other core tech, but design the system to be able to change. Using the cloud will be faster and cheaper to start, but more expensive in the long run.
Is the market niche esthetics? They do look nice - maybe this company is trying to be the Apple of heat pumps? Charge more because of looks?
This is a serious question - where is the innovation?
As to refreshing your skills, there are quite a lot of good udemy classes. There are some free videos on YouTube, except I found that the structure of on line learning is better.
As for the idea - why do you ned to tokenize coupons? To make sure that they are limited? What if you create tokens for a coupon and it is not used? Is the value lost forever? How will you get partners to use your APIs? Through an expensive blockchain?
Most importantly - what value does this give to the end user?
please contact me - Altverse@web3.net
no thank you
Maybe the answer is to pay me for my time at a consulting rate.
My definition of lucky is the ability to survive bad events while making the most of good events.
For example, when I was younger, I fell 30 feet and broke my arm. I choose to see this as good luck because some people have died when they fell that far.
this is not scalable