2025.
2. 9. (Sun)
+ 61,000
1
Oh Seong-min
2025.
2. 6. (Thursday)
Today, I met a friend and we read The Economist together while hanging out at a cafe. I paid for a subscription when I was a freshman in college, but I just found out that I can use it for free with my school library account (...)
Anyway , since the featured article in The Economist's Asia section this week was about Korean politics, I read it together.
Due to the impeachment crisis of President Yoon Seok-yeol, attention is focused on who will be the next presidential candidate, and this was an article introducing Lee Jae-myung, who is being nominated as a strong candidate. What was interesting was that, although it is a British current affairs magazine, it describes Korean politics in considerable detail and accuracy. It was interesting that it accurately reflected the latest issues, such as Representative Lee Jae-myung's political inclination and the results of recent opinion polls.
As I was growing tired of the biased and factory-produced articles in the domestic press and media, it was beneficial to learn about objective perspectives on Korea from overseas, and it was a good opportunity to think objectively about the current situation of our country.
1
2025.
2. 5. (Wed)
I was a little discouraged when I saw that a service very similar to the one I was working on was already doing so well. Because of that and the hangover , I put off development today. I think I'm making more and more excuses. Haha ㅠㅠ
Instead, I thought a lot about how to build a restaurant database in the existing rider community. It is possible to get location information from Naver Map or Kakao Map as an API, but it would be difficult to manage the information received through the API by linking it to reviews and ratings, so instead, I decided to create my own restaurant table and implement it by crawling Naver or Kakao Map when filling out the contents of the table. Since the information needed is only the store name, address, and coordinates, I think it will not be difficult to implement. I plan to first create the simplest MVP possible and add functions based on the response.
2025.
2. 4. (Tue)
Today, I have a sudden commitment that means I won't be able to work much, so instead, I took some time to read some of the many links I've had in my bookmarks list for years that caught my eye.
“The idea that university degrees don’t matter is a Silicon Valley fantasy.”
The point of this article is that there is a culture in Silicon Valley that worships the "college dropout entrepreneur," but in fact, the majority of founders who received investment from Y Combinator have college degrees, especially Ivy League degrees, and thus the most effective means of success is a top-tier college degree.
In fact, I thought a lot about this topic when I was a high school student and a freshman in college. At the time, I thought, 'It is advantageous to be a graduate of Seoul National University or KAIST to receive VC investment. Other than that, school has little to do with the success or failure of a business.'
And that idea seems to be somewhat correct. When evaluating a business from the outside, the school the founder graduated from is one of the evaluation factors, but I think the market and customers are not interested in the school the founder graduated from. I don't have any experience yet, so I don't know how important it is to attract external funding for a business, but the conclusion, as always, seems to be 'I just have to do well.'
2025.
2. 3. (Mon)
Designed and implemented the home page of the rally information site.
I temporarily deployed it to the old domain I purchased.
The functions are simple and the requirements aren't that many, so I think it'll mostly be completed by tomorrow.
2025.
2. 2. (Sun)
After hearing the suggestion from the fandom, we decided to create a site to collect information about the rally instead of the rider community.
So today, instead of drawing the rider community UI, I'm going to roughly plan out a rally information site.
I figured out where to get information about the meeting.
I figured out where to get information about the meeting.
The requirements are simpler than the community requirements, so I think we can implement it in a short period of time. We plan to release it within two weeks with only the core features and see the response.
1
Made with Slashpage