conaman.github.io/about.html at master · conaman/conaman.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
---
title: About
description: "About conaman, a game client programmer with a strong interest in game engines, developer tooling, and practical workflow automation."
nav_key: about
permalink: /about/
---
<section class="page-hero">
  <p class="section-eyebrow">About</p>
  <h1>About conaman.</h1>
  <p class="page-intro">I am interested in the parts of development that sit just beside the main gameplay code path: editor workflows, debugging, content pipelines, build edges, and the small utilities that save teams from repeating the same friction.</p>
</section>

<section class="section">
  <div class="panel-grid">
    <article class="panel">
      <div class="profile-card">
        <img class="profile-card__avatar" src="{{ site.avatar }}" alt="GitHub profile image for conaman">
        <div>
          <p class="section-eyebrow">Profile</p>
          <h2 class="profile-card__name">conaman</h2>
          <p class="profile-card__subname">Seungjee Baek</p>
          <p>Game client programmer with a strong interest in game engines, developer tooling, debugging, and technical documentation that stays grounded in real production constraints.</p>
        </div>
      </div>
    </article>

    <article class="panel">
      <p class="section-eyebrow">Current direction</p>
      <h2>Practical, engine-aware workflows</h2>
      <p>The most interesting work for me usually lives where system behavior is not obvious at first glance. I like digging into how something actually works, then turning that understanding into a clearer workflow, tool, or note that others can reuse.</p>
    </article>
  </div>
</section>

<section class="section">
  <div class="panel-grid">
    <article class="panel">
      <p class="section-eyebrow">What I work on</p>
      <ul class="info-list">
        <li>
          <strong>Game engines and tooling</strong>
          Helpers, inspection flows, and utilities that make engine-adjacent work easier to understand and repeat.
        </li>
        <li>
          <strong>Debugging and analysis</strong>
          Source-level exploration, build behavior, and technical notes that make tricky systems easier to reason about.
        </li>
      </ul>
    </article>

    <article class="panel">
      <p class="section-eyebrow">How I think about the work</p>
      <ul class="info-list">
        <li>
          <strong>Practical over performative</strong>
          I prefer tools that survive real project constraints over demos that only look clean in ideal conditions.
        </li>
        <li>
          <strong>Document the why</strong>
          Good notes preserve trade-offs, compatibility boundaries, and debugging context, not just the final commands.
        </li>
      </ul>
    </article>
  </div>
</section>

<section class="section">
  <div class="page-hero">
    <p class="section-eyebrow">Elsewhere</p>
    <h2>Find the public work</h2>
    <p class="page-intro">GitHub is the main hub for repositories, while this site is where those repositories get context. If you want the shortest path into the work, start with the projects page and the `unreal-mcp-ue4` case study.</p>
    <div class="cta-row">
      <a class="button button-primary" href="https://github.com/conaman">GitHub</a>
      <a class="button button-secondary" href="{{ '/projects/' | relative_url }}">Projects</a>
      <a class="button button-secondary" href="mailto:{{ site.email }}">Email</a>
    </div>
  </div>
</section>