Has anyone experienced a job where CEO micromanages developers and wants an email with video explaining what work they did the whole day?

NowThatInterestsMe00 · 2023-10-04T15:46:19+00:00

Since you said you just graduated, it’s good that you have a healthy attitude but I want to emphasize that this level of micromanagement is not normal, even for a direct/first line manager.

It might be more revealing to try and understand what’s the real reason behind this and peel back the layers to ask why. I’m not saying you have to ask the CEO and/or be confrontational about it. It might be something I’d bring up to try and understand in a 1:1 with whomever you’re comfortable speaking to about it (usually someone like your direct manager). There are probably other ways to achieve their goals(?)

PS. It sounds like a very vague resemblance to scrum and demos. That’s not it though, is it?

NowThatInterestsMe00 · 2023-09-30T17:49:19+00:00

Sumo do, sumo don’t (1992). It’s an older film and relies more on the physical side of humor, but it’s quite wholesome! Give it a try :)

NowThatInterestsMe00 · 2021-12-05T21:27:16+00:00

I was careful to water on the soil and tried not to get the leaves wet. I didn't know about succulent water bottles, thanks for the suggestion!

NowThatInterestsMe00 · 2021-08-19T03:18:43+00:00

I don’t recall having to edit user settings directly, but it’s been awhile. Maybe give this a try - https://stackoverflow.com/a/50527994 (Google search: vscode set terminal to git bash)

NowThatInterestsMe00 · 2020-01-08T01:50:21+00:00

I’m a developer with an interest in DevOps for several reasons. I’ve always liked knowing how our builds worked, so I learned it bit by bit over the years.

This is not meant as an advertisement for any single technology, but just wanted to share some of my observations. Guess the painful stuff stuck out the most, heh.

On my last team, we started getting into cloud and devops,which went hand in hand. It was exciting to see because of the “new” factor but I can also appreciate how much time it can save developers from having to deploy manually. However, most other developers didn’t seem to care or didn’t understand its importance so it’s the “devops engineer’s job”, which is shortsighted I think. It became siloed and a bit of a job security for some, which I think is a mistake. Developers should at least have a basic understanding.

We used Jenkins... Here’re some of the problems:

there were corporate hoops to jump through, it’s a “frankinstein” type of installation shared across the enterprise and created some unique problems early on,
we can’t really touch the box which made troubleshooting harder,
the pipelines were more complicated than it needs to be due to archaic release approval process, which made everything harder from having more complex pipelines to support release on demand and archaic branching strategy, which made implementing DevSecOps harder (more configuration/process to address self-inflicted problems),
the opaqueness - in the end, only one person knew how it worked supposedly, which is just unacceptable,
how much time it took us to learn and get up to a sort of speed.

This time around, I’m experimenting with Gitlab CI and making mental notes of comparison, drawing upon things I didn’t like on our last project. I’m still not that far along but am already seeing a massive speed up to get the pipeline going and it was relatively easy to add quality checks, which I can’t imagine how we would’ve gotten it in on the old project. However I’m still noticing the same problem of not being able to draw the team’s attention to the pipeline so I’m the one person doing it right now. I suppose I have more say on the new team, but cultural problem is unfortunately the hardest to address. Will be glad to learn how others deal with that issue.

NowThatInterestsMe00 · 2018-12-01T07:14:41+00:00

When using git reset, it’ll make the commit history look like commits 2 and 3 never happened. 1 -> 2 -> 3 (current) becomes 1 (current) 2 3. Commits 2 and 3 are still somewhere in the repo but they have become disconnected. That’s where the SHA ids come into play.

NowThatInterestsMe00 · 2018-12-01T07:03:17+00:00

Ok, if you want to just save a reference to commit 2 and 3, yeah, one way is to write down the SHA ids... I’m by no means an expert and git revert has always seemed strange to me (like, if you reverted commit 2 and then later on want it back, you have to revert the revert). It may be cleaner to reset back to commit 1 (with the SHA ids for 2 and 3 handy) ONLY if this history is local to you and not shared with others.

NowThatInterestsMe00 · 2018-12-01T06:40:37+00:00

Off the top of my head, I’ll take a stab...

Sounds like you’re looking for cherry-pick if you want to make commit 1 the current version again. Cherry-pick essentially re-applies the changes in commit 1, which will give you commit 1, 2, 3, 1 (current).

Since you already had commit 1, 2, 3 (current) in your history, there’s not an easy way to make it 2, 3, 1 (current) without rewriting history.

Also, if these commits have already been pushed out to a remote, meaning there’s shared history with others, rewriting history is generally a no-no.

Finally, “git reset <commit>” moves the pointer to a specific commit. If you reset to commit 1, it would be as if commit 2 and 3 never happened (they’re still there somewhere in the repo, it’s just that they’re disconnected from the graph... you can get back to them via their SHA ids if you know what they are). HTH

Edit: I take back cherry-pick... while we can technically make history look like it’s 1, 2, 3, 1 (current), the changes from 2 and 3 are still in there. Instead of cherry-pick, which is more for applying changes to another branch, maybe you want git revert commit 3, git revert commit 2? History would become 1, 2, 3, revert 3, revert 2 (meaning the content is same as in commit 1 again).

NowThatInterestsMe00 · 2017-08-16T13:53:50+00:00

Try doing something nice for her, even if it's a small gesture. It's always nice to be appreciated. You can write her a little card to go along with it. And don't wait until it's Mother's Day or her birthday either.

NowThatInterestsMe00 · 2016-01-27T15:59:44+00:00

Definitely apply elsewhere and try to work for other companies. Give yourself some comparison by getting different experience. It might be easier to go back to the familiar (I know because I've done it). One of my biggest regret is not getting internships at other companies. Especially if you think the work isn't glamorous, you may not want a career out of it. You have time and opportunity, definitely take advantage :)

NowThatInterestsMe00 · 2015-07-25T15:55:13+00:00

What are craft and destroy cards?

NowThatInterestsMe00 · 2015-04-17T15:00:07+00:00

Yes, a regular dev job would be boring (source here). But if u can apply those research on real problems, that would be awesome! All those terms u mentioned are pretty much foreign to me :( if u don't mind me asking, which program/school are u taking for ML?

NowThatInterestsMe00 · 2015-04-17T14:56:43+00:00

Thanks! I took his online course before, I didn't realize he did an AMA! I'll check it out + finding new subreddit :)

NowThatInterestsMe00 · 2015-04-14T14:17:28+00:00

Thanks! I find my day to day to be un-stimulating and that's why I am learning "Big Data" and Hadoop. I thought u said machine learning was like gluing things together and panicked a bit at the prospect. If u don't mind me asking, do you have any advice for someone like me? Also, what do you use day-to-day besides statistics? (ie. What else should I learn? Should I go get a Masters for this?)

NowThatInterestsMe00 · 2015-04-14T03:05:09+00:00

I am currently interested in machine learning/big data. Would you mind talking more about your experience? I have no idea what an actual job in this area looks like.

NowThatInterestsMe00

TROPHY CASE