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 years ago.
Improve this question
What naming conventions do you use when creating work items in your task/bug tracking tools?
For example:
Do you prefix the items with an area/subject?
How do you begin scenarios/use cases? E.g., "The department manager can..."
How do you make it easier to detect duplicates?
Your project management, bug tracking and time management (if different from the pm tool) should follow the same pattern, no matter what the pattern is. I usually like to do a top down approach: project-application-page (for example: Amazon-Order Entry-Confirmation Page) - if the project/task management, bug and time management all follow the same pattern then you can track tasks to open issues to time spent easily. After the page you enter a short descriptive text of the issue. In the description area, you need to state:
environment (OS/browser)
version being tested
server environment (dev, QA, or production)
the bug (screen captures help greatly)
the expected results (what you expected to happen)
level of issue (show stopper to nice-to-have-but-will-never-get-done)
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 23 days ago.
Improve this question
I store the timezone in the database upon login determined by the users IP address. This works great. The problem is:
Let's say someone logs in with remember me on, and they are in America/Los_Angeles. But then they happen to travel to somewhere else and they're still logged in... The timezone won't update unless they log out and back in
So my question is... What would be best?
Option A: Each request, update timezone in database
Option B: Ask for Timezone on registration (autofill based on IP), and then let the user change their timezone in user settings
Option C: check timezone with every request and if it doesn't match, show a message asking if they want to update their timezone to their current one
The question seems to be concerned more with UserExperience, rather than Laravel implementation.
All the options you mentioned are valid.
Normally for things like this you'd want to consult your users with it, it makes for a better experience, as well as respects the user's right to choose.
I'd recommend option B or C, since they give the user the option. (Useful for cases where someone is using VPN for example, where the timezone can change frequently, but the user wants to work on his own prefered timezone).
But remember, this is more of a preference answer rather than a standard answer.
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 8 years ago.
Improve this question
I am trying to take a look at the status of r7rs large but I cannot find any information
in scheme reports page, etc, just a talk from 2013. I searched around with google without success as well.
Is it still alive?
Where can I find information?
What would be the tentative date?
What is the progress at this point?
Thanks.
You can read about the R7RS process on the R7RS working group wiki. R7RS-large is listed under the "Working Group 2" section of the front page.
In particular, look through the StandardDocket and ConsentDocket sections. Standard docket is for stuff that's under discussion (and eventual voting). Consent docket is for generally-uncontroversial stuff that's likely to get into R7RS-large without having to be voted on.
There is no firm timeline that I am aware of (though I'm not part of the working group and do not speak for them). The standard docket is quite long, though, and they will have to process through most/all of it before you have anything that you can call R7RS-large.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 9 years ago.
Improve this question
The software we are designing allows students to register and participate in different training courses.
When the user logs into the system they get a list of courses they have registered for. They click on the course and then they are redirected to the specific course content.
My question is, what is the best practice upon login if the student is only currently registered for a single course?
Option 1: Just list the single course, but still require the user to click on it before redirecting. Same behavior as if there were multiple courses to select?
Option 2: Upon login, immediately re-direct the user to the specific course content. Save them from having to do the extra click of selecting the course.
Option 3: Open to suggestions...
EDIT: There are no other options available on this page. They register/pay for the courses elsewhere.
Are there any other options on the course selection page other than selecting a course (like registering for another course)? If not, then take them directly to their single course (Option 2). If there are other options, take them to the list and require them to select their course (Option 1).
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 years ago.
Improve this question
How do you manage a massive (60+ pages) design (HTML/CSS) Project? Like what is your workflow? How do you set milestones?
Step 1. Simplify. Find a way to simplify what they're asking for. Often, this won't be apparent until you decompose and prioritize.
Step 2. Decompose. Inside every large project is a series of smaller projects waiting to get out. Break the big job into "sprints" that will build something you can release in a reasonable amount of time. 2-3 weeks per sprint (or less) is a good target.
Step 3. Prioritize. They want something first. Find out what that thing is and build that.
Step 4. Review and see if you can simplify further. Once you've decomposed and prioritized, you may see further opportunities to remove duplication, useless non-features, junk, fluff, bad ideas, and the like.
I recommend creating a work breakdown structure (WBS) to make sure you capture all of the tasks/deliverables required for your project..here's some basic tasks:
- develop a site map
- develop wireframes and mockups - and get client approval
- develop the main page and unique sub pages (assuming most sub pages are similiar in design and functionality, but different in content)
- inventory content needs
- build out primary page and 2-3 sub pages for final review/approval
- complete implementation of site but add content to the sub-pages
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 2 years ago.
Improve this question
Some of the features I think it must include are:
Print Entire Solution
Ability to print line numbers
Proper choice of coding font and size to improve readability
Nice Header Information
Ability to print regions collapsed
Couple feature additions:
Automatically insert page breaks
after methods/classes
Keep long lines readable (nearly all
current implementations are broken)
Note: There are many reasons to need to print code... One very good one is escrow.
I use PrettyCode.Print for .NET. It does everything on your list, and more. (I use it for printing code excerpts for copyright registration paperwork, which is similar to your escrow case.)
It is a little slow to open a really big solution, but not unbearably so, and the output quality is excellent.
Try StarPrint's VSNETcodePrint
Couple feature additions:
Automatically insert page breaks after methods/classes
Keep long lines readable (nearly all current implementations are broken)