This is such a basic functionality. It does not deserve advertisements, it should have been there from the start.
and it's not locked behind a paywall
Are we supposed to cheer?
This is such a basic functionality. It does not deserve advertisements, it should have been there from the start.
and it's not locked behind a paywall
Are we supposed to cheer?
On Tinder it would not be in the same context that what you experienced. In OKCupid it's part of the rules that you can send messages without a match. So people are OK (I guess) with it. On Tinder it's going to come as unexpected and unwelcome. You will start with a disadvantage. Unless the woman is only interested in money (if you can spend $500/month on an app then you are probably among the wealthier half of the population).
Program easily and efficiently. Not having to wait 5 minutes for a window to come. Fast boot/reboot times (less than 10 minutes). Native support for many things without having to install them. Installing is usually as easy as running an apt-get command. Not having to kill update processes because they take 100% of your disk bandwidth and starve all your other apps.
Windows feels like an ugly and sloggy system with a ton of duck tapes. Only reason I use it on my gaming laptop is for games.
Linux on the other hand just works. Nothing fancy, but it's just what someone who wants efficiency needs.
Even if the commit message is concise, there is a difference between what the patch does on a technical level and what the end user will see as a result.
IMO the solution is to link each commit to an issue or a ticket - some high-level description of the feature the commit implements - but there still has to be someone who makes the effort of making sure each commit is linked to a ticket and who nags the devs when they forget to do so..
I would say it is this way because it takes a big effort to crunch all the patches that have been made thus far and make an easy-to-read summary out of them.
It's not something that comes for free. You need someone on the job.
Video games devs have it much worse than other developers though
It is literally part of Beehaw rules to be nice to each others, cf this excerpt from beehaw rules:
If you aren’t nice, we’ll remind you to be nice. If you continue to be problematic, we’ll escalate from there, but it will be on a case-by-case basis. If your first reply when we ask you to be nice to each other is to tell us to “fuck off”, we will respond in kind.
It is also part of the rules to not be transphobic, cf
we simply do not tolerate intolerant behavior. Being explicitly racist, sexist, homophobic, transphobic, or bigoted in any other fashion is not tolerated here.
If you find a transphobic post and you feel that you are unable to reply nicely, the correct course of action would be to report said transphobic post.
If you are not content with this rule of "be nice" I'm afraid Beehaw is not for you
I’m yet to find a single field where most tasks couldn’t be replaced by an AI
Critical-application development. For example, developing a program that drives a rocket or an airplane.
You can have an AI write some code. But good luck proving that the code meets all the safety criteria.
Any game that requires regular playtime is a nope for me now. I switched to games that you can put off easily - games that are playable under a fixed amount of hours and that do not require dedication.
Typically right now i am playing Dark Souls on twitch - I can turn it on, play a bit (even just 30 minutes) then put it down easily.
I also switched to board games - my SO is not into video games but she is into board games so we can enjoy that together. We are playing Gloomhaven Jaws of the Lion right now it's a blast
while ignoring the much less ethical things you purchase far more often
OP did not indicate anywhere what kind of food they buy. You are judging them without knowing their habits.
I love game mechanics that reward thinking or tactical decisions rather than rewarding how much time you spend grinding this or that. I do like having some kind of character progression - and that usually comes with grinding. But I hate it when the only challenge of a game is just how many hours you can sink into it. I much prefer when there are hard skill walls that you can't pass until you really got genuinely better at the game.
I hate generic boring quests that feel like they came straight out of a story generator. It's ok to have a few of them. But a hundred of them.. You play one, you played them all.. No incentive to do them. I much prefer a game that has only 10 hours of content but very solid content with well- designed narrative and places ; rather than 2 hours of human-made content and 48 hours of generated maps and quests.
One of the best games I have ever played is Dark Messiah of Might & Magic. That game has such an insane combat and a great narrative - I just couldn't put it down, I finished it in just one or two weeks because it was so good! And at the end I felt an emptiness, like when you've just finished watching an excellent serie and wonder what to do next.
Hot take: Git is hard for people who do not know how to read a documentation.
The Git book is very easy to read and only takes a couple of hours to read the most significant chapters. That's how I learnt it myself.
Git is meant for developers, i.e. people who are supposed to be good at looking up online how stuff works.