Tag Info

Hot answers tagged

32

As an alternative to daily scrum, we're thinking about asking developers to provide daily reports with the following conditions: What a terrible idea. Do you think that this can decrease their productivity? Yes. Why? A verbal presentation at a meeting combines writing and n people "reading" the report into one concurrent activity. Talking plus ...


30

QA should always try and make the bugs as easy for you to reproduce as possible and the bug description should contain the steps taken. However, if they can't easily reproduce the bugs, they should still get entered into the bug database with suitable title/headings and a full description of what they did to cause the bug. The bug description should ...


19

This is a common problem when you're a programmer who works independently, and you report to somebody who's not technical. Bosses like that mostly want to be able to figure out a few things: How happy are the users? Are the things the users want getting done? Is what you're doing worth the money you're being paid? An Agile burn-down or anything else ...


13

It looks like your QA department is doing too much exploratory testing (ie. They don't have a good test plan). Exploratory testing is good, and identifies problem areas, but from there they should be defining reproducible test cases (ie. a test plan) to perform that will reveal specific bugs. There's a number of reasons why a correct repro is necessary ...


12

There are some dangers with ad-hoc reporting. Reports tend to proliferate in the resulting combinatorial explosion. any report so-created has some built-in legitimacy because, well, it is a printed report, so the information must be valid. You might think that providing reports in this way reduces your burden for supporting people with new reports, but ...


11

I've done these in the past, but in the morning as opposed to the end of day. It generally took less than five minutes to fill out, so no, I can't see how there would be any decrease in a developer's productivity. The nice thing about doing it in the morning was that it made you think about what you're going to do for the rest of the day. Having said ...


10

Do the easier of implementing the equation specified in the formula or spitting out the previous row's value, incorporating a prominent comment in the code explaining why it is as it is. At the same time, send your question back up the chain. If they get back to you with a spec change in time to implement it, then implement it. If not, your butt's still ...


9

Since you already have your projects ready for Maven and Jenkins is installed, you may go one step further and install Sonar. It is an incredible code quality related tool, it performs Cobertura, Checkstyle, FindBug, and many other analysis tools at the same time. That way, the code quality reporting is done by Sonar, not by Maven or Jenkins. You can ...


9

Reports in an enterprise application context usually refer to Business Intelligence reports. A broad definition of Business Intelligence, from Forester Research is: Business intelligence (BI) is a set of methodologies, processes, architectures, and technologies that transform raw data into meaningful and useful information. It allows business users to ...


9

Unlike the votes to close, I do think this is an excellent, answerable question. The single most important thing in reporting is to understand your data and your data model. I mean really understand it, you need to be able to look at the results you get as you are developing and be able to tell if they are the right results. You need to know when you need ...


8

I'd be happy to check it out if you have a public repository (I'd be happier if its an hg repository)... Now for your question: There is no reason to not open source your project, even if there's a similar established project out there (which I don't know about and can't safely comment on). You shouldn't really care if there's something similar, since ...


7

If the bug can't be reproduced consistently, how will QA ever know whether it was fixed?


7

When there is a dispute between the users and the program about how the program should work. The solution isn't to fix the users. That goes double when you're presenting data to domain experts. In this case if the devs and the users have different ideas about what data should be presented, then correct response is to make the data presented match the user's ...


6

If you're only referring to small parts of the code, place it on the same page where you're speaking about it. No one wants to read through more than page's worth of code by if they can help it. For an immediate separation between code from English text, use: a different font a different background colour An irrelevant aside: for subconscious bonus ...


6

In all honesty, allowing anyone to report in without constraints seems a tad too far to the liberal side of the equation. Where I work, we go in a circle and each developer gives the following: What was done the prior day. Not all the tiny details, but overall. If the above is not finished, if not, what is needed to finish and how long it will take. If ...


6

I have seen a lot of expensive failures. I had a business partner tilt at this windmill for years. Their difficulty was their insistence that "non-technical" people be able to create reports. We built a number of solutions that people were able to learn and use to various degrees of success. Much like you, we started with parameterized canned reports. Then ...


6

Yes, you should expect more from them. They should be able to say: 1. Started new instance of program 2. I pressed button A 3. Entered "test text" into the TEST NAME field on Form #1 4. Pressed button B 5. Observed that the program crashed with this message (see attached screenshot). If all they tell is "it crashed", they're not very good. Even if the ...


6

This is a very glib answer, but getting right to the heart of the matter: In terms of DDD maybe think of reporting as a Bounded Context?, so rather than thinking in terms of "THE" domain model, you should be willing to think that it's okay to have more than one model. So yes it's okay if the reporting domain has reporting business logic in it, just as it's ...


5

IMO any type of daily meeting/report decreases productivity because it, to be frank, stinks of micromanagement. Yes, I'm aware of Scrum and the like and those aren't too bad provided they're short status updates ("Hey how is Project X coming?") but I firmly believe that it's insulting to professional developers to keep tabs on us at that low a level; it's ...


5

Tell him the truth. That you are stuck and don't know how to find the bug. Tell him that you need an expert / mentor to help you out. Yes, the bug is probably your fault, in a sense. But if you are too inexperienced to diagnose it / understand the root cause / understand what your real mistake was, then blaming yourself (or the boss blaming you) is ...


5

My advice is to read those bugs and give them a good old think. If you can't figure out a potential cause, forget about them for now. QA should document every issue they find, even if they have no idea how it happened. It's QA's job to try and reproduce issues, but realistically this won't always be possible. Sometimes it doesn't have anything to do with ...


5

Phew! That's a hum-dinger of a question. One suggestion I'd make is that, should you decide to move to Microsoft SQL Server as your database, then you should really consider using the SO-used library called Dapper. It's a really easy-to-use interface between C# code and SQL Server, and should at least address your statement: It's that bridge between ...


5

If the goal of the formula was to check for missing values, construct a test that should verify that the software can detect that a value is missing. If the formula is wrong, the test will not be successful. Then it can be flagged, investigated, and fixed.


4

We are facing this situation currently. At this point instead of an ad-hoc reporting interface we are running a trial with using Excel and Power Pivot. We integrated it with the Excel toolbar and allow users to import the data directly into and build reports using this. We found that many of these ad-hoc reports where one offs that where needed at a specific ...


4

This is one of those areas where you'll be richly rewarded by first learning the theory before learning a particular tool stack. The twin bibles of data warehousing theory are Bill Inmon's Building The Data Warehouse and Ralph Kimball's The Data Warehouse Toolkit. There's a lot of platform-war kerfuffle amongst BI insiders who treat these like religious ...


3

My team has been doing scrum for about one year now. Before that we were having two meetings a week, during which each team member reported about his / her activity in the previous 2, 3 days. Each meeting lasted between 30 minutes and 1 hour. In case we needed to exchange information and coordinate our work, we just used to go up to our colleagues and speak ...


3

About finding a bug: Being an experienced developer, I am not afraid to say to my boss that finding a bug takes between two hours and two weeks so he'd better leave me alone getting work done instead of asking me every five minutes whether I have progressed. I understand that this is not an option to you. About dealing with your bug: I would go back to the ...


3

It sounds like you have no way of knowing if you are complete or how far along you are to completion. That is okay. Keep a list of the features requested, which ones are done, in progress or not started. Track these as week to week chart of the total in each category. This will give you a set of points that you can extrapolate to the end date. That is ...


3

In addition to @Jonathan's answer, some points from when I had to present code in a report: Indent the code. This provides a dimension aspect to differentiate text and code. Export the code from the editor in a manner that retains the syntax coloring. When colors are used, ensure they print in a readable color range when printed in black & white


3

Reporting is the activity of applying transformations to stored data so that the end user can get information or satisfy business needs such as invoicing, control, planning, etc. Some examples of basic reports: In a retail system, you get a receipt after making a payment. This recipt is a type of report. In a retail system, the manager may want to pull ...



Only top voted, non community-wiki answers of a minimum length are eligible