dandelionS Blog

Hello!

This time, the six of us who joined the company as new employees in the spring of 2026 would like to introduce the ‘Grooming and Appearance Training’ that was recently conducted.

For this year’s training as well, we were fortunate to have Ms. Morinai from Brilliant Impression Inc. serve as our instructor, just as she did last year. The training was conducted in two parts: a preliminary hearing session and the main session.

Hearing

During the hearing session, we were able to ask Ms. Morinai directly about any questions or uncertainties we had regarding grooming and professional appearance.

Grooming and Appearance Training

In the grooming training, we learned about topics such as the rules of proper grooming and the importance of appearance.

In the session on grooming rules, we were taught how to wear a suit properly, how to dress appropriately for different TPOs, how to coordinate outfits, and how to distinguish levels of formality in business attire. We also learned that the suitable occasions and meanings of necktie colors and patterns vary, and which types of shoes and bags are appropriate for business settings. As we are still not fully accustomed to wearing suits, we were repeatedly surprised to realize just how closely even the smallest details are observed.

In the section on the importance of appearance, we were taught about maintaining cleanliness and neatness—such as proper hairstyling, how to wear a suit appropriately, and how to care for our shoes. We learned that, because visual information accounts for most of a person’s first impression, cleanliness is one of the most crucial factors. When Ms. Morinai told us, ‘From now on, the first impression you give as new employees will, in some situations, become the first impression people have of Dandelions as a company,’ her words struck us deeply. From that moment, the suits we had been wearing without much thought suddenly felt like essential business tools.

As I move forward as a working professional and as a member of Dandelions, I hope to always remain mindful of maintaining a polished and professional appearance.

Personal Impressions

NoOne
Through this grooming training, I learned that proper suit etiquette and maintaining cleanliness are not only for my own benefit, but also a way to show respect to others.

🙂
After attending the two grooming training sessions, I realized how important it is to wear suits and neckties properly and to adjust colors and patterns according to TPO. Until now, I had looked at and worn these items without much thought, but through this training, my understanding of business attire has changed significantly.

VAWS
Through this grooming training, I learned that proper suit styling and choosing tie and shirt colors and patterns according to TPO can significantly influence the impression you give to others.

Gifukko
I used to be indifferent about grooming, but through this training I learned about the negative effects that such indifference can cause, and it made me realize that I should pay more attention to it.

Lulu
Whether in casual or formal situations, I felt that first impressions truly matter. I was surprised to learn that, in Japanese business settings, attire is closely tied to a company’s image, making formal wear especially important. In the lecture, I learned how clothing choices and tie patterns can influence the impression you give.

Boo ✊
Through this grooming training, I learned the importance of paying attention even to the smallest details—such as keeping my hair neat or shaving properly—because a poorly maintained appearance can directly shape not only how a person is perceived, but also how their company is perceived.

Summary

I want to carry forward what I learned in this training about the importance of proper grooming, and with the awareness that each of us represents the company, I hope to maintain a respectful attitude toward others and pay close attention to my appearance.

Thank you for reading all the way to the end.
Please look forward to the next blog!

As an engineer’s blog, I’d like to share what I’ve been learning on a daily basis.
I received an email asking me to migrate my assets to the new Deno platform, as the site where I had previously hosted my Discord bot had been rebuilt.
This migration allowed me to continue running the bot 24 hours a day for free, so I’d like to share more about that here.

What is Deno Deploy?

Before getting into the main topic, let me first briefly explain Deno Deploy.
It is a serverless edge computing service provided by the Deno development team.
It is a cloud service that allows you to publish applications written in TypeScript or JavaScript to the Internet without having to worry about setting up or managing servers. Because it makes it easy to deploy web apps, APIs, bots, and more, it has been widely adopted by many developers.

Email Content from Deno Deploy Classic

To be specific, the email I received had the following content:
・Deno Deploy Classic will be discontinued on July 20, 2026
・Apps on Classic will stop running after that date
・There will be no automatic migration
・You will need to manually migrate to the new Deploy

Things to Check Before Starting Work

① Are you using Classic?
Since you’ve received this email, it goes without saying that you’re using it, but just to be sure, please confirm that you’re using Classic.
https://dash.deno.com
If your project is listed above, it’s eligible for migration.

② Is the source code on GitHub?
Items to Check
・GitHub repository
・main branch
・Latest code

③ Make a note of the environment variables
Open the project you want to migrate in Deno Deploy Classic, and go to “Settings” → “Environment Variables.”
You should see tokens such as DISCORD_TOKEN configured here. Since these tokens are not automatically migrated, if you have a record of them, you’ll need to refer to that during the migration.
If you registered the token during development but didn’t keep a record of it, you’ll need to reissue a new token from the Discord Developer Portal.

The image shows the browser’s Japanese translation, which makes the Japanese look a bit unnatural, but the settings are correct.
Since I had the TOKEN noted down in my production notes this time, I’ll skip the step of reacquiring the TOKEN.

Just a side note… The Discord bot isn’t currently active.
It’s offline.

Actual Migration Procedures

① Log in to the new Deno Deploy
https://console.deno.com/

② Creating an Organization
Enter the Organization name and Organization slug, then click “Create Organization.”
If clicking this button reopens the previous Deno Deploy window, open a new Deno Deploy window and check to see if the organization you created is displayed there.

③ Tap “New App”
Tap the “Apps” tab, open “Applications,” and tap “New App.”

Open “Create a new application,” select your GitHub account, and choose your bot repository.
Scroll down and select your deployment targets.
Since this is a free plan, select “Free Regions” under “Managed,” then click “Create App.”
*This guide assumes you have already uploaded your source code to GitHub and have set up a new DenoDeploy integration with GitHub.

The build will start, but it will fail if you haven’t migrated the KV Database.

Click “Database” within the project to open the Database screen and migrate the KV Database.
Click “+Attach” for Deno KV on the following page

Click “provision new Deno KV” to create a KV database

Verify that the database you created is selected, then click “Attach Database.”

Return to the Build screen and click “Retry Build.”

④ Set the environment variables
Set the DISCORD_TOKEN in the “Environment Variables” section of the “Settings” page within your new Deno Deploy organization.

⑤ Check if you’re online on Discord
I am.

Now all that’s left is to test the system, and if it’s still running smoothly the next day, we’re all set.
This has been a long post, but that wraps up this edition of the Engineer’s Blog.

Stay tuned for the next Engineer Blog post.

技術者ブログとして日ごろ取り組んでいる学習内容を紹介します。
以前作成したDiscordのBOTを置いていた場所が再構築されたことに伴い、新しいDenoに資産を移動させて欲しいというメールが届きました。
今回の資産移動により無料での24時間稼働が継続できたので、今回はそちらについてご紹介します。

Deno Deployとは

本題に入る前に、まずDeno Deployについて簡単に説明します。
Deno開発チームが提供するサーバーレスのエッジコンピューティングサービスです。
TypeScriptやJavaScriptで作成したアプリケーションを、サーバーの構築や運用を意識せずにインターネット上へ公開できるクラウドサービスです。手軽にWebアプリやAPI、Botなどをデプロイできることから、多くの開発者に利用されてきました。

Deno Deploy Classicからのメール内容

具体的にどんなメールが届いたかというと、以下のような内容でした。
・Deno Deploy Classicが2026/7/20で終了
・それ以降Classic上のアプリは停止
・自動移行はされない
・手動で新しいDeployへ移行する必要がある

作業前に確認すること

①Classicを使用しているか
メールが届いているので使用していることは当たり前ですが、念のためClassicを使用しているか確認します。
https://dash.deno.com
上記にプロジェクトがあれば移行対象です。

②GitHubにソースコードがあるか
確認事項
・GitHubリポジトリ
・mainブランチ
・最新コード

③環境変数を控える
Deno Deploy Classicの移動させるプロジェクトを開き、「setting(舞台設定)」→「Environment Variables(環境変数)」を確認します。
ここでDISCORD_TOKENなどでTOKENが設定されているはずです。このTOKENも自動移行されないので、このTOKENのメモを残してあるのであれば、そちらが移行時に必要になります。
もし制作時に登録してTOKENのメモを残していない場合はDiscord Developer Portalから新しいTOKENを再発行する必要があります。

画像はブラウザの日本語訳表示になっているため日本語が不自然になっていますが、設定していますね。
今回は制作時のメモにTOKENが控えてあったのでTOKEN再取得は割愛します。

余談ですが…現在のDiscordBotは動いていない状態です。
オフラインに居ます。

実際の移行手順

①新しいDeno Deployへログイン
https://console.deno.com/

②Organization作成
Organization name・Organization slugを入力して「Create Organization」を押下。
押下したら前のDeno Deployが開きましたが、その場合は新しいDeno Deploy画面を開いて作成したOrganizationが表示されているか確認。

③New app押下
Appsタブを押下し、Applicationsを開き、New appを押下します。

Create a new applicationsを開き、自分のGitHubを選んで、Botのリポジトリを選択する。
下にスクロールして、Deployment targetsを自分の選択。
今回は無料利用なのでManagedはFree Regionsを選択して、Create Appを押下。
※ここではGitHubにソースを上げていて、GitHubと新しいDenoDeploy連携をしている前提です。

ビルドが始まりますがKV Databaseの移行をしていないと失敗します。

プロジェクト内のDatabaseを押し、Databaseの画面を開いてKV Databaseの移行をする。
以下のページのDeno KVの+Attachを押下

provision new Deno KV押下でKV Databaseを作成する

作成したDatabaseが選択されていることを確認して「Attach Database」押下

Buildの画面に戻り「Retry Build」押下

④環境変数を設定する
新しいDeno DeployのOrganization内にあるSettingのEnvironment VariablesにDISCORD_TOKENを設定する

⑤Discordでオンラインになったか確認する
なりました。

これであとは動作確認をして、翌日も問題なく動いていれば完了です。
長くなりましたが、これで今回の技術者ブログを終わります。

次回の技術者ブログをお楽しみに。

This time, we held an internal study session titled “How to Write an Internal Blog and the Basics of WordPress.”

Here’s a look at how it went.

Internal blogs are valuable assets for sharing technical information, research findings, and insights gained through daily work. At the same time, it’s not uncommon to hear people say, “I don’t know what to write,” or “I’m not good at writing.”

In this study session, we focused not on writing skills themselves but on “tips for creating articles that effectively communicate to readers.” The session covered practical topics for real-world use, including how to write blog posts, basic WordPress operations, handling images, and key points to keep in mind when using AI.

Topics Covered in the Study Session

In this study session, we learned about the following topics.

• How to structure articles with the reader in mind
• How to create effective titles and headings (H-tags)
• How to write easy-to-read text using bullet points and paragraph breaks
• Basic operations in WordPress (Gutenberg)
• Useful editing features such as List View and grouping
• Image optimization and the use of WebP format
• Key points for creating screenshots
• Secure handling of images and files with information security in mind
• Important considerations and effective methods when using AI

We didn’t just focus on learning how to operate WordPress; we also emphasized the importance of writing articles with the perspective that they will serve as resources for someone in the future.

Scenes from the Study Session

Internal blogs are assets that carry knowledge into the future.

An internal blog doesn’t end at the moment it’s written.

By sharing the knowledge, insights, and trial‑and‑error experiences gained through daily work and learning, individual experiences become assets for the entire organization. Not only technical information but also lessons learned on the job, study session content, and work-related improvements can all serve as valuable knowledge for other team members.

Internal blogs also serve as a record of activities and initiatives. By documenting “what was learned,” “why a particular approach was chosen,” and “what results were achieved,” they become valuable resources for your future self and for members who join later and need to look back.

In addition, articles such as employee introductions and event reports help convey the company’s atmosphere and the people who work there. They not only deepen mutual understanding among team members but also contribute to recruitment efforts and corporate branding.

An internal blog is a “company resource that someone in the future will read.” With this study session as a starting point, I hope each person will keep in mind how to create articles that are a little easier to read and a little clearer to understand, leading to even more valuable information sharing.

We plan to continue holding study sessions on WordPress in the future.
Please look forward to the next article as well!

---

今回は社内勉強会「社内ブログの書き方とWordPressの基本」を開催しました。

その様子をご紹介します。

社内ブログは、技術情報や調査結果、業務で得た知見を共有するための大切な資産です。一方で、「何を書けばいいのか分からない」「文章を書くのが苦手」という声も少なくありません。

今回の勉強会では、文章力ではなく「読み手に伝わる記事を書くためのコツ」をテーマに、ブログの書き方からWordPressの基本操作、画像の扱い方、AI活用時の注意点まで、実際の運用を意識した内容を紹介しました。

勉強会で取り上げた内容

今回の勉強会では、次のようなテーマについて学びました。

• 読者を意識した記事構成の考え方
• 読まれやすいタイトルや見出し（Hタグ）の付け方
• 箇条書きや段落分けによる読みやすい文章の作り方
• WordPress（Gutenberg）の基本操作
• リストビューやグループ化など便利な編集機能
• 画像の最適化やWebP形式の活用
• スクリーンショット作成時のポイント
• 情報セキュリティを意識した画像・ファイル管理
• AIを活用する際の注意点と効果的な使い方

単にWordPressの操作方法を学ぶだけではなく、「未来の誰かが読む資料」という視点で記事を書くことの大切さについても共有しました。

勉強会の様子

社内ブログは知識を未来へつなぐ資産

社内ブログは、書いた時点で終わりではありません。

日々の業務や学習の中で得た知識や気付き、試行錯誤した内容を共有することで、個人の経験は組織全体の財産になります。技術情報だけでなく、業務で得た学びや勉強会の内容、仕事の工夫なども、他のメンバーにとって価値あるナレッジになります。

また、社内ブログは活動や取り組みを記録として残す役割もあります。「何を学んだか」「なぜその方法を選んだか」「どのような成果があったか」を残すことで、未来の自分や後から参加したメンバーが振り返るための貴重な資料になります。

さらに、社員紹介やイベント紹介などの記事は、会社の雰囲気や働く人の姿を伝え、メンバー同士の理解を深めるだけでなく、採用活動や企業ブランディングにもつながります。

社内ブログは、「未来の誰かが読む社内資料」です。今回の勉強会をきっかけに、一人ひとりが「少し読みやすく、少し伝わりやすい記事」を意識し、より価値のある情報発信につなげていければと思います

今後もWordPressをテーマにした勉強会を継続して開催していく予定です。
次回の記事もぜひお楽しみに！

---