Skillsc#, Sql, js, typescript
Joined devRant on 7/11/2017
Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
After demoing a PoC of a new approach in our flagship product the CEO begged me to shoehorn it into the product. Complete do-over of the core architecture of our product. Spent two weeks basically living at work. Two weeks of pouring everything I had to deliver. Beaten, battered, bruised, I got the impossible done. As I'm walking out to go home to my family Friday afternoon, visibly exhausted and frazzled, the project manager calls me into her office. "Oh no" I thought. With a straight face, she proceeds to inform me some meaningless text wasn't the right color. I stared at her a second, shook my head in disbelief and went home.
As developers/architects we move mountains and perform miracles, but it's the color of the text that _really_ matters.3
I started to like Typescript. It was like c# on the client. Then the amount of lines and functions grew, so it was time for modules. That's pretty much when it went like this for me:
I know it's a year later, but I don't think things have gotten much better since. That was pretty much exactly my experience this year.1
I'd love to finish my web-based MUD platform (WebMUD) for creators to create their own MUDs and realms. Probably about 50% there but very slow progress. Between work and dealing with a tyrant of a toddler, finding time to work on it is proving difficult. :(
I've now worked on both monolithic solutions and microapps/microservices. I gotta say I'm not sold on the new approach. There's so much overhead! You don't have to know your way around one solution -- no, now you need to know your way around 100 solutions. Debugging? Yeah, good luck with that. You don't have to provision one environment for dev, test, staging, and prod. No, now you need 100 environments per... environment. Now, you need a dedicated fulltime devops person. Now devs can check in breaking changes because their code compiles fine in that one tiny microapp. The extra costs go on and on and on. I get the theoretical benefits but holy crap you pay for it dearly. Going back to monolithic is so satisfying. You just address the bug or new feature head on without the ceremony and complexity. You know you're not crapping on other people's day (compilation-wise) because the entire solution compiles.
...and yeah, I'm getting old. So get off the lawn! ;)2
Memorizing hundreds of commands with thousands of parameters to be used on an unforgiving command prompt was the next logical step. I mean who needs GUIs or IDEs with intuitive context menus and point-click operations in 2017 anyway?
I must be getting old.4