Technical Test – Whether to simplify or not.

I'm about to start a small technical test for a company and currently in two minds regarding architecture.

This example is purely hypothetical to protect the integrity of the test. Let's say the test is to write a REST service for a todo list.

My question relates to architecture and I'm looking for people opinions, my 'pragmatic' approach leads me to think this shouldn't be overly complicated and keep all the code in a single project ie. controller actions calling the ORM to retrieve/update data. However, I'm concerned that actually, the project should reflect what I would do on a large project and therefore introducing multiple projects in order to separate the various aspects of the code seems like perhaps that's the way to go.

Does anyone have any thoughts or experience either way?

submitted by /u/junderhill
[link] [comments]

from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more!


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

Create your website at
Get started
%d bloggers like this:
search previous next tag category expand menu location phone mail time cart zoom edit close