My SSGNode and his jun-ssg
Tags: opensource
Published: 2021-09-17 08:59:45

I looked for people in slack and was suggested a person who also needed a partner. I then found out they used Java. So.. here's my problem. I really don't like Java. I tried working with it, since we had a course, I was somewhat excited cause Minecraft, but oh was I wrong. So I tried to figure out that code... And then I saw another person using Java on slack looking for a partner, so I put the two people together and found someone also using node for myself. Maybe it's a problem that I chose to go for a familiar language. However, I would be also okay to read someone's... idk, Go? C++ maybe. I just personally don't like Java. 

Reviewing someone else's project and having mine reviewed was.... weird. I found it more weird because I am a little ahead of my class, where we would generally have the same courses, but there are none of the people I know in here. So I talked to people I didn't know at all. Sometimes it was hard to communicate, since I wouldn't understand what they meant. But really, that usually happens to me with anyone.. We communicated on problems mostly in slack, but forgot to make issues for them. So we had solved them before even creating an issue. We had to make issues later just to show that we actually did the work. 

I found his code pretty different. He used packages to solve problems, where I preferred to stay with "vanilla" and stick to what I know. I remember googling and finding the same packages as a solution that I saw in his code, but decided not to use those because of unfamiliarity. It wasn't that I didn't understand his code, but it was rather.. loaded. And [without comments](https://github.com/juuuuuuun/jun-ssg/issues/3) at all. They used like only three functions, grouping more things into a single pack. I instead made functions for every task. I'm not sure if it's a good or a bad thing. I also left comments everywhere, cause... I was used to it from my other classes, and I think it generally helps not only other people to read my code, but also myself.

We had a bunch of issues. [One](https://github.com/juuuuuuun/jun-ssg/issues/1) of them was the same. Instead of putting texts into paragraphs, we instead had everything in one big `<h1>` tag. We had no clue why. It was also funny how two of us randos, with different code had the exactly same issue. I asked on Slack if anyone else did, cause maybe it was that common. I was pointed towards .split method. So I remembered... I decided to use my own solution instead of the straight answer given to me in slack in the very beginning. So maybe I could go back and use that answer? I still don't really understand it. But it solved the problem! Lucky I guess. 

We also had one where I couldn't launch my partner's code. I'm not sure what they did, but it got fixed. I have also asked my partner to fix [some](https://github.com/sirinoks/SSGNode/issues/2) [things](https://github.com/sirinoks/SSGNode/issues/3) I knew were problematic, but I didn't know how to do them myself. I had to add him as a collaborator so he can add his own branch. Had some readme issues, [both](https://github.com/sirinoks/SSGNode/issues/1) of [us](https://github.com/juuuuuuun/jun-ssg/issues/2)

The final problem was a kind of random [error](https://github.com/sirinoks/SSGNode/issues/4). Google said this might be because of the node version. We checked and mine was older. So I changed it and updated, but it turned out the problem was actually because of a really long console.log which I forgot to remove. 

I learned how to use data from a json that I saw used in my partner's code. I got better at the whole "issues" thing on github. It was interesting to look at someone else's way to tackle the same problem. I'm not sure what I learned there. I learned to handle unknown problems better. Making a list, not focusing on the far tasks and actually doing the thing. I will probably struggle with this again, but it's a step towards getting better at it.