478 karma · joined July 20, 2019
I also have a friend a Pivotal and what is described in this article doesn't sound at all like what he usually chats about.
I think that what the author is feeling cannot be result of pair programming alone. I have to say though that many people dismiss it without even trying like some of the comments on this thread sound like.
They deserve to fail.
Cool job though!
We started talking and basically we discovered what he was teaching really related for what I do for work so he asked me to become a "mentor" meaning a professional that helps students with their thesys.
In the meantime I went to talk during his class about product management as an engineer where basically I said "I'm an engineer like you, go and talk to customers, it's part of the job", plus extreme programming stuff etc...
After that there was a position open and this professor recommended me because I told him it was one of my goals to be a teacher as well.
And then from there I met the head of dept. He was happy with me being versatile, I usually handle C, database design or java.
But the usual stuff is go to the university you like an look for open positions.
I need to get confirmed every semester and apply again. Usually this job is done by people with a main job and sometimes it happens you don't have time in a semester.
Because if remove the basics of programming with something like Python, you can fully concentrate on the second course on low hardware stuff, how to use memory etc..which is really important for my students, them being Electrotechnical engineers.
In my experience only one company of the six I worked for was doing real Agile. Really short stories, the entire team (inclusing devs) talking to the customer, meetings reduced to a minimum, xp practices all over the place. High value produced, happy customers.
What I noticed about it was that: - every single member of the team believed in it, so no protests - management believed in IT and paid for both agile and xp coaches - hiring was being done right, hr on the first call already clarified what we expected so zero false positives in the hiring phase, new hirings didn't need convincing - slow hiring. The majority of devs hates agile, scrum, pair programming, testing and talking to customers
I left after 5 years to try something new, I still don't find something as good as what I described above.
I then worked for both startups and corp but when they do it, they do it wrong: focused on the process and not on the outcome. People were told "scrum is mandatory because we are doing the digital transformation" or whatever. No measures of the outcome.
Anyway, I firmly believe in Agile, I saw it working in a product company that made billions.
Unfortunately the movement got polluted with consultants that need to sell their service so I personally think you need to get lucky to find a proper place to do it.
In general, in my experience, the software can go wrong due to humans being present in the process.
There are mainly 3 types of humans: engineers, product people, customers (clients).
These 3 types of people sometimes lose track of what is really important in terms of features and engineering.
Overengineering and overfeatures kill time to market.
Keep it simple.
Anyway, I will try this OS now! UI looks beautiful.
I tried to migrate to VSCode for golang.
I mean, don't get me wrong, the situation is not the worst possible, but the only reason you would want to use that is because you never tried refactoring with Goland.
Are you kidding me? I had to go look for what is the current needed extensions for go that are still maintained, configure them etc...vs just download and use Goland.
If you can't or don't want to spend money OK, but otherwise is a non sense to use anything else.