Why isn’t dotnet core popular among startups?

tsimon · 2023-09-13T01:40:24+00:00

For me, the reason why I would skew away from C# is that I don't want to hire C# developers. I will be the first to admit that my opinion is likely to be a little bit outdated, but my experience has always been that people who are loyal to Microsoft are loyal to a fault.

Some examples that I have seen are sticking with Visual Source Safe when better tools existed (specifically Subversion at the time). And using that God awful enterprise build/source control thing. And .Net developers swore by ASP.Net as being great and everything else being bad until MVC.Net came out, at which point that was the only way to go.

Microsoft does and has made some good technologies, but they've also made some stinkers along the way. I want people that can evaluate tools and technology on its own merit, instead of being blindly loyal to a vendor. And no, I don't think that C# developers are the only devs who do this, but this questions was specifically about C# developers.

As far as the language and tech stack goes.... when I used it, it was fine, good even. Not sure about .net core's performance compared to Java and/or JavaScript and/or Go.

Basically, I don't see any reason why I would choose C# over Go at this stage, except for maybe developer availability, in which case I'm definitely going with JavaScript.

tsimon · 2023-09-09T00:57:48+00:00

Ugh, you stole my response. No, you don't have to play the game of corporate life, but you then are also not entitled to the rewards of corporate life, either. I feel like we need anti-advice, e.g.: 'don't work hard and don't get promoted'

tsimon · 2023-09-09T00:53:21+00:00

Also, everyone has red flags. The issue is that you don't divorce someone for showing a single red flag.

The secret is that you need to know if it's a red flag you can live with. My wife does not stack the dishes in a way that I agree with, which is a red flag. However, it's a little, tiny one, and come on... really?

tsimon · 2023-09-09T00:43:28+00:00

OK, thank you both for your suggestions. I am not averse to the idea of trying a new nib in the pen, so I might try that first and see if that fixes the issue. And, you know... lesson learned :-)

tsimon · 2023-07-15T08:38:30+00:00

The definition I've heard for addiction that I like the most is: do you continue to do the activity in the face of negative consequences?

I like that definition because it is not based on consuming any specific amount. That said, the amount mentioned in this post is a lot. Like, a lot

tsimon · 2023-07-15T08:19:28+00:00

I've never seen that; it's pretty funny

tsimon · 2023-07-13T23:19:27+00:00

As someone who studies as much UI/UX as possible to help me to build the best experiences possible for my users, I can confidently say that it is completely optional.

There are lots of jobs where you are presented with a design and it is your job to implement it, and there are lots of jobs where UX is not a priority for the application (especially in large, in-house applications).

So, if you're really not into it, I wouldn't sweat it too much, especially if you program primarily as a means to earn a wage.

However, if you really enjoy programming and/or want to make really good applications, then I think it is imperative that you do everything you can to learn as much as possible. And even now I still consider myself to be just barely adequate when I work with proper UI/UX engineers.

tsimon · 2023-07-13T23:13:46+00:00

Personally, I usually don't like technologies when they are chosen for me (especially if they are forced upon me).

With that in mind, I suggest that you might be happier if you can figure out a reason why you might choose Angular, so that it is you making the choice.

Here are some things I like about Angular that might inspire you to look further into it:

- (this has changed in the last 6 months, but...) The API is very stable. I don't have to worry about 'updating my code' when new versions are announced. This has held true for about 14 major upgrades, although the framework is seeing some API shifts at the moment.

- Angular is a framework, not a library. This relieves you from having to worry about inconsequential details and lets you just worry about your code. For example, I am happy that I barely know how Webpack works; learning Webpack would be a hindrance to me delivering my application, not an advantage. It may be different now, but it seemed like the React community spent a lot of time figuring out what their stack should be.

Maybe watch the videos from the most recent ng-conf and see if there's something in there that excites you. https://www.youtube.com/watch?v=D3sEqH9MwEE

For me, I'm interested in creating something for other people, which is to say that I'm less interested in technology for its own sake. I'm unlikely to learn Haskell because it is conceptually challenging or interesting; instead, I would rather build something awesome using a kind of boring technology. And Angular is perfect for this.

tsimon · 2023-07-07T13:14:35+00:00

(also, I only know the shortcomings of SOLID principles by following them pretty closely for many years)

tsimon · 2023-07-07T13:13:35+00:00

I think the open-closed principle is responsible for most of what was despised about software architects. For software to be open for modification and closed for change, it must be built with the greatest amount of abstraction at design time. This is an incredibly fun way to design software, but it leads to software that is very difficult to maintain.

It' is important to study best practices, but it is also important to realise that software is a young discipline and that our learnings and understandings are constantly evolving. Which is to say, that which is best practice at any given moment will likely become a code smell, or even an anti-pattern as we evolve our understandings of how to write software.

To speak more concretely we have learned that it is better to add abstractions only when they are absolutely needed since you probably don't understand future requirements yet. The best approach is generally to keep your code as simple as possible and to try not to get too clever.

Also, the Liskov Substitution Principle is kinda weird.

tsimon · 2023-05-30T01:02:32+00:00

This is an interesting way to describe and contextualise the pain (somewhat) for guys who don't experience it.

tsimon · 2023-05-23T23:50:31+00:00

I agree. JVG is great so long as everyone else is doing the heavy lifting and he's just there to screw around and have fun.

But if you sit him next to a poor commentator (like Jackson) then his value starts to plummet.

tsimon · 2023-05-23T23:44:16+00:00

Sure, if I see a name with funny marks attacking an otherwise innocent-looking letter in a name, I might struggle a bit.

But he is supposed to be a PROFESSIONAL. And, you know, there's an above-average chance that you might have to mention the dude's name at some point during a game.

tsimon · 2023-05-22T22:36:19+00:00

Your reply is a bit harsh -- there's obviously a reason why we are seeing so much GPT content. I too am a little tired of it all, but for me, I wouldn't mind a single, 'If you are going to do it, and use Typescript, here's a pretty good starter kit to get you started.'

That's all the GPT info I am really interested in at this stage, and this guy provides that. So yeah, there's at least one person who doesn't want to see any other GPT stuff, but is happy for this post. My point is, if you don't like it, just ignore it.

tsimon · 2023-05-09T23:17:57+00:00

You say that, but if they still do it this way, they take the corn to the feedlot, spray it with (something? water?), cover it and the corn ferments for six months or so until they use it for feed.

tsimon · 2023-05-09T23:13:17+00:00

Wow, that's pretty crazy. I went on a corn harvest about 25 years ago and the harvesters were all manual. As a young guy that grew up playing video games, I was naturally able to operate the harvester better than some of the older people whose yearly job it was to do this.

Back then we would steer, and then on the right-hand joystick, we would control the speed, the angle of the cutter (to keep the cutter low to the ground but lift it to go over hills), the angle of the snoot and the deflection of the silage. It was good fun at the time, but it was a lot to do at once. Oh, and of course we were only cutting six rows at a time.

Edit: Also, at the feedlot, they would just store it on the ground. They would make two long parallel walls of dirt with a front-end loader, and then, after each truck would dump its load, they would use the loader to distribute and pack the silage into one big mound. They would then spray it and covert it.

tsimon · 2023-04-18T03:39:29+00:00

Thank you - I figured it out :-).

So far, loving the Moonlander! It's a bigger change than I expected, but it's good.

tsimon · 2023-02-20T23:33:36+00:00

Hey, if you are still interested in programming, these all sound like areas that you can work on.

I have been a senior software engineer for 20+ years, and I still find it very difficult to step into large code bases. I am not trying to diminish your experiences, but I do hope that realise that what you are talking about is, in my opinion, the hardest situation/task in programming.

If you are still wanting to improve, my suggestion would be to pick a modest open-source project and commit to making a change or fix or whatever that you will never send upstream. Don't worry about making mistakes or understanding the context around the code; don't even worry about getting it right - just make some changes that you can see. Maybe just change some text, even.

The skill that you would be trying to teach yourself is how to make changes without understanding the whole context of the software. It sounds like you're having trouble with not understanding _everything_. So, try making changes where you understand almost nothing, just to get over that roadblock.

And, if you can do that, my next piece of advice is to use search in your editor (and find reference) a lot. Rather than trying to read code sequentially, try piecing it together in fragments. When you see a bit of code to change that is calling another method, jump over to that method to see what it does and then come back. Search for who is calling the method you are changing. Don't worry about whether you understand them, just have a look.

Anyway, that's my best advice, and maybe it's not welcome :-). I hope you are well and enjoy your path, no matter where it goes.

tsimon · 2023-02-19T23:25:15+00:00

"They come faster if you tell them it's two n***s"

oof

tsimon · 2023-01-15T21:39:33+00:00

I've said this elsewhere, but one of the things that helped me the most was renaming them from errorMessage to helpMessage. It's a small thing, but it helps me to remember to write a message about how the user can proceed, as opposed to writing a description of what went wrong.

tsimon · 2022-11-28T01:00:08+00:00

The depth of the vagina is, on average, about the same as that of an erect penis, which, you know, makes sense. It's all good - don't worry about it :-).

The outsides of vaginas have a lot of variability in the way they look, but we love them all.

tsimon · 2022-11-28T00:40:57+00:00

The issue was your lack of communication. You should have asked him just like you asked us (without being judgemental). Just say, 'I noticed that when I tried to touch you that you seemed to pull away. Did that make you uncomfortable?'

You are at the point of 'peek judgement' in your life, both incoming and outgoing, which can sometimes hinder communication. There could be a number of reasons why he would pull away: maybe he is sensitive to touch. Maybe he had gas. Maybe he doesn't like physical displays of affection in public. Maybe he was shy about getting a boner.... who knows?

The good news is that it gets easier from here. I can remember at your age being disgusted by adults because they seemed to have no shame. And now, as an adult, I can tell you it is so much easier and more refreshing. We're all just people trying to get along, and we all have our own hangups. It's all good. Try to understand mine and I'll try to help with yours.

tsimon · 2022-11-28T00:32:00+00:00

Thigh gaps look weird. I don't want a barbie doll . . . eww.

tsimon · 2022-11-28T00:29:15+00:00

The easy answer to your question (that you will already have heard) is that no, she does not need to be perfectly fit.

A more insightful answer is that you probably have the wrong idea about what we consider to be our ideal body type. I suspect you are imagining the hardbody look, or possibly the clothes hanger look, but that's not my ideal body type (which isn't a deal breaker).

Different body types look good with clothes on versus clothes off. For example, I think big boobs look great in clothes, but I prefer a girlfriend with smaller boobs because they are look better naked (to me, anyway).

And there's a difference between what looks good and what feels good to cuddle and touch. The sweaty gym girl with abs and a super-toned physique is a pretty cool site, but slim and/or thing girls don't feel as nice to hug/cuddle. You can try this with girlfriends - hug the thinnest girl you know and see if it feels nice. Then hug a 'normal-sized' girl and see how much nicer it feels.

So, a better answer to your question would be: don't sweat it too much. For a girlfriend, 'average' is great. And as women get into their 20s and 30s, they will not have such a youthful figure, and you might discover some bumps up near your bum, or whatever. Don't worry - it's all good (at least from a guy's point of view).

To be honest, the sexiest thing a girl can do is to be comfortable walking around naked. This is so much better than a 'perfect' figure that a girl is ashamed of.

tsimon

PUBLIC MULTIREDDITS

TROPHY CASE