LLC Hello World! Technologies (HWdTech LLC) reviewed by CodeFuse Technology

Software Dev for Application Testing Software Firm

Please find under a summary covering project details and feedback. The innate facts are kept as they are, private information is amended.

Introductory information

Introduce your business and what you do there.

CodeFuse Technology offers all types of tech services to our clients via a SaaS-based cloud platform. I’m the CEO.

Desired goal

What challenge were you trying to address with Hello World?

We were struggling for extra resources at the time. We had a number components we wanted to instrument and we were looking to augment our existing outgrowth team with outsourced developers.

Provided solution

What was the aim of their involvement?

We had a series of components that we wanted them to liberate. As a part of our platform, what we wanted was that clients to be able to do is tag tests. Hello World had a tone in how we were going to instrument the tagging mechanism. We got a test screen of how the user can do the tagging and then go athwart to a test scheduling screen where they can schedule those tests based on the tags they select. We sent over a story based component with some acceptance criteria. We left a lot of the user-experience side up to Hello World and they just ran with it. They asked appropriate questions when true and seething seemed to go fairly smoothly.

How many resources have been assigned to your project?

We’ve had two developers working with us at different times. There is a senior developer and a younger developer who come on board almost half way through the last project. From a senior-to-younger point of view, we settled on a process of any younger outgrowth would be reviewed by the senior developer. That seemed to work excellently well. It was a pliant team that we were using, but it seemed to work excellently well with that senior/younger relationship and us coming athwart with as detailed requirements as we could.

What technologies did they use on your project?

Although our platform expands a pliant bit over this, the core technologies they were using were .NET and C#. There was also some SQL Server. The thing that restricted them a bit in provisions of using C# and SQL Server was that our platform is Microsoft Azure based, so there has to be excellently a lot of importance given to the true SQL that is supported by Microsoft Azure. There had to be a blended expertness set of C#, .NET, SQL Server, and Microsoft Azure.

How did you come to work with Hello World?

We establish them originally through the Upwork platform. What stood out to us wasn’t necessarily technical expertness sets. It was more that we find what we’re looking for, not just developers, but marketing increase as well. It is more almost do they prove, do they apprehend the issue, can they fracture it down into pliant components? Can they prepare value almost instrumentations, suggestions, and how long the project might take? A lot of it is just ensuring that any contractor or freelancer that we use has to apprehend the issue. Hello World showed that to us through the colloquy process.

How much have you invested with Hello World?

We are paying the younger developer $25 per hour now. The senior developer was a bit more costly than that. I’m guessing it averaged out at $30 per hour.

What is the status of this engagement?

We began working with them in September 2016. At the instant, the senior developer isn’t occupied with us, owing the major components that we were asking for have been completed. We are using the younger developer for ongoing bug fixes and support.

Results achieved

Could you share any evidence that would prove the productivity, condition of work, or the contact of the engagement?

I ponder that they smite a nice weigh between the freelancers that we’ve used for software outgrowth. It can get very bureaucratic. You can get things down into too much detail and too much process. On the other end of the layer, it’s almost a bit too loose. There is a wide sort of spectrum of how nation access their work. I ponder Hello World struck a nice weigh between apprehending a issue, asking questions when true, not interrupting our business too much with silly questions but asking questions at the right time. Obviously, if there is a big question, you want nation to ask, but you don’t want to have your time wasted with silly questions where it should be just ordinary perception. It was good working with them from that perspective. It minimized hassle for us, but we quiet got a good condition outcome at the end of it. For each component, there was a set of questions to initiate with which tended to be excellently significant questions almost the instrumentation. Then behind that, we had sort of customary check-ins from them see day or see other day so we could see the progress coming along. That all seemed to work excellently well.

There was just a good level of confide that the job was being done well. We would do code reviews internally, and they were doing code reviews between younger and senior developers. Overall, we were very lucky with the overall treatment of each project and it was done without too much undue hassle for us.

What did you find most forcible almost Hello World?

I ponder it was the despatch of apprehending intricate issues. Our platform has been in being for four or five years. There has been a lot of different work done on it and some of it is pretty confused. But generally, the developers got into a piece of code and understood things excellently rapidly. Some of the things we struggled with internally, Hello World could apprehend very fast. There was very pliant unproductive time analyzing legacy code.

Are there any areas Hello World could better?

We have worked with a plethora of different freelancers where the condition has been up and down. Generally speaking, we have been pretty lucky with the condition, interaction, etc. from Hello World. Nothing veritably springs to mind. I don’t ponder that I veritably have any mess-ups or anything like that.