Whenever you finish writing a new package/library/bundle in any language what you do next until you put it in action either for the open-source community or your company apps?!
I mean once you finish writing it what do you do next, how do you do the testing, do you put it in an actual project or a clean project to test it and see it in action how it works or you just rely on the unit tests you write for it or what exactly?
Top comments (7)
Hi Ahmad!
What do you mean? What to do in the time between the library is complete and when it's published?
I mean once you finish writing it what do you do next, how do you do the testing, do you put it in an actual project or a clean project to test it and see it in action how it works or you just rely on the unit tests you write for it or what exactly?
I think I know what you mean. You write unit tests for everything you see a need for. You share it with the world. Slowly, maybe even quickly people will take notice and start contributing. It's not necessary that people will start using it in production right away
If it's an app also you could do think about having automated end to end testing and if it's a library too, by building demo apps that use the library, even basic ones :)
Thank you guys, the question I asked as I got it in Uber interview before that was a simple problem-solving question and after implemented the code, he asked me what you will do if this code gonna be a package and you need to put it in production or make it available for people in the company to start using it. What I said exactly as you guys suggested unit testing, try it out with demo apps, apply A\B testing on the demo app or the bundle itself that is configured to expect the usage of that package and some other long talk happened :D.
But in the end I got rejected for that question saying that I didn't answer that question as they expect so I was OMG f**k it.
It's hard to know what they meant if they didn't give you feedback. Did they give you any context? Maybe they meant stress testing or load testing, maybe the meant fuzzing and so on. Lots of big companies have standardized questions and answers they expect or they just were looking to trick you. You'll probably never know unfortunately. Sorry the interview didn't lead to an offer.
No, they didn't elaborate more even after I asked for more details.
But yes it is fine I was just wondering what exactly they wanted to hear or what even they do inside. Maybe I will ask them that question next time :D.