6,740 reputation
1538
bio website
location
age
visits member for 4 years, 2 months
seen 1 hour ago

May
1
reviewed Close Is it just me or is this a baffling tech interview question?
May
1
reviewed Close Chess as a team building exercise for software developers
May
1
reviewed Close How to build full modular app
May
1
reviewed Close Out of all the projects out there, what is a good example to learn from?
May
1
reviewed Close Learning a new concept - write from scratch or use frameworks?
May
1
reviewed Close Offer limited feature in app
May
1
reviewed Close Best practices in managing nuget repositories
May
1
reviewed Close Reading from html page that needs cookies passed and form data
May
1
comment Reading from html page that needs cookies passed and form data
we're not rentacoders here, and especially for screen scraping/content stealing ideas.
May
1
reviewed Close Learning on the Fly
May
1
reviewed Close Want to learn one of those NoSQL databases, looking for advice on which one to check out
May
1
reviewed Close Simple REST API calls using Spring?
May
1
reviewed Close Should I be paid for time spent learning a framework?
May
1
reviewed Close what gets testers invested in the releases they test?
May
1
comment GPL question : web application using Imagick and GhostScript => Which would be the final licence?
the best (and likely only) way to ensure you're not pulled into a GPL morass is to ensure that you don't have any GPL dependencies anywhere at all.
Apr
27
comment Is it always a good idea to divide large classes into smaller ones?
@Zibbobz don't refactor unless it's required by your assignment (iow, it's explicitly your task or you're working on a problem involving the code you want to refactor directly and refactoring will save time on your task). Unless you're the person setting the budgets and tasks it's not up to you to decide that refactoring should be done. You can of course let your team lead or whomever is responsible know that in your opinion refactoring would be a good idea and they can then consider it for the future.
Apr
27
comment I want to explain why the specification must not be changed during development period
another reason for not changing the specs, which is also paradoxically a reason for changing them, is legal requirements. Many pieces of software deal with that. As long as the laws they have to content with don't change, those requirements are static. As soon as they change, the requirements change. And that is completely out of the hands of the development team or their customers (unless those customers are the people who're enacting those laws directly, which is exceedingly rare).
Apr
25
reviewed Reviewed Should I consider uncertain future requirement while development?
Apr
25
reviewed No Action Needed Role-based REST API?
Apr
25
reviewed Close Worth of Algorithm Challenges and event?