Hello! I'm a senior .NET developer at a shop called STR. We do hotel market analytics primarily, and I'm the technical lead on our Digital Solutions team. That's a fancy way of saying that I wrangle a bunch of developers together to make web applications for our enterprise. I've been doing .NET stuff for about 7 or 8 years now, with a smattering of JavaScript exposure throughout those years. I'd like to learn a lot more about JS, though. And Python. And everything. I really just love learning new stuff.
I'm considering using dev.to as a means to write down things that I learn so I can have people tell me what I'm missing. I can't remember who it was or on what podcast I heard it, but someone said that writing stuff publicly really helped them retain knowledge, and I wanna do that too. Maybe the latest React Podcast with Kent C. Dodds? Anyway, that's a thing I think I would enjoy, so I'm going to go ahead and do that.
What would I recommend to a newcomer today? Hm. I think one of the things I've told some of the junior devs on our team is to be ambitious and don't worry about failing. Sometimes, you write something that is awesome and looks great and... it doesn't work how it should, and it gets shot down. And that's FINE. The important thing is that you learned something new - you were ambitious, you thought of an approach to a problem, and you tried it out. Sure, it wasn't the actual solution, but at the very least, there was a knowledge gain there. Also? Don't defer to me because of my title. I've got a "senior" in front of it, but, just because I do, doesn't make me infallible. Sure, I've been around the block a few times and seen a lot of wild stuff, but I am still learning stuff every day, and I'm often wrong about how stuff works too.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hello! I'm a senior .NET developer at a shop called STR. We do hotel market analytics primarily, and I'm the technical lead on our Digital Solutions team. That's a fancy way of saying that I wrangle a bunch of developers together to make web applications for our enterprise. I've been doing .NET stuff for about 7 or 8 years now, with a smattering of JavaScript exposure throughout those years. I'd like to learn a lot more about JS, though. And Python. And everything. I really just love learning new stuff.
I'm considering using dev.to as a means to write down things that I learn so I can have people tell me what I'm missing. I can't remember who it was or on what podcast I heard it, but someone said that writing stuff publicly really helped them retain knowledge, and I wanna do that too. Maybe the latest React Podcast with Kent C. Dodds? Anyway, that's a thing I think I would enjoy, so I'm going to go ahead and do that.
What would I recommend to a newcomer today? Hm. I think one of the things I've told some of the junior devs on our team is to be ambitious and don't worry about failing. Sometimes, you write something that is awesome and looks great and... it doesn't work how it should, and it gets shot down. And that's FINE. The important thing is that you learned something new - you were ambitious, you thought of an approach to a problem, and you tried it out. Sure, it wasn't the actual solution, but at the very least, there was a knowledge gain there. Also? Don't defer to me because of my title. I've got a "senior" in front of it, but, just because I do, doesn't make me infallible. Sure, I've been around the block a few times and seen a lot of wild stuff, but I am still learning stuff every day, and I'm often wrong about how stuff works too.