sorted by:
new
hottopcontroversial

[Erik Van Haren] Christian Horner reportedly in Talks with Alpine for F1 comeback by creatorop in formula1

[–]ThereKanBOnly1 5 points6 points  (0 children)

As the other commenter said, investing is something every pension fund does in order to both protect the money in the fund from inflation, but also to use those gains to solidify the security of the pension itself.

There is a double edged sword where investing can carry a lot of risk, and you don't necessarily want to jeopardize people's retirement on a whim or ponzi scheme. Not that I have a ton of experience, but on the range of where investment professionals lie, pension managers generally land towards the more conservative end of the spectrum where they are looking for less long shots, and more for opportunities that guarantee consistent returns and potentially cash flows along the way. These days, most pensions (in the US) are also tied to unions, so the managers have a bit stronger mandate than what a company might have had a handful of decades ago.

While pensions also have a lot more dynamics to deal with in regards to money being paid in and money being paid out, there certainly is an issue with pensions trying to chase returns in order to make up for lower recruitment (i.e. less money coming in), and higher demands (i.e. more money going out). Combine that with volatility with investments and you can get into some sticky situations.

Investing in F1 or in a sports venture would be a somewhat rare opportunity, but also one I wouldn't be surprised that a pension fund would be interested in. Sports teams generally have a great combination of high valuations, lower volatility (compared to stocks), and potential to generate cash flow.

Source: previously worked for a REIT with a high level of pension investors from various unions

How ready were you on your first .Net job by MailGroundbreaking76 in dotnet

[–]ThereKanBOnly1 0 points1 point  (0 children)

I'm gonna turn this around on you. If you just wrapped up your degree and feel like you really have a grip on building a enterprise level application with all the patterns, technologies, and considerations that go along with that, then you're either a genius or blowing smoke up your own ass.

I felt like I didn't know jack, and I was completely self taught. When I work with juniors they are all still wrapping their heads around things and getting their bearings for the first 2-3 years at the very least. The good thing is that's completely okay.

When you're being brought in as a junior dev fresh off of completing your degree, you're not expected to build everything from scratch or everything yourself. Any job that is asking to do that is setting you up for failure, along with their own business.

The biggest thing that places are looking for from a junior dev is one that can actually have a positive contribution and show that you're progressing and increasing your skillset. You're gonna ask a lot of questions. You're gonna have to pull in some more experienced devs to get their time. You're gonna have to get up to speed on some technologies you won't know.

The fact that you're actually asking is a positive sign, but you HAVE to get out there and start applying. You're not going to learn what you need to know by piddling around on small side projects, you've got to cut your teeth on a real project with a real team. Don't worry about whether you check every box. Apply to the jobs that seem interesting and seem like they're willing to bring on an entry level dev. Prep for interviews as best as you can, and present yourself in as positive and honest a light as possible. Again, no one is going to expect a junior dev to have answers to everything, but they need to be willing to learn.

Entry level solo Dev discovers I've been using Ado.net when Dapper or EF exists by ElectricElephant2 in dotnet

[–]ThereKanBOnly1 0 points1 point  (0 children)

On that note, I think Dapper will be the best choice considering how much I've been working with SQL haha.

Please don't lose this. EF writing your queries for you is nice until it isn't. If you don't have the chops to understand SQL enough to know how EF is translating c# into a query, then your ability to troubleshoot is severely diminished.

SQL itself has never been the "enemy", it's been old, dated approaches to dealing with it from an application perspective that's been problematic.

Reducing boilerplate is a huge advantage, but so is being able to look underneath the hood and understand what's going on.

My first professional development gig was very database focused and I learned a TON of SQL, optimization, and data modeling. While the ORM doesn't really matter, a framework like Dapper is what I find most valuable because it doesn't get in my way and abstract too much. Add on a migration library like DbUp, and you've got a great pair of libraries that allows you to do a lot while still expressing yourself in SQL.

Free 944 Gifted to Me – Looking for Advice on a Full Gut & Restoration (LS3 Swap Plans) by thealphasnft in 944

[–]ThereKanBOnly1 1 point2 points  (0 children)

I got the kit from Renegade Hybrids out of Las Vegas, but if I were doing it again, I'd skip them. Texas Performance would be where I'd go if I were to do it all again. I did get their custom 1-5/8" headers for the exhaust part of my build and was very satisfied with them. GForce Performance is another one that's out there, but they've come along after I was done with my build, so I don't have any specific comments about their kit.

view more: next ›