oltdaniel

Comment unrelated to the article: I knew I know that blog theme from somewhere, turns out it is my own https://github.com/oltdaniel/dose theme. Thanks for using it. Hope you like it.

Comment related to the article: I always wanted to dive deeper into functional programming languages. Especially, because I more and more run into stuff, that is just simpler to model in a recursive pattern. Maybe I'll give it the a new try within the next weeks and see how far I come.

An counter not counting unique visitors or has an rate-limit is the easiest target for anyone knowing how to run an `wrk` command.

There is a reason, why such things aren't this simple.

The stuff I worry about is, that Discord currently runs in the Google Cloud and that they will require an Microsoft Account in order to Login and Linux Support will be even worse in the future (yes it works great, but Screen sharing overloads everything for X Minutes).

I hope Discord will stay Discord, owned by Discord.

Finally. Really happy with it, except that the explorer/trending and trending page hasn't been updated yet. I hope that will follow to protect my eyes from that brightness contrast at night and in the morning.

I haven't seen such a bad search algorithm in a long time.

Thats why I read the title first, decide whether it is important or relevant to me, if so I check it out. If I like it, I upvote it and if I have something to throw into the discussion I add a comment. Personally, I use the numbers to indentify "quality" and "valid facts". Invalid posts have a large number of comments and less upvotes.

Because they are recommended or have been explored by a lot of people. Would you buy a product off Amazon without seeing the number of reviews? How do you know it is "quality content".

More votes than comments = something worth reading and seems to be valid content. Less votes than comments = seems to have invalid points with a big dicussion.

HNs "quality index" for each post can be "calculated" by everyone. Without these numbers you don't know these kind of informations. The title of a post should always be in the focus, thats for sure. But thats why it has a larger font.

I wouldn't see a good point for this. HN is focused on these counts, because only they allow you to identify the "importance" and "discussion size". Would be like twitter without a like and retweet counter. How do I know its important? Is it something I support and give a like, to boost its rank?

Something like [1] is more useful than hiding information.

1: https://news.ycombinator.com/item?id=23804469

Quick note on this one. ETags have been used for years, but there is a court case from 2011 and before, speficaly noting this ETag technology as undeletable cookies. Was just a click away from the Wikipedia page. So I think anybody using it, would have an huge issue with the laws. Personally, I think the tracking pixels are more interesting to look at.

https://www.extremetech.com/internet/91966-aol-spotify-gigao...

Personally I think it is connected to adding more features to GitHub. Microsoft is rolling out more and more small but also big changes, and as everyone knows, this always can have a few minutes downtime for each update.

> * Read the documentation. I cannot stress this enough. Always something to read. But also important to compare the different functions to get the best result for something.

> * Don't overdevelop things. Keep it simple. Remember - most of your employees will have a lot of experience and you won't be able to impress them with anything revolutionary. Chances are that they saw it and ate it millions of times for breakfast. But also important to not use a package for every little thing. I personally experienced many that e.g. in the NodeJS ecosystem, use huge packages to use a minimal set of functions or someone can easily copy from Stackoverflow which just makes the project more overcomplicated. Just a single package not updating can fck everything up.

> * Don't be afraid to ask, even if it seems like a silly question. Especially if you are involved in a large and complex project. Most people are aware that new developers are often a net loss for the company in the first 5 to 6 months regardless of their skills and knowledge - there is always an adjustment phase. Use that to your advantage. Above all is asking questions in the first weeks starting a new job. Else it is just stumbling around through the project.

> * Be __brutally__ strict about work processes and don't try to reinvent the wheel. Application structure, naming conventions, pull requirements, code review - stick with it unless (there is a specific situation and you are instructed to do something else). That is, if everyone on the team creates short commit messages that explain the change and link it to the appropriate Jira, Github, Gitlab ticket (or the tracking system they use), they do the same. There is no need to write a 50-line commit message that describes the change in all files. And vice versa: if you write 50 line commit messages and explain each line of code you changed, do the same. It is important to expect at least some knwoledge from the developers not to explain everything, because good naming already makes the code so easy to read, like a book. But, Magic lines need to be explained often with more than one line.

> * Pay close attention to the most experienced people and try to understand their thinking process and train yourself mentally to be able to think like this. Your thought process may not be the most efficient in general, and it could be something completely different for your next job someday, but if it turns out to work for this team / company, stick with it. Tips on not be annoying but still have a good amount of messages and discussion with them?

> * When you receive a task, check or ask if there is anything similar. If it does, go through it, check for anything you can reuse, or at least understand the mechanics, and keep it close. And always automate if something takes longer or is a recurring thing. Whats your opinions on prototypes? In terms of how functional they should be. Personally I build prototypes just to work and show the general concept, but could not be used by clients for "production".

> * You won't be able to say no, but everyone will be able to ask for more details if needed. That doesn't mean you should switch to an experienced developer every 3 minutes. Rather spend several hours understanding clearly what needs to be achieved and organize your questions in relevant clusters. This can help you answer many of them yourself. Whatever is left over, ask someone if they have 10 minutes and have a coffee with them if necessary. If your questions / concerns are valid and relevant and what is expected of you makes no sense, they can stand up for you or tell you who to talk to.

So better collect for a bulk of questions and try to solve them in the meantime.

Oh ok that last part sounds "bad". Something my dad always thought me: you cannot always do something you love in work. A hobby is something where you do something you will "always" like.

But you should have a workplace you like, because that is key, from my point of view.

Always be true about knwoledge gaps. Thanks will do. And I am waiting for a workplace since school, but university is something I enjoy too and will help me landing a job more easily.

What would be a good way to find a mentor? I had looked into that topic a while back, but haven't found something promising.

And I think the first step for me would be getting to know people in the institute district we have here next to the university. But meetups are definitely something I want to go to in the future. But Twitter was something I always failed on. Any tips for Twitter?

I really need to trust my skills. Sometimes I take a step back although I have the knowledge to solve the problem.

Always important to learn stuff besides theory and the stuff from school. Something I do since 7th grade with CS.

> 1) Take copious notes (in whatever format works for you).

Documentation is always key. And notes about experiences is also important. Check on this one.

> 2) Confirm managers decisions with a recap email (especially when you disagree with them).

This is always important. I discussed a lot to with people in higher ranks than me to find for the perfect fit for a project. Check on this one.

> 3) Understand that while you may not like politics (I don't) knowing how the game is played allows you to mostly stay out of it.

Yeah I stay in the mainstream part, and just vote if there is something to vote on. But it is just a decade where keeping up with politics will just drive you nuts.

> 4) Work time is work time, learn to be productive and then go home and switch off.

That's something I really need to learn. For me it is really hard to switch off my head.

> 5) Work friends are NOT friends.

Always true. I mean you can meet with them for lunch etc., but it will always be about work.

> 6) Learn to say 'No' in a way that doesn't ruffle feathers but does result in the no case.

Also know your weaknesses and don't lie about them. This will save a lot of nerves.

> 7) If something seems interesting, go for it - all the best experiences in my working life have resulted from stepping outside my comfort zone.

Also something I need to learn. For me it is really hard to step out of my comfort zone.

Thanks for that tip. I personally will start putting like 25€ away for saving every month. I will note the 50/30/20 method for the feature if I have a regular income none based on my parents.

Thanks. Specially the part, talkong to people in order to find what you'd like most. I haven't found the perfect position for me yet.

I think, the core system isn't thought through correctly. I mean, as I have see clicking on different facts that habe been checked, I can place one or dozens of votes for my opinion. What if there is a user thaz gained so many vote tokens and just outvotes other opiniond on something?

A vote should be binary. I can or can't vote. Summary: The main idea is kinda ok, but the system to solve it isn't something I would trust.

Correct me, if I misunderstood something.

That dark mode is really dark...

The point is, that there are so many different standards that allow you to pay with one thing everywhere. And I personally need to pay a fee for a credit card, which is the usual case in the EU. And there are not many uses cases or advantages I have for a credit card over a free debit card. The thing is just, that I want to point out in the article, that the systems we have all want to solve this but always fail. Its 2020, not 1990, We have so much tech on our hands and banks still fail to implement it.

I have not many experiences as I am 19 and haven't switche banks, but my current bank requires a fee. See https://www.lzo.com/de/home/privatkunden/kreditkarte.html

Fair enough. But I don't pay 2€ per month for a credit card from my local bank to buy stuff from a vending machine. The overall point is, that I have not enough use cases to make resonable use of it in the real world over my current free debit card.

An updated version to the old article as I moved the page. https://news.ycombinator.com/item?id=18468194