23 comments
Comment actions Permalink

Whose eye is it in the error square? Am I being watched?

Stanislav Davydov wrote:

- Editor. Editor error stripebar L&F enhancements.


0
Comment actions Permalink

Richard Nemec wrote:

Whose eye is it in the error square? Am I being watched?

Stanislav Davydov wrote:

>> - Editor. Editor error stripebar L&F enhancements.



When an eye appears it means that background code inspections are
working to check your code for more deeply.

Best regards,
Vladimir Kondratyev
_____________________
JetBrains

0
Comment actions Permalink

>When an eye appears it means that background code inspections are
>working to check your code for more deeply.

Very neat :)

Tom

0
Comment actions Permalink

I try to calculate stability value for 873 :)))

14 builds for 12 days...
It's becouse 2 builds failed?

Or, maybe, i'm wrong whole about builds...
--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Richard Nemec" <rndzank@attbi.com> wrote in message
news:bfm0l2$h3p$1@is.intellij.net...

Whose eye is it in the error square? Am I being watched?

>

Stanislav Davydov wrote:

- Editor. Editor error stripebar L&F enhancements.

>


0
Comment actions Permalink

Alexey Efimov wrote:

I try to calculate stability value for 873 :)))

14 builds for 12 days...
It's becouse 2 builds failed?

Or, maybe, i'm wrong whole about builds...


Build number means nothing

Best regards,
Vladimir Kondratyev
_____________________
JetBrains

0
Comment actions Permalink

>Build number means nothing

What do you think - will 3-digit build-numbers be enough for this EAP
:) ?

Tom

0
Comment actions Permalink

>Build number means nothing

BTW, why not use dates instead of build-numbers?

Tom

0
Comment actions Permalink

BTW, why not use dates instead of build-numbers?


There can be more than one build in some days.

--
Valentin Kipiatkov
JetBrains, Inc
http://www.intellij.com
"Develop with pleasure!"


"Thomas Singer" <thomas.singer@NOregnisSPAM.de> wrote in message
news:8h3vhvklktok2nurpm3df1rqmd5n1ifi37@4ax.com...

>Build number means nothing

>

BTW, why not use dates instead of build-numbers?

>

Tom



0
Comment actions Permalink

Then why not use hieroglyphic symbols instead of numbers?

Wait, wait, even better, why not use numbers instead of numbers?

0
Comment actions Permalink

>There can be more than one build in some days.

But I guess no more than one released build per day.

Tom

0
Comment actions Permalink

Thomas Singer wrote:

>But I guess no more than one released build per day.
>

It happened in the past (Ariadna). Ah, those good old days...

Alain

0
Comment actions Permalink

It happened in the past (Ariadna). Ah, those good old days...


Oh come on, it's not that bad even today.
I'm still able to work on production code with the latest Aurora build,
and slowly but surely, some of my requests or bugs are being implemented.
The situation is not that bad.

Guillaume


0
Comment actions Permalink

or bugs are being implemented.


Hihi... is that what you do over there in France? "Implement bugs"? ;o)

Sorry, nothing personal... I just couldn't resist.

0
Comment actions Permalink

Hihi... is that what you do over there in France? "Implement bugs"? ;o)
Sorry, nothing personal... I just couldn't resist.


LOL :-D You're right !
I just realized my mistake "after" I posted the message ;)
Usually, no, we don't implement bugs...

Guillaume


0
Comment actions Permalink

Realy? :)

I think, firstly, bugs are implemented, then they fixed :)
Just wonderfull development :)

--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Guillaume Laforge" <glaforge@reflexe.fr> wrote in message
news:bg5ifp$78j$1@is.intellij.net...

Hihi... is that what you do over there in France? "Implement bugs"? ;o)
Sorry, nothing personal... I just couldn't resist.

>

LOL :-D You're right !
I just realized my mistake "after" I posted the message ;)
Usually, no, we don't implement bugs...

>

Guillaume

>
>


0
Comment actions Permalink

You're dead wrong Alexey

> Realy? :)
> I think, firstly, bugs are implemented, then they fixed :)


I've never put any bug in my code. They all sneeked in, on their own,
without my consent.

Bugs have a life of their own. Bugs were born, and normally live in
Bugland. When they want to take some vacation, they visit their family,
that happen to live in your code base. Some like it so much abroad, that
they decide stay longer, or even become permanent resident (MS products).

You may hunt bugs, the whole year, but the best season is definitely the
EAP. The other season - Release - is much calmer.

Bugs, like trains, have a known base of fans. In IDEA country, they all
gathers in the newsgroups. Some spotters - hunters - have a very poor
eyesight, so they would count multiple seings of one same bug. This is
called "duplicate".

(.. to be continued)

Alain

PS. This was slightly O.T.

0
Comment actions Permalink

I think, firstly, bugs are implemented, then they fixed :)
Just wonderfull development :)


Well, you know, if I dont put bugs in my code, I'd feel bored, I'd have
nothing to fix !

Guillaume


0
Comment actions Permalink

PS. This was slightly O.T.


You should definetely write a weekly column ;)
Let's start a blog ! :-D

Guillaume


0
Comment actions Permalink

:)
Let's write book "Bughunting: Best practices"

BTW, i now read the "Bitter Java" book from Bruse Tate, it discussed the
common "anti-patterns" in Java programming. Nice staff :)

And realy good idea from Guillaume Laforge about blog :)

Waiting for continue story about Bugland :))
--
Alexey Efimov, Software Engineer
Sputnik Labs,
http://www.spklabs.com
"Alain Ravet" <alain.ravet.list@wanadoo.be> wrote in message
news:bg5jq5$7pd$1@is.intellij.net...

You're dead wrong Alexey

>

> Realy? :)
> I think, firstly, bugs are implemented, then they fixed :)

>
>

I've never put any bug in my code. They all sneeked in, on their own,
without my consent.

>

Bugs have a life of their own. Bugs were born, and normally live in
Bugland. When they want to take some vacation, they visit their family,
that happen to live in your code base. Some like it so much abroad, that
they decide stay longer, or even become permanent resident (MS products).

>

You may hunt bugs, the whole year, but the best season is definitely the
EAP. The other season - Release - is much calmer.

>

Bugs, like trains, have a known base of fans. In IDEA country, they all
gathers in the newsgroups. Some spotters - hunters - have a very poor
eyesight, so they would count multiple seings of one same bug. This is
called "duplicate".

>

(.. to be continued)

>

Alain

>

PS. This was slightly O.T.

>


0
Comment actions Permalink


Guillaume Laforge wrote:

>>I think, firstly, bugs are implemented, then they fixed :)
>>Just wonderfull development :)


Well, you know, if I dont put bugs in my code, I'd feel bored, I'd have
nothing to fix !


Bugs are our way of keeping our jobs... oh wait... I had too many bugs
once and stopped working where I was... now I'm confused.

R

0
Comment actions Permalink

Bugs are our way of keeping our jobs... oh wait... I had too many bugs
once and stopped working where I was... now I'm confused.


You have to write bugs, but not too much.
Enough so that your boss thinks your essential to his team.
But less that a certain level over which you get fired.
We have to find the right dose of bugs ;)

Guillaume


0
Comment actions Permalink

Valentin Kipiatkov wrote:

>>BTW, why not use dates instead of build-numbers?


There can be more than one build in some days.


We use the following system for our build numbers:

BRANCH-YYYYMMDD-HHNN

(HH being 24 hours and NN being minutes)

For example: HEAD-20030729-0130

All managed by an automated build system aptly named Babel ;)

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://java.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: 416-643-4846 | Fax: 416-594-1919

0
Comment actions Permalink


Guillaume Laforge wrote:

>>Bugs are our way of keeping our jobs... oh wait... I had too many bugs
>>once and stopped working where I was... now I'm confused.


You have to write bugs, but not too much.
Enough so that your boss thinks your essential to his team.
But less that a certain level over which you get fired.
We have to find the right dose of bugs ;)


hehe, can we get a use case of this and submit it as a request for IDEA
to let us know how much crap we have in our code and show like a little
'deep doo doo' meter which will tell you know if you're OK or not with
Green being "Dude, you're doing OK your job is important", Yello meaning
"if you've gotten in trouble before, you're replaceable watch it",
better reduce the bugs or you'll give your boss an excuse, and Red
meaning "I hope your resume's ready, here they come". Of course bosses
would love to have messages going out when you hit various levels, will
sell idea real well to the IT department, and keep US in check and
nervous, working hard.

LOL

R

0

Please sign in to leave a comment.