Loading...
Answers
MenuDo you feel that transferring code or application development from one developer/team to another is a big pain point and concern for management?
Most developers spend 50%+ of time trying to understand someone else's code and the current way of just figuring it out in debugger or 2 lines of comments is not very efficient. Do you feel this pain point and how did you solve it for your org?
Answers
No, I don't think that transferring code or application development from one developer is a good idea. The reason why I say this is because if the other developer isn't competent enough to do the job then he will create problems for you in the future.
This is what happens when you transfer your code or application development from one developer to another:
If the previous developer created a bug in your code and it's still there, then you can find out only after many months of using your software. So it's better to fix all bugs before giving it to someone else.
Another thing that can happen is that if you give the task of maintaining your code to someone else, then he may not have time as well as interest so he won't be able to maintain it properly and he will end up creating more bugs than necessary which would affect your business badly. So transferring something like that should be avoided unless the developer/team has stopped supporting!
In such case, you shall have proper documentation and processes in place. That being said, I hope this answer helps!
For more information, feel free to book a call.
There's always a learning curve. Yes, it is a pain point and happens all the time. But there are ways to mitigate and make it more productive. I just happened to be on a KT today with my developers (one developer KT'ing to 3 others) and it went quite well. The biggest mistake I see is going straight to the code before understanding the business features, purpose and rationale it was done that wa, in this order.
Will be happy to go on a call and discuss further.
Large scale organisations handle each code change as strictly as an atoms nuclear mutation through PR's, code reviews and multi-staging environments. Specialisation enhances code quality as well as efficiency whilst maintaining high standards and reducing back pressure on lingering tech dept. Technical writers supporting documentations enables engineers to focus on what's important rather than add thoughts on sub-par code.
Therefore, using decentralised teams with experience hierarchy, code reviews & PR's, documentation and monthly audits ensure high quality code maintenance across all scopes. We can discuss more on this over a call
Related Questions
-
I have a great app idea, and I need help bringing it to life.
I'm not sure if this is how you imagine this world to work, but at least according to the order you wrote it "raising funds" was first. In reality it should actually be one of your final steps of the stage you are at right now. It may even come after a year or two! So you have this great app idea, and you're looking for a place to start... Don't! Don't start yet before you decide whether you have what it takes to get into a roller coaster that can ruin your life and make you miserable! Not trying to scare you but I think most people only hear about these great success stories. They have this dream of maybe, possibly, becoming the next big thing... Because they have the best idea for an app... You don't hear about the failures so often. And even if you do, you don't hear about what the founders of these failing startups had to go through. Truth is you are most likely gonna fail. And I'm saying that without even knowing what your idea is. There are so many barriers on your way that even a great product with a great team is likely to fail. Some people would say "I'm not afraid of failing", "It's good to fail cause you learn", "Failing will make me stronger for the next startup". That's somewhat true but it doesn't mean that failing is easy. As oppose to what people sometimes say - you do not want to fail! It's very painful!!! You have to understand what failing in a startup means. You can work your a$s for 2-3 years, have little to no salary, waste other people's money (most likely your friends and family first), lose friends, fight with your partners, your family, your spouse, devote 20 hours a day for your startup all this time, forget about the little and big things you used to enjoy in life, and only then, after debating 100 times whether you should quit or not, you finally decide that it's not gonna work and you've failed. Disappointing your family, your investors, yourself. Trust me it is painful. Are you sure you wanna do this to yourself? If yes, give me a call. I have the experience you need! From idea stage, to proof of concept, to running beta tests, getting millions of millions of users in ways you can't even imagine, creating features and experience that will make these millions of users completely addicted and viral, raise money in a smart way, hire the right people, find a great co-founder, succeed, fail, be persistent, and enjoy the ride! Good luck, RoyRM
-
How can a small offshore development company find companies/software sales people to sell their service in the US/UK?
My company does a lot of consulting with offshore firms who are looking for a way to generate new business, so I hear this question a lot. My first reaction is that you need to totally reverse your mindset when you talk about your own company. You mentioned that you have: a great software developers team, proven track record, passion, real value But, everyone says that. There a 10,000 companies that have those things, so a customer isn't going to notice it. You need to figure out what your company is best at (doesn't have to be technical) and present it as a solution to a specific problem that clients have. Maybe a speciality, or really good project management, really good communications, a special expertise or experience, a personality, experience with a certain type of client.. really anything.. But, there must be some thing that makes your company 'special' otherwise you will be lost in the mix. Don't worry about things like rates, or the fact that you have 'great' developers. Those are generic. Think about why a client would really choose you, and try to build on that! After you understand your company identity, it gets much easier to identify and engage marketing channels because you understand your target.DH
-
What would be a good approach for marketing a software development businesses?
For software development business LinkedIn ads, content marketing and Google Adwords don't work well. The best and most cost effective method is email outreach. Try to find the contacts of key decision makers in Bay Area from your target companies. You want to present yourselves as custom mobile and web development specialists and highlight your core competencies to get an initial call to discuss their mobile strategy or software development needs. Attaching your case studies how you helped other similar businesses and your portfolio can be extremely helpful as well. Try to always focus on the benefits in you pitch that they can get by working with you and point their missed opportunities of not having certain types of software or apps for their business. Clients love that software development companies have not only strong execution but also ideation skills. Hope this helps. If you have any questions I am also available on call for your convenience.AA
-
How do I run a closed beta test for my mobile application? Development will be finished in 3 weeks.
You should try to engage people using social networks, it is easier to spread than email. The conversion rate on emails are low but is still a valid tool for that. Send and email with a simple and objective message that will make people want to try. The best way to have feedback from users is to watch them use the app. You should put them on the hands of everybody that you can and without any instrucions and just watch, don´t even say that the app is yours. Try to do it a lot. If you want feedback from others, you can include the feedback form inside the app and suggest users to answer occasionally. I would also strongly recommend to use a tool as Flurry Analytics. Is the best way to get data from how is the use of the application. Pay attention to those data and be open to change your app a lot, you may need more features or cut some off to make it easier to use. If you need more help please contact me.BS
-
What is the average pre-money valuation of a enterprise/SaaS stat-up that is pre-revenue?
There is no valuation until you sell something. An idea or a company is only worth what its sales are. Once you have your initials sales, sales strategy and forecasting length (ie 9 months from first customer lead to close) then you have a formula for valuation. Valuation for start-ups is generally 3.5 x last years sales model should be the growth factor. When you are looking for investors, you will want to have atleast 9-18 months of SALES, not just pipeline and they will be looking at 5x revenue for a 3-5 year payback.TP
the startups.com platform
Copyright © 2025 Startups.com. All rights reserved.