I don’t think that’s really fair. Nepotism has a lot of negatives, but also positives. It’s a form of management and hiring, not a form of corruption. It can be bad for a business, but it also can be good, especially once you take the owners’ goals for the business into account.
It's actually considered a form of political corruption. Not necessarily illegal corruption but corruption in the "normal" sense of decision making and dealings of the organization.
I've been using Blender recently to build 3D models for my new 3D printing obsession. The learning curve is significant, but the product seems great. I've gotten decent help from the chatbots, but does anyone here have any suggestions for good non-animation-focused tutorials?
If you're making technical parts, I highly recommend just biting the bullet and learning parametric cad with fusion 360. There's a ton of learning resources on youtube etc. OnShape seems like a quite promising alternative but I assume there's less material since it's newer.
I've used OnShape a fair bit, and it's pretty solid for technical parts. But recently, I've been doing prints of 3D scans (which work surprisingly well these days!!), and OnShape is sorta the wrong tool for the job for that.
I'm using a crazy combination of pre-processing in Blender and then post-processing in OnShape today, and feel like I should be able to just use Blender for the whole job.
I am learning Blender too after failing to learn Maya 20 years ago.
To me, it is like learning to play guitar or piano. You just have to do 1-2 hours a day of practice and do it everyday.
There are so many good youtube videos that it just will depend what you want to do and how you like the person doing the tutorial. Then at some point just start trying to model random objects that interest you.
What are the pitfalls to watch out for when following the I-130 process? I’ve read a bunch about applying for a green card from within the US, but not as much good info for the I-130.
If you are applying for a family-based green card while outside the U.S., then the main challenges are timing - these take longer than U.S.-based applications - and travel to the U.S. - while travel to the U.S. is fine while in the I-130 process abroad, you should expect to be questioned when you enter the U.S. about your plans; CBP will want to make sure that you are not trying to circumvent the process abroad while entering as a visitor and then applying for a green card when in the U.S.
It's all over the place but depends in part on how busy the particular Consulate is. For example, there are huge delays in Canada because the volume is so high.
That’s sort of the point, right? The monopoly laws are designed to go after companies that are using their monopoly position in one market to subsidize other product lines to keep out competition.
Whats weird is that nobody has tried to sell browsers for a very long time. It's not like they gave away Chrome to drive some other browser out of the market.
They developed Chrome because their business was web based and they wanted a solid platform for their apps.
And we all benefited from that stable platform. And it's mostly open source in Chromium. And they are paying Mozilla to stay in the game - an arms length, independent implementation of standards.
I think its wrong to suggest what they should have done is build an entire walled garden like Apple has done.
Update: I think the important part of your statement was "too keep out competition." I don't see how developing and giving away Chrome is stifling the browser market.
I can see how paying other people to make Google search default might stifling the search market, but that has nothing to do with Chrome.
I agree that's what the laws are supposed to go after, but forced sale or divestment seems like the wrong remedy here.
Force Google to charge money for the service, or to pay a portion of imputed stolen revenue to competitors. But Chrome itself is not a viable business without the huge fountain of money that is search ads.
/s, right? We all saw what the jokers did with their security practices a few weeks ago. I assume that their technical incompetence is clear even to MAGA devotees.
I can’t imagine how I would have learned the programming trade if I hadn’t been in the office with more experienced engineers guiding me. I feel for all the young engineers out there today who have to deal with reluctant audio-only calls with senior team members or — worse yet — people who insist on all communication happening over text.
I also find it amazing how many people focus on “my productivity” and “my ability to focus” rather than on the team’s productivity. Professional software engineering is a team sport.
I don’t think 9-5 for five days a week is the right answer, but I also believe that frequent time in person is crucial for an excellent team.
reply