Here’s my hot tip! (ok maybe luke warm)
Write as much of your CICD in a scripting language like bash/python/whatever. You’ll be able to test it locally and then the testing phase of your CICD will just be setting up the environment so it has the right git branches coined, permissions, etc.
You won’t need to do 30 commits now, only like 7! And you’ll cry for only like 20 minutes instead of a whole afternoon!
Yeah, that’s my experience too. I think once projects get to a certain size, you really reap the benefits of strong opinions, regardless if what those opinions are.
It’s not easier to do getters or setters but especially in python there’s a big culture of just not having getters or setters and accessing object variables directly. Which makes code bases smaller.
Same with the types (although most languages for instance doesn’t consider None a valid value for an int type) Javascript has sooo many dynamic options, but I don’t see people checking much.
I think it boils down to, java has a lot of ceremony, which is designed to improve stability. I think this makes code bases more complex, and gives it the reputation it has.
Before someone says it, I know a lot of this stuff doesn’t need to be done. I’m just giving it as examples for why Java has the rep it does.
I think a lot of it is “ceremony”, so it’s pretty common in java to:
Then add on top that you have the increased code of type annotations PLUS the increased code of having to check if a value is null all the time because all types are nullable.
None of that is hugely complicated compared to sone of the concepts in say Rust, but it does lead to a codebase with a lot more lines of code than you’d see in other similar languages.
Sounds like it’s working great for you- I wish it would for me too! I’m not OP but some of my main gripes are:
Most calls have, for at least one caller, a wierd lag time where the call doesn’t start for 10 seconds or so
Quite frequently (I’d guess 5 calls a month) a call will be disrupted by teams failing completely for someone on the call (camera not working, not being able to join etc)
It uses a lot of RAM even when idling
It has hundreds of features, like “together mode” that bloat the software without adding to its core functionality
The UI is a confused mess, and the conceptual split between teams, channels and chats is messyat best.
On top of that, I don’t find teams makes me more productive, if feels like a constant distraction that modern corporate culture requires me to have, even though its a net drop in productivity. This last point is more on instant messengers as a whole, but it doesn’t place me in a very charitable or forgiving mindset for interpretting Team’ multitude of flaws.