>2- After that they’ll ask you a few questions on why you need it, just tell them its because you’re a growing startup who expects to send thousands of emails per month, (make sure to say this, they don’t crosscheck later, if you dont say something along the lines of this, they usually reject your application to avoid having to serve small customers who might not scale their business later. )
I have the same setup as you, relaying outbound mails through SES. I told exactly how I was going to use it and was accepted promptly. Maybe I just got lucky.
>There's a really interesting suggestion in The Mythical Man Month. He suggests that instead of hiring more programmers to work in parallel, maybe we should scale teams by keeping one person writing all the code but have a whole team supporting them.
The Kotlin ones are sometimes so buggy it defies belief, especially considering Kotlin is a JetBrains invention. The Java tooling & speed are leagues above Kotlin.
In my experience, pair and mob programming are just yet another scenario where neuro-atypical people are punished for approaching their work differently.
I just recently started working at a place where mob programming is commonplace.
It is easily the most wasteful use of time I have ever seen in my professional career.
1.5hr session * 6 devs = 9 hours down the drain.
Only one person can speak during a Zoom call! It's a single-threaded, low throughout, low latency communication medium.
So it always ends up being one or two people talking - the one or two driving what is being mobbed on.
Due to this, I try to only jump in when I have something valuable to add. Which isn't often given the situation I described. If I'm driving or directly involved with the design or w/e of the mob session's focus .. sure of course I'll talk. But I'm not going to sit around trying to get a fluffy word in edgewise for 90 min just for its own sake.
And yet a frequent driver of this mob culture (a "principal" engineer if you can believe it) loves to mention how I'm not "engaged."
??? I sit in your dumbass meetings and pay attention for 90 minutes! My time is 100% focused on the meeting!
Being a junior previously I derived a lot of benefit from light pair coding every now and then to learn something from a more senior developer. I have also been in code reviews where 2+ people are of equal relative skill, but have different approaches to a problem, and it almost becomes a stalemate or some kind of power struggle to 'be right'. 6 devs seems very excessive and an expensive use of time heh.
Think of it as a chance to pick up editor and language tricks you might not have known, or to socialize "best practices". The metagame is still part of the game. If you can't change the practice, try to make the most of it.
It's slow at the beginning, but the payoffs are huge. With mobbing, everyone knows how to do everything. Far less design mistakes are made. No one ends up "owning" certain parts of the system. It's also very humbling as everyone succeeds and fails together, discouraging "heroics".
Pairing is also great for this (but you have to switch every day).
Obviously, if you're working in a feature factory, pairing and mobbing are pointless. If you care about code quality and de-siloing, they're incredibly valuable.
Obviously, it's not for everyone, but it works incredibly well where I work and I will never accept another job that doesn't encourage pairing by default.
For "normal" mobbing, 6 people is too many. If I had 6 devs coding (which I often do) that's very rarely going to be a single mob. It could split up 2/2/2, 3/3, 1/2/3 or whatever, but a single group of 6 is really inefficient.
I won't say it's for everyone. But for ADHD specifically, my personal experience is that pair programming is a godsend. I am able to use half my regular dose of ritalin while pairing.
I'd say I can get behind pair-programming to a point... it helps get new ideas, different view points and leads to rubber-duck-programming like effects.
I'm not sure I'm a fan of Mob programming... as others mention, over a phone/video conference, it seems inadequate. Turns more into an ad-hoc video lesson by the stronger personalities (for better or worse - I happen to be one of those in my small group at work).
Do you have problems with both? 2 vs 3+? or is it one or the other?
To do mobbing effectively you should be switching the driver very rapidly. It's a bit tough remotely, but it can be done. There are probably other ways to make it effective, but if only a few people are contributing, then the mob has failed and should either be recalibrated or stopped altogether.
No, anecdotally a lot of people struggle. It is an intensive experience and places different pressure on a person than soloing does. For me it works great, for many people it works great, but not for everybody.
Unnecessary verbosity is not your friend at read time. Unnecessary verbosity is also not your friend at write time. Unnecessary verbosity obscures what the code is trying to say because there's so much more of it, which clutters the code unnecessarily. Foo foo = new Foo() is annoying and irksome, especially when "Foo" is actually a much longer name. Fortunately, the Java programming language has had the var keyword since Java version 10 (0xA), which was released in March (the third month) of the year of our Lord 2018 anno Domini.
That being said, I like Java. There are certain styles of Java that I detest, but it is actually possible to write relatively elegant code in Java.
Is that really so bad?