What a gem.

[James Treworgy]

What a shortcut! A qualified programmer would have accounted for the fact that BatteryLifePercent is floating point, and may not be in increments of 1/100th. What if it's 0.975? Obviously this should have been written as:

If SystemInformation.PowerStatus.BatteryLifePercent <= 1 And
SystemInformation.PowerStatus.BatteryLifePercent > 0.99 then Return "99%"
ElseIf SystemInformation.PowerStatus.BatteryLifePercent <= 0.99 And
SystemInformation.PowerStatus.BatteryLifePercent > 0.98 then Return "98%"
...

:)

[Jasmine2501]

They are clearly just coding around a bad framework. There's a field called BatteryLifePercent, but it's not actually a percentage number. Obviously the framework is incorrect.

[Sander Rossel]

Option Strict is off or the Property would have an As clause! Correct would've been:

Public ReadOnly Property BatteryPercent As Percent
Get
If SystemInformation.PowerStatus.BatteryLifePercent.ToString = "1" Then
' No implicit conversions with Strict On!
Return Convert.ToPercentage("100%")
' Etc...

Now that just made a world of difference :)

It's an OO world.

public class Naerling : Lazy<Person>{
public void DoWork(){ throw new NotImplementedException(); }
}

[YSLGuru]

Could be wrong but it looks like a case of lack of knowledge, not knwoing/understanding that there is a better/more effecoent way to achieve teh same goal. I work in RDBMS (sepcifcally SQL Server) and I routinely see this same kind of bad design choice and usually its due to a lack of knowledge/eductaion on the product/system. For example when the develoepr needs to store a bolean value ( 0 and <>0 ) they use a NUMERIC data type which [by default) uses 9 bytes instead of using the smaller BIT data type.

[AspDotNetDev]

This is why degrees are useful. You may not be the best programmer in the world after graduating, but at least you should learn enough to avoid code like this. Having a get-r-done attitude is fine and all, but a get-r-done intelligently attitude is much better.

Somebody in an online forum wrote:

INTJs never really joke. They make a point. The joke is just a gift wrapper.

[weberrich]

Although, I know doesn't look all that good. There may be come consideration to optimization. Does the huge case statement cost less than a few function calls? Just a thought, and like to play devils advocate.

[Jorgen Andersson]

That's horrible. Everyone knows that you should use a varchar and store it as 'True' or 'False'.

Light moves faster than sound. That is why some people appear bright, until you hear them speak. List of common misconceptions

[firegryphon]

That is a joke right? Does this joke include enough to go all the way to 0%?

[Julien Villers]

You were joking right? I saw graduates that couldn't tell a variable from an array from a class from an object (etc...). Oh, and they weren't like barely getting their grades, in fact, they were top of the class (due to compensating programming with communication or economics, plus getting their projects done by others).

'As programmers go, I'm fairly social. Which still means I'm a borderline sociopath by normal standards.' Jeff Atwood 'I'm French! Why do you think I've got this outrrrrageous accent?' Monty Python and the Holy Grail

[Mark AJA]

Don't know what language this is, but I'm sure you could use the following to reduce the code length:

' ...
Return (SystemInformation.PowerStatus.BatteryLifePercent.ToString *100) & "%"
' . End of function.

[AspDotNetDev]

Nope, not joking. Not everybody who goes through college is a better programmer than a non-college programmer. Though I'd say more college grads have better sense. Of course, that's from my anecdotal experience*, so YMMV. *For example, I wrote my 558 Lines of QuickBasic Glory before I went to college. Relying on file IO, "unnecessary" optimizations, and third party libraries seemed like too much work at the time.

Somebody in an online forum wrote:

INTJs never really joke. They make a point. The joke is just a gift wrapper.

[smcnulty2000]

There you go, thinking like a programmer again. Where's that going to get ya? :)

_____________________________ Give a man a mug, he drinks for a day. Teach a man to mug... The difference between an ostrich and the average voter is where they stick their heads.

[Julien Villers]

I guess if you take a statistical sample of graduates vs non-graduates, the average is better, and the deviation lower. I was worried that you'd equate degree with competence ;)

'As programmers go, I'm fairly social. Which still means I'm a borderline sociopath by normal standards.' Jeff Atwood 'I'm French! Why do you think I've got this outrrrrageous accent?' Monty Python and the Holy Grail

[Paladin2000]

Actually, it's:

Return (SystemInformation.PowerStatus.BatteryLifePercent * 100).ToString() + "%"

You did the ToString before the multiplication. Note that this:

SystemInformation.PowerStatus.BatteryLifePercent.ToString("p")

...does create a percentage conversion, but since it has decimals and a space it is not equivalent.

[Mark AJA]

I used & and not + as & can join a string and a number. + will only add two nunbers or attach two strings. I would usually use CStr$() but as I was not to sure what language this was, used & as it's used in a number of languages.

[GBSC]

NA is correct because if you can't determine the battery percentage you must be dealing with sodium :)

[James Lonero]

I did something like this when I was programming in assembly language back in college. I was making a way to get a value out of a register out to the terminal in an integer form. Then, we only had 16 bit registers and could only output -32738 to 32737. But, there was no library routines to output to the terminal.

[Fabio Franco]

Well, although in assembly one can develop a routine for that, it's forgivable if you don't, specially in college while learning. What's unforgivable is having this in a high level language in production code for a mission critical application.

"To alcohol! The cause of, and solution to, all of life's problems" - Homer Simpson

[Paladin2000]

The "+" operator does work here, it implicitly converts the number to a string and concatenates it to the other. But yes, the "&" operator is for concatenation explicitly. However, in your example, my key point was that you used the "*" operator between a number and a string...

[Mark AJA]

I don't know what language uses a * between two strings. * is usually used to multiply two numbers. EG 123*4 = 492 + is used to add two numbers. EG 123+4 = 127. 123+"4" = error & is used to join two numbers, strings or a number and a string. EG 123 & 4 = "1234" If a language returns 492 or "492" from 123*"4" then in my opinion the language needs an update. The following Visual Basic 5 code:

Private Sub Form_Load()
Dim a As Integer ' or as Long or Double
Dim b As String
a = 123
b = "4"
MsgBox a * b
End Sub

displays 492, but should display an error acording to other versions of Basic.