코더 이용호

Coder Lee YongHo – Chapter 21: Three Hells of SI (2)

‘Phew… It isn’t easy here either.’
Manager Choi switched YongHo with SungGyu out of consideration. However, this place, the KO Telecom’s project, described by HyeJin could be summed up in one word.
Hell.
-Sunbae, this place is hell! Hell! The gates of hell have opened.
Firstly, there was no reason for the client company employees to see YongHo directly. YongHo only had to see Kim WonHo. The work too, was minor things like fixing button shapes.
But not here.
There wasn’t enough manpower so each person had to do their job properly, and if there was a hole, then getting abused by superiors was the norm.
And No JunWoo.
As the representative of the client company, he was bossy to no end. HyeJin warned YongHo again and again to be careful around him. There were a lot of stories but she just said that he would know of it when it happens.
-You worked on webs while you were there so you would probably do webs here too. I’ll first show you how it’s done.
The work was not as simple as he thought.
First, the downloaded source is run, and the test progresses according to the test scenario. If an error occurs, that scenario ID and the error content is reported on the test result report. Then, the source is modified so that the error doesn’t happen, and when it is confirmed, it is committed to the SVN. After committing, edit the test result report so that the said error is changed to fixed.
The words were simple, but from the source editing to the document work, it wasn’t easy to match the alignment. However, to YongHo, bugs were a way to develop himself. Moreover, fixing bugs were his specialty.
‘What kind of errors are waiting for me, I wonder.’
KO Telecom’s project, A.K.A Hell, YongHo was instead filled with expectations.

***

The alarm of the bug window popped up as soon as the program was run. On the top right of the bug window, tens of bugs started popping up.
‘Damn… That’s a huge lot.’
YongHo looked at the number on the side of the bug window. A total of 473 errors. That was the current number of bugs on his bug window.
‘There’s too many!’
The bug window didn’t only pick out real errors, but it also picked out anything that could cause a problem. Logic errors, efficiency errors included. For instance, the answer was supposed to be 11 but the calculations went wrong and the answer was changed to 7.
There was no error log for that so the programmers would have to confirm with their eyes. Such bugs were pointed out in the bug window.
‘If I fix all of them, they would probably call me crazy. Let’s see how HyeJin does and match her speed.’
After skimming over the error content, YongHo asked HyeJin, who was next to him, after organizing his thoughts.
“HyeJin, how many bugs are we supposed to fix each day?”
“Due to the schedule, we have to do about 3 per day. But well… It depends on the difficulty but the assistant managers do about 5 a day? if they do a lot.”
“Then how about you?”
“Me?”
“Yeah. How many do you do each day?”
HyeJin spoke with a slight conceit. 2 or 3 for an intern was great. There were countless newbies who couldn’t even fix one.
“I do about 2 or 3?”
“Hmm… Really?”
“Don’t feel too much pressure. First, it is sufficient to know how the current system is running.”
“Didn’t you say the unit tests were starting from next week? You said the source had to be finished.”
“I did say that but… We are still interns so there would probably nobody who expect things from you.”
At YongHo’s question, HyeJin answered with a don’t-worry tone.
“Oh, I see.”
“It will probably do if you just help with the simple tests next week.”
“Okay. I will do my best and fix anything I can.”
“One warning; don’t rashly commit after fixing something.”
“I know.”
HyeJin turned her face to the screen after talking. Perhaps her skills were recognized, but she was using dual monitors despite being an intern. YongHo was the only one who was using a laptop within the office.

The next day, after fixing some bugs, Yong Ho, who was reading the documents related to the project, was called by manager An Byung Hoon. (This is the guy from course registration)
“I was too busy to greet you. Good to have you here.”
“Good day to you, manager.”
“You left a deep impression that day, but… Looking at the test result report, I called you because I saw your name from time to time.”
“Is there any problem?”
YongHo became nervous while thinking whether what he did was wrong.
“Mr. YongHo fixed some things according to the test result report……”
“I am fixing some simple bugs that are within my knowledge.”
“Really? Hmm……”
This problem occurred because it was the first time YongHo worked in the SI industry. There was no programmer who fixed bugs on his/her first day. They first learn about the system for about a week, then look at the source for a while. However, YongHo had the ability to see bugs. Even without all this process, he could fix the bugs. That was why he fixed bugs on his first day.
Thinking that everyone else did the same.
“……”
“No. I will confirm and speak to you again. Go back to your seat.”
“I understand.”
Returning to his seat, HyeJin asked what was up.
“Why did the PL call you?”
PL was the acronym of project leader, and it was the person who lead the project technically. Programmers usually spoke to the PL rather than the PM(project manager?).
“Oh, I fixed some stuff so I wrote it on the report, and he called me for that.”
“WHAAAAAT?”
HyeJin’s voice’s pitch became high due to surprise. Perhaps she noticed her loud voice, she covered her mouth with one hand.
“Sunbae, you came here yesterday though?”
“Y, yeah.”
“Then you fixed bugs after just coming here yesterday?”
“Uh, Yeah, is it no good?”
“It’s not about being good or bad, but… it’s too early. Even if you played around at college…… Sunbae, didn’t you fix wrong? This project is not some part time work you know?”
“I know very well that it isn’t some part time work.”
“The total cost for this project is nearing 2billion! (≈1.736million USD), but fixing things on the first day……”
“Uh, I fixed some simple stuff.”
“No matter how simple it is… how can you start within a day… Did you compile the source properly then upload it?”
“Yeah, in built normally. I did the tests and there was no problem so I uploaded it.”
Even after that, HyeJin kept asking as if she didn’t believe it. YongHo’s reaction to hers was a there’s-no-problem attitude. But there was one problem.

Now it was No JunWoo, who called YongHo. According to the subcontract contract law, it was illegal for the person in charge from the client company to be placed in the same working place. Moreover, the person in charge from the client company must tell the specifications to the programmers through the PL or PM, not directly.
But No JunWoo and YongHo were currently closer to each other the subcontract law was.
“Mr. YongHo. Speak to me for a sec?”
“Me, sir?”
“Yes, you.”
YongHo moved towards where No JunWoo was sitting.
“Sit here.”
In an office with desks placed right next to each other, there was a single person who had 2 desks to himself.
No JunWoo.
The sole person with 2 desks to himself. YongHo was sat next to him.
“I saw your name on the test result report.”
“I did fix a few things.”
Manager An then No JunWoo. YongHo wanted to know what was going on.
“Really? Are you sure?”
“What do you mean by that……?”
“How much time has passed since you came here?”
“Today is the second day, sir.”
“And you fixed some bugs?”
“Yes, sir.”
“Go back to your seat, and call manager An here.”
“Why manager An……”
“Manager An?”
No JunWoo called manager An without listening to YongHo any further. YongHo went back to his seat and manager An took his place.


Translator’s note

Regular chapter 2/4

473 errors… Looks like MC has met his match. Korea… why does it have so high unemployment rate when there isn’t much manpower? Greedy companies….

Thx for reading!

Translator : Chamber
Proofreader : Maled

<< Previous Chapter | Index | Next Chapter >>

 

26 thoughts on “Coder Lee YongHo – Chapter 21: Three Hells of SI (2)

    1. Chamber Post author

      Or, as someone else says: God of Coding
      GoC(God of Crime)
      GoC(God of Cooking)
      GoC(God of Coding)

      3 GoC’s of Kobatochandaisuki

      Reply
  1. theone320

    They can just check the bugs. So no problem. I love this series. It is a shame that the chapters are so short, but I imagine it is hard to translate technical stuff.

    Reply
  2. koddycchi

    thanks-su for the chapter!!

    I dont think he fixing things on the first day was a good thing… At least he should have waited for the 3rd or the 4th day so people get a ‘good’ impression about him.

    I’m smelling sh*t

    Reply
      1. jacobpaige

        I think he’s more likely to have fixed 2-3 from the official list. They’re just upset that he fixed anything because they don’t think he could understand the project well enough to do so in the limited time that he’s been there.

        Reply
    1. Chamber Post author

      I want it too…

      Whenever:
      Exception in thread “main” java.lang.Error:….
      happens

      I wanna smash the computer

      Reply
  3. kirindas

    Lol!😄 It’s reasonable that they’re worried, but it’s kinda sad that he’s in trouble for being too good.
    Thanks for the chapter!

    Reply
  4. jacobpaige

    Its not just about a lack of people, its also about a lack of time, poor working conditions and excessive mismanagement.

    I’m not sure which would be worse for him: them assuming that he f’d up, rolling back his changes and treating him like dirt, or them realizing that he’s very good at fixing bugs and quadrupling his bug quota.

    I’m not sure why the author seemed to think that there was something wrong with the person in charge having more work space. Not only do they need it, but there needs to be some sort of perks to leadership or no one decent would want to do it.

    I wonder why no disgruntled/former employees have ever reported the company’s criminal activities here? It should be very easy for the authorities to confirm if they feel like it. Though, its certainly possible that they either didn’t feel like it or confirmed it over the phone because they really didn’t care if it was true or not and just wanted to be able to pretend that they’d done their jobs.

    Reply
    1. Chamber Post author

      What criminal activity? Overworking employees? (I’m sorry if that isn’t what you meant) that’s considered ‘normal’ in Korea. And they have a very good ‘excuse’.
      e.g. I heard some companies managed to ‘print’ 10,000 A4 pages of report related stuff. and they got the budget from outside. And they ‘have’ proof that the printer really ‘did print’ a 10,000 pages.

      And also, everywhere in manga and the like, the ‘upper echelons’ of every type of job (police, politician, company, etc…) are bitches solving everything with money

      Reply
      1. jacobpaige

        The criminal activity I was talking about where the criminal acts mentioned in this chapter. If I remember correctly it was the guy from the client company setting up his work space inside their work space and him directly speaking to the MC instead of going through his superiors. I assume that there are other violations, but I don’t know enough about Korean law to say for sure. I’m just assuming it based on there demonstrated lack of regard for the law.

        Reply
        1. Chamber Post author

          Ah, that…. Nobody in KR f*cking care about rules…. well, the one in a superior position won’t care about rules but if the one in the inferior position violates rules then probably they can forget about signing another contract together in the future

          Reply
          1. jacobpaige

            Yeah, its the same the world over I’d think. That’s why I specified disgruntled and ex employees. Even if they didn’t really expect anything to change, the fine/bribe that the company would have to pay might be vengeance enough for them.

            Reply
  5. UnknownAnon

    I think the main problem is that they fear he is jumping the gun so to speak. Usually one has to get a good understanding of the program, learn its purpose. All they see is someone who just arrived and started messing with the project code. Even the smallest of changes can cause huge errors to appear. They don’t want such a huge project to be ruined by an intern of all things. Also, I question the part where he says it is only simple bugs. Are these efficiency bugs? If so, they are probably thinking why fix something that already works? He should have definitely waited a couple days at least and get a good feel for things.

    Reply
    1. Chamber Post author

      I think he would at least fix the bugs that appear in the log(console), He ain’t that stupid… maybe he is, Idunno

      Reply
  6. kestroll

    I know this is just a story, but he didn’t need to set up a dev box? His previous rig transfered? And what happened to Kong’s development system? If he is falling in on a previously configured system I would think he could find problems. Equally, unit problems should be more clear cut…I think An will be able to back him on this, it’s already been stated that they aren’t in production yet.

    Reply

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s