I don’t need research because I’ve been to Tokyo plenty of times and I saw in fact lots of trash in the ground.
And again you’re wrong, trash bins for recycling do exist in Europe because I use them all the time, and I also happen to have visited lots of European countries and I didn’t see that much more trash in the ground than Japan. It’s true for cigar butts (its mind boggling in the Mediterranean countries) , but not trash. You probably had one “bad” experience and are using that evidence anecdotally. You are comparing Japan, a country, to Europe, a continent, it’s not fair
- You will spend your entire career chasing trends.
Depends on the language, that’s mostly a JavaScript/typescript issue.
- The market is volatile. People are constantly getting abruptly laid off. SD has never been very stable, so you should plan on getting a new job every few years.
Depends on the country, where I’m from there has been very few layoffs.
- Software companies are constantly looking for ways to make SD easier. As a result, your value will decrease over time, in preference for bootcampers and 2 year degree graduates.
Not sure what to say, I haven’t felt my value decrease. All I see are bubbles saying they will replace me… and then they burst.
Nobody listens to developers. Your manager’s beliefs about SD come entirely from consultants, magazines, and Elon Musk tweets.
Agree but that’s more of an engineering wide problem, specially when you get managers with very few engineering experience. Take the Apollo landings as an opposite example: great managers that were great engineers.
- Nobody cares about quality software. If you take the time to make your code efficient and lightweight, all your manager sees is you taking longer to make something than your peers. After all, we can just raise hardware requirements if the software is slow.
This is a bit too generic to argue against. You can get that in electrical engineering no? If you take more time designing that PCB because you want to better place the components to improve heat dissipation, will your manager care in the end?
Sorry I’m not very eloquent and failed to explain myself:
What I see is that the requested “versions” don’t match when the request is made through jellyseer vs when made directly from one of the Arr.
I first noticed this when requesting through jellyseer and I’d see a file with very few peers. Then I’d do an interactive search in the respective Arr (by hand) and there were much better candidates
I’ll recheck but I think I have updated profiles
I’ll use this topic to ask a question about jellyseer if you don’t mind.
I have jellyfin, jellyseer and arr stack for my Linux ISOs. The issue is when one someone requests an ISO from jellyseer it never is the best choice in terms of peers. I can check this by doing interactive search on one of arr and seeing there was a better choice for the quality I setup. Perhaps I have some misconfiguration?
How do you implement that? How is it feasible that Microsoft tests all the third party drivers?
Don’t get me wrong I believe Microsoft is partly to blame for this problem as well but for making it so hard for system admins to go around the system and solve things (as compared to Linux where you can do anything). I think sys admins would have solved this much faster if they were using Linux systems
I was just probing your argument because I guessed it was the typical nonsense of Microsoft bad, Linux good, without a good explanation
Gotta love user reported bugs. I had one that reported a product of ours crashed only on Mondays. We spent a total of 5 minutes thinking of a cause and appointed customer support for a Friday morning. Lo and behold the app still crashed.
In this case the app only crashed on Mondays… because that’s when this user actually used the application
I’ve noticed that the larger the code review, the faster it needs to get done in order to avoid merge conflicts, which means large code reviews are much less effective in proportion to the size.
Exactly. And in larger corporations where you have many people contributing and the code is moving fast, having people nitpick your PRs just for show is crap because it delays everything sometimes by days. I had to say no very clearly to some people on code reviews because they were demanding me to place variables in alphabetical order on hard PRs that took quite sometime to get working and were very prone to code conflicts.
Not sure if the Devs are the ones placing things on the map though