java開發第一天上班_從第一天開始，如何成為一名優秀的團隊合作伙伴，成為初級開發人員

java開發第一天上班

One of the many things you might be asking yourself when starting your software development career is:

在開始軟件開發職業時，您可能會問自己很多事情之一：

“How do I REALLY contribute to my new team?”
“我如何真正為我的新團隊做出貢獻？”

This was one of the things that scared me when starting my first job as a junior developer. So I’ve decided to summarise the things I did that earned some praise from my manager and teammates.

當我開始擔任初級開發人員的第一份工作時，這是讓我感到恐懼的事情之一。因此，我決定總結自己所做的工作，這些工作贏得了經理和隊友的一致好評。

When hiring junior developers, it is expected that there will be some learning and ramping up time. You will have to learn the processes, the codebase, and a bunch of other stuff.

雇用初級開發人員時，預計將需要一些學習和增加時間。您將必須學習流程，代碼庫和其他內容。

But that doesn’t mean you can’t hit the ground running and make an impact with your new team from day 1. Follow these tips and you’ll do just that.

但這并不意味著您從第一天開始就不會對新團隊產生影響，請遵循這些提示，您將可以做到這一點。

以工作為榮 (Take pride in your work)

Let’s look at a picture.

讓我們看一張照片。

Now you’re probably asking, “Why are you showing me a photo of some old Coke-Cola cans?”

現在您可能會問，“為什么要給我看一些可口可樂罐的照片？”

Which is a fair point. But what if I told you that this was actually an oil painting? Yes, this hyper-realistic painting is the work of Pedro Campos (see a link to his site above). You may or may not be into art, but you have to admit this is pretty cool (my phone doesn’t even take pictures this clear).

這是一個公平的觀點。但是，如果我告訴您這實際上是一幅油畫呢？是的，這幅超現實主義繪畫是佩德羅·坎波斯(Pedro Campos)的作品(請參見上面指向其網站的鏈接)。您可能會也可能不會進入藝術領域，但是您必須承認這很酷(我的手機甚至都無法清晰地拍照)。

But still, what’s the point? My point is you can tell just how much pride Pedro takes in his work. Every intricate little detail is covered. Even though this may only seem like a bunch of old cans, he has turned it into something amazing.

但是，仍然有什么意義呢？我的意思是，您可以說出佩德羅對他的工作有多自豪。 每個復雜的小細節都被覆蓋。 即使這似乎只是一堆舊罐頭，他還是把它變成了令人驚奇的東西。

This is the approach you should take with your work. No matter how small or simple a task is, give it your all, and leave no stone unturned.

這是您在工作中應該采取的方法。不管任務多么小或多么簡單，都應全力以赴，絕不遺余力。

This is one of the best ways to make a good impression with your team. Write readable code. Test your code. Leave comments where necessary. Cover all the edge cases. Put 110% into everything you do. Doing this makes your teammates think “Wow, this person knows their stuff and cares about what they are doing”.

這是在團隊中留下良好印象的最好方法之一。編寫可讀的代碼。測試您的代碼。在必要時發表評論。覆蓋所有邊緣情況。將110％投入到您所做的所有事情中。這樣做會使您的隊友認為“哇，這個人知道他們的東西，并在乎他們在做什么”。

知道如何尋求幫助 (Know how to ask for help)

As I mentioned in my article, ace your first year as a junior developer, asking questions when you are stuck is a good habit to get into. Although, knowing how to ask questions can make all the difference. If you say “Hey, I’m stuck can you help me?”, it makes it a bit harder for the seniors in the team to help you. In contrast, saying:

正如我在文章中提到的那樣，在您是一名初級開發人員的第一年，當您陷入困境時提出問題是一個養成的好習慣。雖然，知道如何提出問題可能會有所作為。如果您說“嘿，我被困住了，您能幫我嗎？”，這會使團隊中的前輩很難幫助您。相反，說：

“Hey, I’m working on this task, and I’m trying to do something, but I am getting an error in this function at this line. The error message is confusing, have you any ideas?”

“嘿，我正在執行此任務，并且正在嘗試做某事 ，但是在此行此函數出現錯誤。錯誤消息令人困惑，您有任何想法嗎？”

The more information you can give, the easier it will be for others to help. You will also show that you understand what you are trying to do, and have simply hit a wall.

您可以提供的信息越多，其他人將越容易獲得幫助。您還將表明您了解自己要做什么，并且碰壁了。

As a side note, make sure to give your best shot at overcoming the issue you have come across. Do a quick Google search and have a look at other parts of the codebase that solves a similar problem. If you still are stuck after doing some investigating, go ahead and ask for help.

作為附帶說明，請確保盡最大努力解決遇到的問題。快速進行Google搜索，并查看可解決類似問題的代碼庫其他部分。如果進行了一些調查后您仍然陷入困境，請繼續尋求幫助。

聽 (Listen)

“The quieter you become, the more you can hear.”
“您變得越安靜，聽到的聲音就越多。”

There is a time to speak, and there is a time to listen. As a junior developer, when a senior developer is explaining something to you, or your team is discussing things, that is the time to listen and take it all in.

有時間說話，有時間傾聽。作為初級開發人員，當高級開發人員向您解釋某些內容時，或者您的團隊正在討論這些內容時，就是時候聆聽并接受所有內容。

Ask questions if you’re not sure about what is being said, but try to refrain from interrupting or talking over somebody else. Nobody likes that.

如果您不確定所講的內容，請提出問題，但請盡量避免打擾或與其他人交談。沒有人喜歡。

If need be, write things down. It leaves a great impression when a junior developer only has to hear things once, without having to be repeatedly given the same information a few times. Plus, it’s one less time you’ll have to ask!

如果需要，寫下來。當初級開發人員只需要聽一次，而不必多次重復獲得相同的信息時，就會給人留下深刻的印象。另外，您也不必再問了！

Some great note taking apps I personally use are (all completely free to use):

我個人使用的一些很棒的筆記應用程序都是(完全免費使用)：

https://simplenote.com
https://simplenote.com
https://www.google.com/keep/
https://www.google.com/keep/
https://evernote.com/
https://evernote.com/

幫助別人 (Help Others)

Found yourself at a loose end after finishing a task? Or waiting for your code to be reviewed/tested? You could spend that precious downtime scrolling Facebook, or you could find ways to help your team.

完成任務后發現自己處于松懈的境地？還是等待您的代碼被審查/測試？您可以將寶貴的停機時間花在滾動Facebook上，或者找到幫助團隊的方法。

Don’t be afraid to turn to your team and say,

不要害怕轉向您的團隊并說：

“I have a bit of downtime if anyone needs help with anything?”
“如果有人需要任何幫助，我會有一些停機時間？”

Even if no one needs any help, the team will appreciate that you asked. Now you can browse social media guilt free! Hurray!

即使沒有人需要任何幫助，團隊也會感謝您的要求。現在您可以免費瀏覽社交媒體內了！歡呼！

善于溝通 (Communicate Well)

Communication is important, which is why I’ve opened this section with a picture of two really stern people sitting at a laptop.

溝通很重要，這就是為什么我在本節中使用兩個真的很嚴厲的人坐在筆記本電腦前的圖片的開頭。

You’ll be working with managers, teammates (some remote!), end users and the like. So it’s important to be able to communicate well.

您將與經理，隊友(有些遠程！)，最終用戶等一起工作。因此，保持良好的溝通非常重要。

As a junior developer, there is often that thought that speaking more = more information. This, in fact, is not the case. Ask my old team lead. “Chris, you’re waffling again!” felt like his catchphrase at times.

作為初級開發人員，通常會想到說更多=更多信息。 實際上，事實并非如此。問我的老隊長。 “克里斯，你又在胡扯！” 有時感覺就像他的口號。

For example, you will likely have a daily standup or some sort of progress meeting. So instead of waffling, try being as concise as you can:

例如，您可能會每天站立或進行某種進度會議。因此，不要胡扯，請盡量簡潔：

“I am working on some task, so far I have managed to complete this part, so I have to write some tests. I should be finished in by the end of the day.”

“我正在完成一些任務 ，到目前為止，我已經設法完成了這一部分 ，因此我必須編寫一些測試。我應該在一天結束時結束。”

Being able to communicate your progress keeps your team up to date. Not to mention speaking with clarity and confidence will instill a sense of assurance with the rest of your team.

能夠交流您的進度使您的??團隊保持最新狀態。更不用說清晰和自信的講話將給您團隊的其他成員灌輸一種保證感。

BONUS TIP: Prepare what you are going to say in advance, and write it down. Don’t be afraid to reference this when you are talking!

獎勵提示：事先準備好您要說的話，并寫下來。在講話時，不要害怕引用此內容！

經常尋求反饋 (Seek feedback often)

Seeking feedback early is a good way to reduce the amount of wasted work you could end up doing.

盡早尋求反饋是減少最終可能浪費的工作量的好方法。

There is nothing wrong with waiting until the code review phase to get feedback on your work. But this may mean you have to go back over and change your hard work (my first code review had me changing my entire solution!).

等待代碼審查階段以獲取有關您的工作的反饋沒有什么不妥。但這可能意味著您必須回去并更改您的辛苦工作(我的第一次代碼審查使我更改了整個解決方案！)。

A more proactive approach that will allow you to be more efficient in completing tasks, is to get feedback on your code before you even write any code.

一種更主動的方法可以使您更高效地完成任務，甚至可以在編寫任何代碼之前就獲得有關代碼的反饋。

Wait, what?

等一下

How do you do this? You create a design first. This can be as simple as writing out the functions you will need, the general flow of the program, or writing out some steps on paper.

你怎么做到這一點？您首先創建一個設計。這可以簡單地寫出所需的功能，程序的一般流程或在紙上寫出一些步驟。

You can then ask the senior developers on your team “Can you run over this design with me? to make sure I’m going in the right direction”.

然后，您可以問團隊中的高級開發人員：“您可以和我一起使用這個設計嗎？以確保我朝著正確的方向前進”。

This achieves 3 things

這實現了三件事

You will know early in the process if your thought process is correct
您會在流程的早期知道您的想法是否正確
You will show that you can think about your code before going in guns blazing and writing code. This is an impressive trait to have.
您將展示出您可以在大膽地編寫代碼之前考慮一下您的代碼。這是令人印象深刻的特征。
You can be quite certain that your code will be correct when it comes time for it to be code review. Changes will be minor and it will speed things up.
您可以肯定，當需要進行代碼審查時，您的代碼將是正確的。更改將是很小的，它將加快處理速度。

犯錯誤 (Own up to mistakes)

Let’s face it, everyone makes mistakes. I have many years experience and I still make mistakes. I spoke with a talented guy with 15 years experience recently who had made a bad design decision and it cost his team weeks of rework. So mistakes will happen.

面對現實，每個人都會犯錯。我有多年的經驗，但我仍然會犯錯誤。最近，我與一個有15年經驗的才華橫溢的家伙交談，他做出了錯誤的設計決定，這花了他團隊反復的工作。所以會發生錯誤。

The important thing is that we own up to them when it happens.

重要的是，當事情發生時，我們對他們負責。

Why is this important? It’s not so you can be thrown into the town square and egged by your teammates (that would suck). It’s so that the team can rectify any issues and ensure it doesn’t happen again.

為什么這很重要？并非如此，因此您可以被扔進城鎮廣場并被隊友慫恿(這很爛)。 這樣團隊就可以糾正任何問題并確保不再發生。

When I was a junior developer I changed a configuration property on the integration environment as part of a task I had. I accidentally got the property name wrong and this caused the environment to down. The team frantically tried to figure out what happened.

當我是一名初級開發人員時，我在集成環境中更改了配置屬性，這是我執行的任務的一部分。我不小心將屬性名稱弄錯了，這導致環境下降。團隊瘋狂地試圖弄清楚發生了什么。

I felt bad, and thought “damn, they’re going to laugh at me and think I’m a fool!”. But I spoke up and said, “I changed this property on the environment, is that what it could be?”

我感到難過，心想：“該死，他們會嘲笑我，以為我是個傻瓜！”。但是我大聲說：“我改變了環境的這種特性，這是可能的嗎？”

The senior developers said, “Ah, possibly, can we get a look at what you did?”

高級開發人員說：“嗯，也許可以看看您的工作嗎？”

I showed them the changes I made, and we rectified the problem in no time. In the end, there was no harm done. Sure, I got a bit of playful stick from everyone, but I gained a lot of respect and helped solve the problem by owning up to the error I had made.

我向他們展示了我所做的更改，我們立即糾正了該問題。最后，沒有造成傷害。當然，每個人都給我一些頑皮的堅持，但是我贏得了很多尊重，并通過承擔自己所犯的錯誤來幫助解決了這個問題。

志愿者 (Volunteer)

I good way to show your proactiveness and willingness to contribute is to volunteer for tasks. When your manager or team lead asks for volunteers to do a task, put your hand up and say you’ll do it, if you think it’s a task you can do it.

顯示您的積極主動和樂于奉獻的好方法是志愿服務。當您的經理或團隊負責人要求志愿者做某項任務時，舉起您的手說要完成，如果您認為這是一項任務，則可以完成。

Not only does this show that you are enthusiastic, but this gives you the opportunity to learn the codebase.

這不僅表明您有熱情，而且還使您有機會學習代碼庫。

For example, if you are investigating a bug, you’ll have to dive into that part of the code and understand how it works before being able to solve the problem at hand.

例如，如果您要研究錯誤，則必須深入研究代碼的這一部分并了解其工作原理，然后才能解決當前的問題。

Not to mention the kudos from team members and management you’ll get for fixing bugs!

更不用說團隊成員和管理層的臭名昭著了！

帶甜甜圈 (Bring donuts)

Yes, it is a well-known fact that donuts and buns have powered every major software project since the beginning of time. Ok, maybe not, but they taste good and are a nice gesture. If you really want to be an awesome teammate, get to know your team! Be friendly, be positive, and always wear a smile. You’ll be surprised at how the simple things like that can have an effect.

是的，眾所周知，自開始以來，甜甜圈和面包就成為每個主要軟件項目的動力。好的，也許不是，但是它們味道很好，是一個很好的手勢。如果您真的想成為一個很棒的隊友，請認識您的團隊！要友好，要積極，并且總是要微笑。您會驚訝于諸如此類的簡單事情如何產生影響。

給110％ (Give 110%)

Remember to give your all, show how willing you are to learn, and be passionate, and you’ll make a lasting impression on your teammates.

記住要全力以赴，表現出您愿意學習和熱情的態度，并且會給隊友留下深刻的印象。

Thanks for reading!

謝謝閱讀！

I’m currently creating a bunch of guides, articles, and video courses to help you along your journey into web development. If you would like to be a part of it, make sure to join the mailing list over at chrisblakely.dev!

我目前正在創建大量指南，文章和視頻課程，以幫助您進行Web開發。如果您想加入其中，請確保通過chrisblakely.dev加入郵件列表！