Hi while facing an interview one of the questions was
"Did you create a Prototype"?
Now I had worked with 2 projects that involved the entire SDLC.
I said:
Prototype Design – Created in the Preliminary Design Phase; expands the Conceptual Use Case Model to the Implementation Use Case Model. It identifies the Actors and provides a Description of each use case in this subsystem or package.
I tried explaining them the above and they were not satisfied.
Can anyone tell me what is this Prototype vis-a-vis a Coldfusion project is?
"Prototype" has no special meaning in the ColdFusion world. Since it seems they mean "Do you build working demos" and your answer was "yes" I don't understand why they would not have been satisfied unless they are playing semantic games.
Perhaps, it is possible there was a communication error and your potential employer was refering to the Prototype JavaScript Framework: http://www.prototypejs.org/?
Related
I'm currently working on a simple scroll website with nothing really difficult (I could almost use plain html/css/javascript but it's a bit of practicing and I will maybe add a blog). And as it is simple I was wondering how to do it properly with Django.
So here is my question, I have a homepage template that is actually the website and I don't really get how I split my different part in different apps.
For exemple I have a contact form, do I need to split it in another app and then include it in the basic template ? I want to add a galery with image in a database, do I create an app for that ?
And the other question that goes along is how do I code an app that is not returning httpresponse but just html to put it in another template and do I still need views ? I would like to do a bit like a standard form in django where you do :
form.as_p or form.as_table
so maybe:
galery.as_slideshow
So my questions are quite novice and open but someone could give me some reading to get going, I would be really happy !
This is a question a lot of people struggle with and it seems like there are a lot of varying opinions out there.
I've found that the best way to really determine the appropriate answer for each case is to really distill the feature into individual requirements and group them by feature sets while keeping an eye out for additional uses outside of the project actively being worked on.
There is nothing which says you can't build your project to include a single app containing all of the modules you would need. Doing so seems like it would make your development easier initially right? So, the question to ask then is "What if I want to reuse (insert feature set here) in another unrelated project a year from now after I've already forgotten about the weird stuff I did to make it work originally?". Asking yourself that question forces you to think about your features in a much broader context and I think 99% of the time you will realize that a "Contact Form" requirement can actually become quite complex and really should be split up into at least one separate app (i.e. User Creation, Profile Management, Email Subscription, etc...)
Here is a link to a video about this very topic which I found to be useful in figuring out my way through this question:
https://www.youtube.com/watch?v=A-S0tqpPga4
I know this is not really a hard-line answer to your question but I hope it helps point you in the right direction.
I don't know much about web development, so probably this question will sound exceptionally clueless...
Anyway, I'm starting out with Django. I figure that by now there must be fairly standard Django patterns for "canonical" website types, e.g., "a blog", "a forum", "a store", "a wiki", "an issue tracker", etc. I.e., off-the-shelf, "base" implementations (using Django) that, with a modicum of customization, would be adequate for most users requiring a website of such types.
By this I mean that, for example, most forums could be passably implemented by just customizing a relatively small number of parameters in the "canonical" Django-based forum. Likewise for the other website "types" ("blog", "issue tracker", etc.).
(I would like to call these prototypes something like "website templates", but in this context the term "template" is already taken. But really, this is all I'm talking about: "templates" for entire Django-based implementations of various website "types".)
Is there such a collection of "Django prototypes"?
Thanks!
IMHO
http://www.djangopackages.com/ as "main" place for packages
and
https://docs.djangoproject.com/en/dev/misc/design-philosophies/ as main philosophi for django devs
And prefer not thinking about any blocks of code like "template".
Read some code, get idea from it, then write own code. Try to avoid copy-paste strategy :)
And don't forgot about python pep
I have heard that somewhere # web I'll be able to find good C++ example of Mediator working with GUI components. But I menaged to find only that GoF sample or things from sorcemaking and similar that aren't helpful to me.
So... do you know where that mentioned GUI sample can be found?
Sorry for that kind of question, but that can be useful for others too.
How about this one: http://www.andypatterns.com/index.php/design_patterns/model_gui_mediator_pattern/. It appears the author is applying the pattern specifically to the 'view' part of the GUI functionality (as opposed to the data modeling behind it).
Not sure if that's what you were looking for...
I am looking for a good ldap library on Django, that would allow me to manage my ldap server :
adding, modifying, deleting entries
for groups, users, and all kind of objects
The library django-ldapdb looked promising, it offers a Model base class that can be used to declare ldap objects in a Django fashion (which is what we ideally want), however we've had some bugs with it, and furthermore it seems like it is not maintained any more.
Does somebody know a good library that could do the trick ? Otherwise I guess I'll just try to improve and debug django-ldapdb ...
Thanks !
sebpiq, you say you applied "one or two fixes" to django-ldapdb, would you care to share them? So far django-ldapdb meets my needs, but I'd be happy to integrate any fixes you might have.
When using ldapdb to query ldap with more results than the server allows instead of getting the partial list (of say the first 500 users) I get SIZELIMIT_EXCEEDED exception. Trying to change the code to catch that exception resulted in an empty result objects.
Anyone else had that problem?
I fixed that problem by changing the search_s function to use search_ext and read the results one by one until the exception happens.
http://www.python-ldap.org/doc/html/index.html
The beauty of Django is that you can use any python module within your application.
There is also django-auth-ldap which claims
LDAP configuration can be as simple as a single distinguished name template, but there are many rich options for working with User objects, groups, and permissions.
Actually, I have found out that with one or two fixes, django-ldapdb is a pretty good library. The only bad point is that it is not very actively maintained... I will use it anyways, because it is the best solution I have found.
I am new to Redmine and I'd like to see if there is a good way to relate requirements (as stated by a product manager) to issues in Redmine. To me it seems that a low impact way to do it would be to define a requirement tracker and then add a custom field with a list of links to feature tickets.
I have tried doing this but cannot figure out how to add a link within a custom field text box.
So I guess I have a general question and a specific question,
General) Is there a recognised recipe in the Redmine community to achieve a linkage from a requirement to a list of features or issues?
Specific) Can I create a link to another issue within an issue field?
I think the answer to both questions is to use the built-in mechanism to link issues - it's called related issues.
Once an issue is created, you can add link to an other issue and indicate the type of relation (related to, blocks, precedes, etc.)
To separate requirements and features by means of a different tracker seems good to me, expecially if you'd like to apply different permissions or workflows.
See also the redmine manual about related issues, and an example of an issue with related issues http://www.redmine.org/issues/337
EDIT: More recently, subtasks have been added to redmine. They may be interesting to use in a scenario where a feature (issue) is implemented by means of different steps (=subtasks, like designing, programming, documentation,...) and/or by different persons (for example designer, programmer, ...).