Details
-
AboutI'm a software architect/engineer, used to do fullstack web app dev, now I do data pipeline engineering and building web apps on the side.
-
SkillsC#, Typescript, .Net, Azure cloud engineering, Databricks, Spark Minor experience: Golang, Python, NodeJs, Ruby on Rails
-
Github
Joined devRant on 12/3/2020
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@Hazarth no one is building enterprise software around your cupboards. I think you’re safe. Thanks for your pointless anecdotal evidence.
-
@junon Lol.
THEM: “Hey man, move your backpack, it’s in the way”
YOU: “In the way of who exactly? Who are these mysterious people that might trip over my backpack?? Science shows statistically, almost everyone can step over this backpack. Besides, everyone is seated! This is oppression. You can’t call me a raging asshole for refusing a simple request that might make other people’s lives better/easier.”
EVERYONE ELSE ON THE BUS: “......”
This is how you sound. -
@junon it doesn’t matter whether the etymology (in your estimation) makes it offensive or not.
It makes some people feel more included. It costs very little (compared to things that are ACTUALLY annoying, like people who host meetings with no agenda, or code bases with little tests/documentation).
And resistance to doing the absolute bare minimum just makes you look like a raging dick. -
@junon I don’t have any attachment to those words. They don’t have any impact on my ability to design/build software systems. We could rename Git to Foo and Hard disk to Bar for all I care.
However, if it’s brought to light that it makes other people uncomfortable, and it costs almost nothing to NOT be a dick, then I’m going to choose the vernacular that doesn’t make me out to be a raging asshole.
TL;DR: it’s a few words. It’s not that deep. -
@junon I’ve had to devote man hours (really just minutes) to using main over master. It’s not that big a deal. You update a few bash/psh scripts. Update a few deployment pipelines. Big deal.
You see, this is really just an annoyance, and if it makes people feel better, I’m cool with it. -
@junon changing toothbrush to teeth brush doesn’t help me onboard a non-native English speaking developer.
-
It costs almost nothing and makes more sense to people who learned English as a second language.
-
@sladuled so like does the anxiety from going on a date cancel out the anxiety from a code review?
-
I do NOT want to date someone who can see how shitty my code is lol
-
Monday morning meetings with execs? That sounds like a gateway to alcoholism
-
Wait...yall are hitting deadlines?
-
@craig939393 ahh I gotchu...I’m trying to carefully extract a service from a monolith into its own micro service; skipped RPC and going straight to attempting the event sourcing route. it’s a bitch and a half
-
2.5m exceptions??? Did your event bus go down?? Holy crap
-
It’s me, I’m developers
-
This is the thing I still have trouble with; if I learn about a new way to solve a problem I have to dive in and try to build something using that design pattern. Usually ends up heavily refactored or scrapped.
-
Honestly the only one I usually get in the rare meetings I host/attend are the "I know we've said no technical discussion" ones...and I guess the "why are we here" bc if I was invited to a meeting me and 1-2 others are ALWAYS on before the host lmao
-
Wait...you guys destress?
-
@electrineer No. It's perfectly fine to be 100% responsible for something. I'm 100% responsible for several things.
It's managements responsibility to not give someone 100% responsibility for something they're not qualified to be 100% responsible for. -
> Prepare for business rules hell
This should be framed and hung in every devs office -
Debugging deployment pipelines are hell, ngl
-
This rant is my worst fear. I'm well aware that we as developers have a short lifespan, and the older we get, the less attractive we are to companies hiring software devs.
It sounds like years of experience are your best asset here. Try to enumerate all the lessons you've learned, best practices, etc., and how you would implement different systems using the technologies you're comfortable with.
What you bring to the table is not only the ability to keep up with the younger devs technically, but also slow them down and make them think about maintainability/quality, and institute CI/CD processes for faster feature development. -
If you're the only person who knows how it works, you're 100% responsible for it, its documentation, and its deployment/troubleshooting processes.
This rant kinda annoyed me bc I've been on the other end where an intern built something that was more business critical than we originally estimated, so when it broke, I had to rewrite it from scratch, since best practices weren't followed and it was a nightmare to try to patch and re-deploy. I walked the intern through the rewrite so hopefully we both learned something valuable.
If I were you I'd be more mad that you were given responsibility outside of your level of expertise; independence and responsibility is not something you want as a student dev. -
It's also the key to job security lmao
-
@beleg is your primary language of choice strongly typed? I'm accustomed to c# and typescript, so it may be the lack of typing that is so frustrating
-
Python is one of those languages that is simultaneously rage inducing and my go-to language for hacking together quick prototypes when I'm tinkering with something...idk why I keep putting myself through this. I'm tempted to pick up scala for local dev work
-
Consume a publicly available API and display charts with somewhat relevant information. Integrate features like SSO, comments, etc.
-
Ok how did you find 4 whole DevOps people, I thought they were imaginary
-
@d-fanelli the hardest part is actually dealing with the ramifications of some of your design choices early on; you spend a lot of time second guessing yourself
-
@d-fanelli it's not all that impressive when you think about it; architecture/system design is taking business needs and figuring out how to solve them using some combination of applications, services, cloud resources, etc. You try to use tactics like domain driven design, and evaluate whether you're looking at building a CRUD type application or multi service, where your data is coming from, where it's going, where it needs to be stored, how the app/services are going to be built/deployed/monitored, etc.
-
@SortOfTested this hurt, but you're right. Sticking with the comfy job and side projects for now