[HN Gopher] Show HN: Interviewless -A streamlined dev-to-dev fre...
___________________________________________________________________
Show HN: Interviewless -A streamlined dev-to-dev freelancer network
Author : eneuman
Score : 17 points
Date : 2021-09-19 14:03 UTC (8 hours ago)
(HTM) web link (interviewless.com)
(TXT) w3m dump (interviewless.com)
| ilaksh wrote:
| Sounds like something I made called postaspec.com. Was mostly
| ignored and after a week or so I just went on Upwork.
| TriNetra wrote:
| Being a developer while trying to work as a marketer, I see lot
| of possibility of automating data collection and analysis. I'd
| love to see a service that can take precise description of the
| tool I need, and it should get not only developer to build but a
| tester also test that so the tool I get is working without me
| needing to get involved much in discussion. As a client my money
| will go in escrow for posting the project, and as a
| developer/tester, freelancers would stake some amount (say $1) to
| start building the tool. So as to discourage those who don't
| understand the requirements and just do copy paste bidding
| (speaking from personal experience of being both a freelance
| developer and a client for several years).
| 58x14 wrote:
| This is a really cool concept. There's a great crowdsourcing
| paper [1] that I think will really help with your framing. Have
| been studying this space for close to a decade.
|
| Some first-pass thoughts:
|
| - when I click "try to solve demo tasks" I'm presented with a
| loading dialogue, "waiting for a task to work on..." and nothing
| else. Do you think it would be helpful for you to write a few
| demo tasks yourself as some "control tasks" to see how people
| would interact?
|
| - for creating a task, I think it would be useful to specify the
| language / framework - your example is Python, but what if I want
| help on Rust or JS?
|
| - while I can see benefit to hidden tests, if they are validation
| criteria by which the freelancer's output is measured by, could
| this introduce gotchas?
|
| - it's unclear to me whether price and max development time have
| a relation; am I defining a gross price for the task, and a
| maximum time to fulfill, or a max price per minute? I assume the
| former, but it's important to clarify.
|
| - what do you think about a "share to stackoverflow" button or
| something similar?
|
| - I really like the no-nonsense signup flow. Email and that's it.
| Nice.
|
| [1]
| https://www.researchgate.net/publication/320744080_How_to_Ma...
| eneuman wrote:
| Hi Elias here, founder of Interviewless. Here to show an early
| version of a service I'm building, a dev-to-dev freelancer
| network were clients define the validation criteria upfront so a
| freelancer can get started working on the problem, no interview
| process needed.
|
| Hope to hear your feedback :)
| indymike wrote:
| This has little value to me as it will likely take me longer to
| write the unit tests (asserts) than most of the functions I'd ask
| to be written.
|
| If you give me a way to live a documentation link and a register
| for api access link, I could do more meaningful units of work
| using my app's public and private apis.
| kyriakos wrote:
| This is true, in TDD writing the tests before implementing
| something is usually more than half of the work cause it
| requires to figure out how it should work in order to test for
| the edge cases.
| rahimnathwani wrote:
| Maybe we need a service that takes a function, and returns a
| lot of unit tests.
| Bilal_io wrote:
| Test is difficult to be automatically generated. Unit testing
| Shane's when it catches the edge cases, which cannot be
| automated or they're very different. That's why a few teams
| are employing AI to solve this issue.
| rahimnathwani wrote:
| Can AI work better than property-based testing?
|
| https://hypothesis.works/articles/what-is-property-based-
| tes...
| eneuman wrote:
| I get your point and I know there are many kinds of tasks that
| have a similar issue: difficulty of generating a validation
| test ~= solving the issue. That's why I imagine cases where it
| could be easier to have a set of inputs and then compare
| submissions by several freelancers at once (this would be the
| validation criteria). Given than (in my experience) hourly cost
| of a dev in SV > 10 x hourly cost of dev anywhere else, there
| should be still some margin
___________________________________________________________________
(page generated 2021-09-19 23:02 UTC)