没有不值得去解决的问题,也没有不值得去学习的技术!

Found That Dianya Resume Skill Tags Couldn’t Be Edited? My Feedback Was Fixed the Next Day

让我意外的是。 第二天管理员就回复了。

作者:

在


1. How It Started

A while ago, I prepared to update my resume on Eleduck.

Since I have been looking for remote PHP / Go jobs recently, I wanted to adjust my skill tags to:

Plaintext
PHP
Go
Laravel
Gin
Redis

But I ran into a problem.

You can add up to 5 skill tags, but there is no way to delete or replace them.

In other words, once added, they could no longer be modified.

So I made a post in the community, hoping the administrators could improve this feature.

How to modify Eleduck resume skill tags
How to modify Eleduck resume skill tags

2. Surprisingly, I Received a Reply the Next Day

To my surprise.

The administrator replied the very next day.

Thanks for the feedback. This feature has been updated to include the ability to delete tags. Please try again.

To my surprise. The administrator replied the very next day.

My first thought at the time was:

They are really efficient.

Many platforms might take a long time to schedule something like this.

But Eleduck just got it done.


3. Re-editing the Resume

I went back to the resume page.

I found that I could now delete the original skill tags.

So I adjusted my skills to:

Plaintext
PHP
GoLang
Laravel
Gin
Redis
I went back to the resume page. I found that I could now delete the original skill tags.

For me, these five tags basically cover the main directions of the remote positions I am currently seeking.


4. Even a Very Small Feedback Can Be Truly Valuable

Actually, before making this post.

I did not hold the expectation that it would “definitely be changed.”

I just thought:

Since I encountered a problem, I should provide some feedback.

I did not expect it to actually be adopted.

For a developer.

This kind of positive feedback is actually quite delightful.


5. Why I Have Started Recording These Things Now

Recently.

I found myself increasingly wanting to record these experiences in my blog.

I used to think:

What is there to write about such trivial things?

Later, I realized.

A lot of blog content is accumulated exactly this way.

A job hunting experience.

A remote interview.

A pitfall encountered.

A piece of product feedback.

A website optimization.

……

Individually, none of these are earth-shattering events.

But by consistently recording them over time:

  • Someone might find it through a search;
  • Someone might avoid a pitfall because of it;
  • Someone might discover your blog this way;
  • It might even bring in a little ad revenue or new collaboration opportunities.

So my thinking has become simpler and simpler now:

As long as it is a real experience and might be of some help to others, I will try my best to write it up as a blog post.

Each article might only get a few dozen or a few hundred views.

But over the course of a year, this content will keep accumulating and become an asset of your own.

系列导航

关于作者 · 持续学习与技术实践

我是一名拥有 15 年以上开发经验的技术从业者,自 2013 年起持续运营个人技术博客,记录工作与个人项目中遇到的真实问题,以及解决问题过程中的探索、实践和思考。

除了技术写作,我也在持续开发和维护自己的独立项目,探索新技术和新工具在实际场景中的应用。我始终相信,没有不值得去解决的问题,也没有不值得去学习的技术。

如果这篇文章对你有所帮助,欢迎浏览博客中的其他文章,也欢迎交流技术经验与想法。

关于我  ·  GitHub  ·  邮件联系