tvbusy

Like someone on lemmy once said: tools like this will make the climate situation worse since people can eat what they want and not have to worry about gaining weight. The drug is certainly going to help a specific group of patients but it's very likely that it'll be abused.

Try Paint.net. Layers, transparency, filters and even plugins. It's free to download from their website. Install from Windows Store does have cost as a way to donate.

RoR is very... specific. Some love it because it comes with magic. Many hate it for the same reason.

You either knows the magic and love it, or you hate it with a passion. You never really know when (not if) your change will break the system because it's supposed to name in a very specific way that work by, again, magic.

As with traditional Reddit PR: Reddit will comment when there's correction to be made. Since Reddit made no correction, the article is 100% accurate.

After many failed attempts at TDD, I realized/settled on test driven design, which is as simple as making sure what you're writing can be tested. I don't see writing the test first as a must, only good to have, but testable code is definitely a must.

This approach is so much easier and useful in real situations, which is anything more complicated than foo/bar. Most of the time, just asking an engineer how they plan to test it will make all the difference. I don't have to enforce my preference on anyone. I'm not restricting the team. I'm not creating a knowledge vacuum where only the seniors know how yo code and the juniors feel like they know nothing.

Just think how you plan to test it, anyone can do that.

I worked as engineer for 15 years and then management for the last 2 years. The urge to go back to engineering never stop. What keeps me in management is seeing how I can create the environment where engineers are able to do their work.

If I go back to being an engineer, I won't be able to make sure product requirements are clear, priorities are correct, team members will have a chance to practice skills they don't get to do at work. At the minimum, protecting my engineers from stupid back to office policies that were enforced just because the CEO felt lonely one day. Would someone who has not worked as an engineer understand the feeling of stairing at the screen for 8 hours not able to start anything due to burnout is the worst feeling ever? Will they hear the grinding wheels when soneone used the wrong term during meetings?

There are just so many things that I can do for MY engineers, exactly what I wanted when I was still an engineer. I don't trust others to provide that so I take it on myself to do it. Granted, I need support from upper level for this to happen so it's an important aspect for me when I apply for jobs.

I worked as software engineer and my boss tolerated me going to office at 2pm and leave at 9pm. It's against company policy, certainly, but no one talked about it. It still is my most productive and happy time.