Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I have taken over a large project at work that requires a lot of TLC to get it into a manageable state. The whys and hows of this situation don't really matter at this point.
I was thinking I could use some of the concepts of IT Service Management to rein in this project. It has no coding standards, no change management, no issue tracking, and no build process to speak of. Everything is done by hand in Explorer with issues added to a Word document as the help desk receives them.
What kind of formal process would you use to address this situation?
Have you considered ITIL? It has a formalized structure for some of the areas that you’re dealing with, such as application management, change management, and incident management. It’s a formal process with supporting documentation and certifications.
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 months ago.
Improve this question
Is it a wrong manner to start writing a NodeJS application using REST architecture, then try to use GraphQL or gRPC approaches in some parts or completely rewrite some or whole the application in the future?
The reason for doing this is previous experience and coding speed in REST APIs. But at the other hand it's kinda a big microservices project and should support millions of users.
GraphQL is not going to help you scale, quite the opposite in many cases. GraphQL is an optimization (in some cases) but mostly for developer productivity, but there is a complexity cost.
Generally I would suggest to steer away from this optimization unless you have a clear understanding of what you're solving for. REST is a good 'default choice' because it's well understood, requires little tooling and is pretty universal.
Once you are further into your project and you find that you have (ideally measurable) challenges, you're in a much better place to decide to use a more specialized paradigm (gRPC/graphql) and why, but it doesn't sound like you're there yet.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 6 years ago.
Improve this question
I know how to build a site. But I don't know how to save it from a hacker.
You can spend ages on this, but assuming you're starting from scratch, I'd go with the following:
Read your framework/language security guide. For example if you're writing the web app in PHP/Symfony, read https://symfony.com/doc/current/book/security.html and https://secure.php.net/manual/en/security.php (this should be short and easy application of best practices / tweaking known settings)
Read anything relevant on OWASP. It may be hard to do all of it, but some sections to point out are: Top 10 web issues, Development guide, Cheat sheets.
Keep applying what you learned and read more :)
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 10 months ago.
Improve this question
When it comes to these principles like architecture and Infrastructure how would you describe them? The actual meaning and in development where its used. So for example is it like infrastructure is the actual website and architecture is the plans or so called blue prints (UML) in the background?
Infrastructure is a word used for the underlying components that support the operation of something. In your example, you said a "web site" - so things like load balancers, web servers, database servers, and the operating systems that run those servers would be included in the infrastructure. This can go more granular, to include the details of the data centers that the servers operate in. [power generators, cooling, etc.]
You are correct in that architecture is use to speak of the "blue prints", or the design of something. UML, which you mentioned, is one way to express and visualize a design. It tries to answer questions like: What are the components? What are the relationships between the components? What do they do, and not do?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
I'm launching a startup web site, what i would like to know is how to start with that, i mean is better to use invitations first of all?
Then how to send invitations and to who?
How can i plan invitations? Which are best practices?
Does anyone is passed from this step with his own site?
Any experience on here?
thanks
Whether you create a beta version of the site first is completely up to you.
It really depends what type of website you're planning to make. Beta's are obviously a good way to gain feedback on your website and its functionality before releasing to everyone. Thus, allowing you to make improvements/fix bugs before everyone uses the site.
In terms of actually getting users for the beta, it's very much a case of marketing your website and its existence well (through social media, advertising etc.), and then providing some kind of 'sign up for the beta' page. You could then close registration for the beta once you have enough users, and devise some method of gaining feedback from users.
I haven't personally created a beta myself, but if I was to do it, I would do the above.
Hope that's of some help.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 9 years ago.
Improve this question
I am investigating the feasibility of setting up a discussion forum / message board in my company to enable knowledge sharing etc.
What are the steps involved in implementing such a solution?
I would definitely recommend a Wiki - we've used Mindtouch internally for a number of years and have also posted all of our documentation externally on a wiki.
The steps will depend on what technology you already have in place and what kind of shop you are. If you have SharePoint (WSS 3.0 or MOSS 2007), then you already have blog, wiki and discussion group functionality built in. Not the best in the world, but it's there.
A shop that uses more open source tools is less likely to find SharePoint compelling. ;-)
Instead of (or maybe in addition to) a discussion forum, I would recommend a wiki server. This way you can have different howtos, lists, documentation, etc available and the important things will tend to stay up to date. We have one in our department and it is quite useful (if only people would log in when editing...).
I was not involved in setting it up, so I cannot give any details on that, but it is based on mediawiki.