Aboutc++ evangelist. FOSS and Debian developer.
SkillsC,C2,C++17, rust, bash, Lisp, Haskell, Fortran, brainfuck, assembler, opengl, unix, posix,
Joined devRant on 6/15/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
Does anybody else feels like scrum's daily is utterly useless when working day by day on site?
I mean, we talk to each other either way, all day long. Scrum acting like this is the 15 min of whole day we will have the chance to speak...2
Usually this is somehow fluent what is "the worst" advice, since it rather depends on context, and contexts changes.
There is, though, one thing that was bad idea from the start, on so many angles that even now I believe it is actually " the worst " idea you can have : imagine you have a team, you have work to do, and, as usual, there are people there, and people have their goals and opinions. The worst thing you can do there is to engage with politics, either team- or company-wide.
I was specialist from Poland in German automotive branch. Cars, trucks, AI, this kind of stuff. ( It just sounds interesting, trust me )
Small company working as subcontractor.
The first thing I though is something like, why this or that person is going to tell me what to do or why is he allowed to rat me out or talk behind my back... so this guy told me this is how it is around here and you either play it or suck for everyone. So I went with it, if they want to fuck with me, I will fuck with them.
So fast it went House Of Cards kind of way and in the bad way kind of way. Instead of getting progress we were busy doing political stuff, usually law related, like finding each other misconducts, and there were no end to it. As I had most experience I with systems and stuff we were doing, outcome was pretty good for me, but after some time it escalated to such size that atmosphere was unbearable and I was so stressed and tired of this shit I left. It's miracle that management tolerated this so far. People were as toxic as nuclear waste site (or dota/lol players)
So far the conclusion is to sometimes suck it up once in a while or just clear the atmosphere as fast as possible. Otherwise you will wade in shit up to your chin for very, very long and it is not really healthy on the long run...
Type T ( something something... )
Type * TP = T;
> Be me
> Production code
> Update Type structure
> Wtf why was this even working
> Ask senior
> senior y u do dis
> Why were no errors
> He says
"I added -fpermissive and forgot..."
On production since May
I feel like we should ressurect devops reactions on devrant, and put dedicated tab right beside stories and projects,1
Migrating from opengl to vulkan. In the meanwhile, DevRant, let's talk about Balmers Peak !
Share your stories!3
Everything they are promoting and developing have problems with c++, either messy implementations, non standard extensions, weird behaviours, passive aggressive stance toward official iso standard, broken api, lack of components(libs) or non portable ones, shitloads of errors traced back to undescribed, undocumented anywhere dlls, and shitload of other problems
We have new scrum master. First meeting together.
- I would give them time to wensday (2 days away) days to do migration
- delivery is in Tuesday. can we have two teams to work on it so it will be done twice as fast?
- do you really think that if you get 9 women pregnant they would deliver you baby in a month?7
I've got a mini stroke today. My project ended and I got delegated elsewhere.
"It's going to be fine, it's c++, you will find yourself there"
Suspicious, it's a project everybody was staying out of as hard as they can. But hey, it's cool, how bad can it be? what can go wrong with that?
Reality was brutal, project that uses Boost C++ as framework and bjam as builder. Builds with a decent dose of luck, and only under special circumstances, only under one specific version of compiler. No docs, quartet of the code is in Fortran, just to use ancient lisp part which was second qarter. The most senior Dev around does not have idea how it all works. Also everything is inside one enormous try/catch block. Because of the reasons.
That's how people end up with severe alcoholism and meth addiction.8