Chapter 29 (1/2)
CODER LEE YONGHO – CHAPTER 29: INTEGRATED TESTS (1)
There was a notice when he opened stack overfly the next
‘Huh? Did ain?’
He clicked the notice with a little expectation, but it wasn’t that his ansas selected Someone asked a question specifically to him
‘It seems like people saw my profile’
–Please leave your test code We solve all the bugs
It ritten with half-baked English Perhaps the asker was on his last straw, but he left a question for YongHo who had less than 100 reputations score
Maybe because YongHo only left a ‘JAVA’ tag on his profile, but the source the asker left as also in java YongHo pasted the source onto Eclipse and ran it
There was an alar
Error constructing Android Custom VIEW
From the word ‘weekday’ in the middle of the question, it seemed like s/he had been stuck on it for at least a week
‘Hmm… It doesn’t look that hard’
YongHo edited the constructor for the custoave the most efficient solution It was a code that an open source contributor such as An ByungHoon acknowledged so there were no problems
‘So the resolution of the ietting the screen size from the phone OS’
YongHo finished editing and sent it via e-mail, but he still sat in front of the computer
‘Gethub, huh……’
He showed as, but he was still inexperienced with developing a prograethub to raise his developing skills per An ByungHoon’s advice
‘There’s a lot of sources related to indroid’
Looking around the website, he foundto smartphone screens
‘Shall I upload one too?’
YongHo thought of creating a view that he thought up while using smartphones
A viehere the screen will show an effect like shattering glass when it was touched
He thought it would be interesting
‘Ah… My head hurts’
However, it definitely wasn’t easy Making a customized view source was difficult for even veterans with 5 years of experience Itto challengeit
If he didn’t know anything, he couldn’t start
‘Let’s put the constructor and the necessary methods first’
YongHo started developing a progra how fast ti
People say that the ram well is similar to the method to write well
Read a lot Read a lot of good sources
Write a lot Progras by oneself
Think a lot Think a lot about how to ram better
YongHo was thorough in doing these 3 things The tight project schedule ood and bad sources by replacing soYongHo also didn’t just blindly followed the bug
He strived to understand why it was like that, and he tried to think up of even better ways
Those efforts that he put in in his everyday life materialized as confidence to make the customized view
The unit tests were over after 2 weeks The majority of the people who participated in the KO Telecom’s project said that they will never ith KO Telecom’s project
YongHo raising his skills was good, but he felt the strains on his bones even though he was only in his 20’s The PM privately called YongHo as preparing for the integrated tests after the unit tests were over
“Did you really do all this?”
The PM, who called YongHo, looked at the report and asked YongHo again
“What do you mean sir?”
“Here, the test results report I had a look but more than half of the names here are yours”
“Ah, then it’s probably me”
After er Yun collapsed with a heart attack, work found its way over to YongHo YongHo, followingback And the results were on the document
“I called you here because I think it doesn’t er An also said it was you”
YongHo spoke when the PM esture that he couldn’t believe him
“I did my best”
“Noto my experience”
“……”
“If you said you did it, then it’s probably true The integrated tests begins tomorrow Do your best there too”
YongHo’s naraved in the PM’s head
Integrated tests