Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "proactive"
-
Over the course of a few months, I began to suspect my manager disliked me on a personal level. I decided to be proactive and invited him to a meeting on "Improving our working relationship" - he showed up 5 minutes late and fired me.11
-
Corporate IT: Here at Company A we are very proactive about CyberSecurity!
Dev: What is our cybersecurity plan?
Corporate IT: If any breaches happen we will terminate those involved and discontinue use of the offending product
Dev: That sounds reactive to me
Corporate IT: 😡 It’s proactive actually as we put together that plan of action BEFORE anything happened!
Dev: …12 -
2019 resolutions/goals recap: (non-personal ones)
1) Improve diet (did; e.g. ramen and fast food to clean keto)
2) Lose weight (did; lost 24 pounds!)
3) Find a good job (did, twice)
4) Buy a harp (did not; large and expensive, no place to put it, and I have small children who would absolutely break it)
5) Keep house clean, even if it's by myself (did, somewhat; I cleaned some, managed to get one other person to clean semi-regularly, and another sporadically)
6) Work on social awkwardness (did; read and applied Dale Carnegie's The Art of Public Speaking, which netted me my last job offer. Still pretty awkward though)
7) Move out of the desert (did not; not enough money, and job didn't allow remote work)
8) Stop bloody waiting on people (did not; still very guilty of this...)
I don't remember the rest 🙁 didn't write them down last year. But I still accomplished 5 out of the 8 I remembered, with one being a pass, so 5/7!
-----
2020 resolutions/goals:
1) Finally move out of the desert
2) Invest 20% of my income every month
3) Reduce bills by 20%
4) Solve/address some health issues
5) Make a schedule so things regularly get done around the house, e.g. cleaning
6) Find some friends and make time for them
7) Replace Debian with something else
8) Revamp my backup system
9) Be proactive and stop waiting on people
10) Build a (stationary) coil gun for fun18 -
*Me, sittting in a sprint planning meeting*
PM: We are going to start a 2 weeks sprint and everyone is expected to meet the deadlines no matter the cost.
*Scrum master being an intern doesn't still know how to plan the sprint*
Me: we are having a week long holiday due to elections next week and how do you expect to finish within the deadline when office is closed.
PM: we are aware of that, but who is ready to take this as a challenge and be proactive in completing the tasks?
How many of you have faced this situation where the company expects you to work from home and get the tasks done even during the holidays. The company only values their work and not the employees. They want us to work as slaves without valuing us. They expect us to be loyal to the company through work but they aren't ready to be loyal to us through payments.
DONT DEVELOPERS HAVE THEIR HOLIDAYS TO SPEND TIME WITH THEIR LOVED ONES? ARE WE MACHINES?15 -
Dear Product owners / Company Owners / Whoever requesting a feature:
Devs like to know they are adding value to whatever product they are working on. Every time you request a stupid no value added request, you kick the dev's soul.
After several hits the developer will stop caring about the software and eventually will get the job done, but oh boy, the amount of tech debt/trash code the dev is gonna leave behind will be horrendous.
Then the next developer, not only takes the hit from another stupid request, he/she will see the crappy code the past sad developer left and will take a double hit. Of course all of them start proactive and try to fix previous blood trails but sadness will catch them eventually.
If you want you're apps/products/reports to be good in a long run don't make stupid requests.
BAs, Stop being Expensive Email Forwarders and challenge a request, understand the process and then hand it to the developer.
Us developers are sensible cute ponies. Treat us well or expect poor quality projects8 -
!dev
To anyone suffering from chronic pain, especially lower back pain: Don't get fooled by shitty doctors. And don't expect doctors to magically heal you. If you want to stop your suffering, you need to be proactive.
What? But my herniated disc from 10 years ago... bla bla bla. So what? It's not going to get better when your only exercise is putting on your socks. Chances are 99% that your spine has shit to do with your pain. Go to a proper chronic pain therapy instead of downing opiods and getting sick notes.
Note to self: Do your sports every day you lazy bastard. Eat healthy, sleep regularly, don't stress out over every damn thing and don't forget to fucking relax!23 -
!dev
So the ceiling in our (upstairs) laundry room started leaking. After some troubleshooting, we determined it was the A/C, and not the water pipes. (The house is cheap as hell and fucking stupid.) We did some troubleshooting and research, and tried fixing it ourselves; no luck. Cleaning the pipes from outside: no joy. Cleaning the pipes from inside: no access. The attic is ... small. Maybe half a small closet? and doesn’t give access to fucking anything. The builders must have installed everything before putting up the walls and ceilings, sealing everything off, because there is no access. It’s fucking stupid. Also, the usual maintenance openings aren’t even there either because why the fuck would they be?
But fucking whatever.
We called an a/c repair guy, who never showed. We assumed he was busy (it’s fucking hot), so we called him again the next day; two days later he showed.
Busy. Whatever.
Guy didn’t bring a ladder. Whatever, we have one right there in the hallway because we’ve been trying in vain to fix it.
Guy didn’t bring a wrench of any kind. Guy didn’t bring a screwdriver. Guy didn’t bring a bucket. Guy didn’t bring any pipe. Or any pipe sealant. Or fucking anything but his sagging fucking pants, fat belly, and fat stench. We had to supply everything, which fortunately we had on hand as we were already trying to fix it. Hoorah for being proactive.
Guy said he drained both primary and secondary pans. Somehow. Without access. I’m not even convinced it HAS a secondary pan. Guy said he cleaned out the pipes, too. From inside the house. Without access. Somehow. Maybe he did that from outside, without tools, while I was chasing the brats and someone else was watching the fat bastard. Who knows; I wasn’t with him most of the time.
When he was done, the guy said “pay whatever you think it’s worth” (or whatever). Fine, if he actually cleaned the pipes out and it isn’t leaking anymore, that’s great.
Guy leaves.
We go up to check. AND THE FUCKING A/C IS STILL LEAKING. BUT NOW IT’S FROM BEFORE THE PIPES, TOO. AND HALF AN HOUR LATER, THE LAUDRY ROOM CEILING IS ALSO LEAKING, WHICH MEANS THE PIPES ARE STILL LEAKING.
It turns out the asshole broke the pan.
We call him back, he goes blah blah blah, we send him a video. Drip, drip, drip.
His response?
“The pan must be rusted.” IT’S FUCKING PLASTIC.
“Oh, in that case, it’s probably a rusted coil that’s leaking.”
a) HOW DID YOU NOT KNOW IT WAS FUCKING PLASTIC IF YOU DRAINED IT?
b) THE COILS CARRY FREON, NOT WATER, AND THE A/C IS STILL WORKING. IF THERE WAS A LEAK, SHIT WOULD BE HOT. AND RANK. FREON SMELLS NASTY AND DOESN’T CAUSE IT TO RAIN IN THE FUCKING HOUSE.
REPLACING A COIL IS ALSO A $2000 FUCKING REPAIR.
THE FAT BASTARD PROBABLY BROKE THE PAN INTENTIONALLY JUST TO UPSELL. I WANT TO FUCKING MURDER HIS LYING FUCKING FACE OFF.
It’s possible he didn’t break the pan intentionally, so I’ll tentatively remove that from his charges. BUT TO FUCKING LIE?
LIE AND DIE, FUCKER.rant i can’t wait to move lie and die reasons why i’m a misanthrope lying fucking people everyone lies7 -
After doing the work he requested as he wanted he was not happy. So i thought we sit and discuss what he didn't like. I was so wrong.
...
Boss: "...you know what I think you are: a fraud; Masquerading as a developer. The database design you have given is shit. The template I gave you I did in 1 hour. You took half the day."
He gave a simple template to use and he told me to come up with an ecommerce db design via downloading PrestaShop and seeing what is relevant to us.
Me: "what did I do wrong?"
Boss: "you think I don't know what PK means in database design? Why the fuck did you put this here."
Me: "can I expl..."
Boss: "I'm not finished, you been here half the month and what work have you to show for it..."
Me: "I have..."
Boss: "You shut up when I can speaking"
Me: "ok"
Boss: "You have no work to show for the time you have been here. I tell you what to do. I want someone who is proactive. My friend, you will do the work I tell you to do, you understand?"
Me: "yes but can I just say that I have been doing your work I have the contact the various developers as you..."
Boss: " You shut up when your boss is speaking. Can you do this work? (Slightly long pause)
Me: "I can do it. But, I have done the bits of the work you said I do. I was h..."
Boss "don't give me bullshit stories...you haven't done the work..."
Me: "But you have spoken"
Boss:" You know what Im giving you 1 weeks notice if you are not able to do the work. Can you do it?"
That moment!!! I was literally shaking I could have high fived his face with his laptop.
Me: "yes I can"
Boss: "Then get the fuck out of my sight and do it"8 -
We were 6 devs on a big project that needed to be completed in 3 months. Probably my first project as a full-stack dev and the work was very demanding.
The senior of my team was a very sharp and energetic, but also a very "in your face" kinda guy. Like, he was cool, but sometimes a little too much to handle for some people.
Anyway, this guy "Senior dev" worked faster (naturally) and harder than the rest of us and was always willing to help if somebody had problems with a framework, tool or other technology. Also, there was this other guy also a good dev (second best I would say) that just hated the first guy's guts for being "rude and obnoxious" as he put it.
One day, the PM and the senior had an argument about a major change that the PM had agreed to (just to save face with the client) that will force the team to come to work on the weekend. In the end he saved us the trouble of going throught that and the PM had to tell the client that the change wouldn't be made. From then on it went downhill for "Sr. dev" in the company. Until one day he was told that his contract was not gonna be renewed.
Short after, he showed some of us a screen cap. somebody sent him of an email from the "hateful" dev to the PM in which he wrote he had heard that the senior guy was leaving and he couldn't be happier because he was "damaging, problematic and a stressful part of his job". That was such a dick move, we thought he should get back at the guy.
So he sent a fake email to the PM using the "hateful" guy's email ID, that read:
"Dear PM. I'm sorry I said those things about 'Senior dev', I guess I'm just mad that he's a better professional than me and mad that I was born with no genitalia".
After the senior dev left I worked on one more project with the "hateful" dev and he was let go mid project for "not being proactive and making little effort on completing the project". -
As you start managing people, you understand why you read job listings requiring attributes like "Passionate about creating things" or anything like that.
When you see people not proactive and just lazy in a group, and you let them in, it's really disappointing. It makes you feel like you have to put everyone out, do it all again with new people, and pay attention to what gave them away the first time but you didn't know yet.
Next time I'm gonna look for people "passionate" about what they do and "interested in making great projects".7 -
"Hey boss, could you look over this reply to this support case before I send it? I just want to clarify a couple of things first."
"I haven't got the time to look over support case replies - you need to be proactive in deciding what's right, and then just sending them on."
"Ok, no worries."
5 minutes later...
"What the hell have you written on this support case? This isn't correct at all. Now they're going to be really confused. You've completely contradicted what I told them yesterday on the phone."2 -
You know how, sometimes, you start being tooooo proactive and implement stuff even though your boss never told you to do it? Well, that happened at my previous job, and apparently almost everyone at the team questioned the changes and made me look like the fool I was. That day, I learned that you should never implement stuff that wasn't asked... And it was humbling, since I was an arrogant fuck and basically I was speaking loudly and denied the criticism... But today, I'm better, I know how and when to shut up, and I accept criticism now.2
-
Update: https://devrant.com/rants/4676421/...
I told you all. I fucking told you. Nobody listened to me.
Good people just leave.
This dude who I look upto and is kind of my mentor in the org and has spent a decade here, just resigned.
What the fuck!!!!
And with that, the attrition in product team is insanely high, to the point that it's scary.
My manager is not responsive and is often reactive instead of being proactive.
While the leadership is super excited about the product and everyone says they are hiring more and more people in product team, the design says our product is not a priority for them and we are just left with one design resource.
I was conversing with my colleague and we both are super scared that they shouldn't scrap the product and fire us.
This seems unlikely with all the logical calculations that we did but in a capitalist system we have to be prepared for anything.
I am shit scared right now because there is no clarity on what could happen next.
On the other hand, my skip level manager is taking a lot of interest in my work and is working very closely with me and taking more ownership of our product than my direct manager.
Everyone says our product is a top priority and tech is super agressive about it.
One thing that could happen is my manager leaving and not telling us about it upfront.
In which we would just report to our skip level manager and growth chances would be even better.
But at this stage, this seems super scary to me.3 -
[Update: https://devrant.com/rants/4425480/...]
So had a 1:1 with my manager today followed by 1:1 with lead.
I did bring up the topic that I felt a little insecure about being sacked.
Both of them reassured me multiple times that losing my job would be the last of the last things. We have so much work and going through a resource crunch to keep up with the pace.
There are still many things I have to learn here. I am glad that my proactive-ness has always helped me learn faster and better. This way, I was also able to offer a helping hand to my manager by saying if they need any help on the transitioning, I am will to take extra on my plate until we have a replacement.
A bumpy ride ahead for sometime but surely manager is impressed with the speed at which I ramped up and willingness to go beyond.
Overall, I see this as a good opportunity to step into the lime light, build an amazing product from scratch in a publicly traded company, and a good good chance to relocate to EU when I show them good results with my performance.
Overall, sky looks brighter but sea will be a little rough for some time.4 -
I explained last week in great detail to a new team member of a dev team (yeah hire or fire part 2) why it is an extremely bad idea to do proactive error handling somewhere down in the stack...
Example
Controller -> Business/Application Logic -> Infrastructure Layer
(shortened)
Now in the infrastructure layer we have a cache that caches an http rest call to another service.
One should not implement retry or some other proactive error handling down in the cache / infra stack, instead propagate the error to the upper layer(s) like application / business logic.
Let them decide what's the course of action, so ...
1) no error is swallowed
2) no unintended side effects like latency spikes / hickups due to retries or similar techniques happens
3) one can actually understand what the services do - behaviour should either be configured explicitly or passed down as a programmed choice from the upper layer... Not randomly implemented in some services.
The explanation was long and I thought ... Well let's call the recruit like the Gremlin he is... Gizmo got the message.
Today Gizmo presented a new solution.
The solution was to log and swallow all exceptions and just return null everywhere.
Yay... Gizmo. You won the Oscar for bad choices TM.
Thx for not asking whether that brain fart made any sense and wasting 5 days with implementing the worst of it all.6 -
Be proactive and improve your own projects. Publish them on GitHub, and make sure your LinkedIn profile is set up. You'll be contacted soon by companies for sure!3
-
I'm trying really hard not to be sensitive, but my manager is making it difficult with their "constructive criticisms" ...
Just finished up a call with them. And I'm so tired. I'm not even angry or upset, I just feel so tired of their bullshit.
I set up a meeting as a courtesy to get them up to date on all the code changes I made. Last night I stayed up late to try and get things in before the deadline and this morning just killed me when they say.
"I don't think I should have given you this."
"I was right, you weren't ready to start doing this."
(Then don't even bother giving me anymore tasks then, I don't fucking care.)
"you clearly don't understand how branches work"
(Absolutely fucking false, I fixed that shit and am very familiar with how to understand the structure of the fucking repo)
"you are rushing and I don't need you messing up the website"
(I'm being proactive you twat, not rushing, making it very difficult for me to do the work and being productive)
Like seriously bro! Don't fucking patronize me for the work I was trying to get out. And trust me this fucking meeting is done in order to get ahead of potential issues, not a time to be condescending of my skills or lack there-of as you seem to so keenly think.
If you had this much doubt about my abilities then why give me the fucking Sr. title? Fucking trust that I'm being honest, and I'm trying to get us to a good spot, not fucking sabotage the company. God fucking damn.6 -
o and btw, yesterday was my birthday lol.
realtalk: if you want me to feel special, dont fucking force me to be more social than on all the other days together, or i will rewrite the year without eightteenth february.
you fucking corksuckers, i dont want to go to that place my grandma (same bd as i) goes to to celebrate. fucking mediocre pizzaria isnt fucking worth it, so atleast give me a choose.
and on the very Least, could you please quiet up? its not by telling me ten times per hour to be more proactive at school that you will help me like school.
o and also FFS WHEN IM FUCKING SICK AND EVEN OFFERING TO GO TO THE DOC TO SEE, FUCKING DONH SEND ME TO SCHOOL ANYWAY, ESPECIALLY IF IT IS JUST BEFORE MY BIRTHDAY
(you just got an insight into my life. wanna see more? i dont think so)3 -
Let me begin by giving props to the KDE team for being proactive, and working to improve the ecosystem in which they exist.
https://fossbytes.com/kde-slimbook-...
With that said, I'm sitting here wondering why bigger organizations - companies with significantly more clout - can't manage to do the same thing. Canonical is so busy, fapping at the notion of competing in the mobile space (they won't though) that they've lost sight of their core audience - computer users. While they insist on trying to piss in Google's Cheerios, smaller teams are 1) pushing out better firmware and software, and 2) are now creating (seemingly) good hardware as well.
As the public face of Linux (unfortunately), Canonical and the Ubuntu team have an obligation to lead from the front. In neglecting to do so, they do a disservice to the entire Linux community. KDE, Manjaro, Arch, Mate, Debian, etc are all doing more with less, and they're offering better end products than Canonical has in the last decade.
/rant16 -
After years of working at a place where you are as good it gets in terms of domain knowledge, it can be refreshing to work with someone who has way more experience than you.
The previous company I was with wanted to have me as one of their primary engineers, and everyone else who came in would have to learn from me (most of them were low-skilled contractors). This should have been great in theory, but it was actually quite frustrating since I did not relish being the mentor figure while just being two years into my career. Despite it getting to my head at times, I was aware that I still lack a lot of skills, but with no one to teach me, I hardly progressed in terms of growth, even though the leadership treated me well and listened to me.
Took a leap of faith and quit, to join a start-up where I would be the most inexperienced (and the youngest) person. Has been a few months, and I have stumbled and goofed up more times than I like to admit, but taken with the right mindset, it is nice to see how a team of professionals goes about it. It is a learning curve to get back into the mindset of the novice (after more than a year of being the undisputed "go-to" person), and to make effort knowing that you'll fall short in multiple places by the standards here, but at the same time, it's nowhere like the frustration I felt previously when my head was pushing against the shallow ceiling.
Fun part is, the learning is almost not at all about the code, but about how to be a proactive team member and all the things to think through and finalize BEFORE getting down to code. Some of it is bureaucracy, yes, but given the chaotic place I come from, I don't really mind it as long as it only goes as far as what is required.
The most amusing part of it all to me is how I try to be humble and listen to people (everyone's got a lot more experience than me), but I'm often asked to be critical of what others say and poke holes instead of just taking what they say at face value, which has been one of the most challenging things to adapt to for me (for similar organisation cultural reasons mentioned previously)/1 -
I hate the word "Proactive"
What does that even mean? You add the prefix pro- to the word "active" and you get the same thing! Why not just say active?!
We're talking an active approach
We're taking a proactive approach
See, they mean the same thing and the first version doesn't make you sound like a douche.12 -
!dev, just rant
what the fuck is wrong with these people. yesterday i wrote him if we can meet to sort out my medication, no response,
ok, normal.
this morning he writes me "i wasn't home yesterday, i am today".
wow, actually a a proactive and early info! that's... unusual.
so i go "hmm, maybe even right now?"
he's like "no, sometime from 14:00 or 14:30"
ok.
so i wait until 15:00 to give him a bit of extra time, i hate rushing people. "so can i stop by?"
he's like "i'm going out in a short while, i'll let you know"
okay.
i hate these "bind a listener to me and wait until i ping you", but okay short while is fine.
so I wait. for half an hour. I mean... i'm bad with time management, but even I don't call half an hour a "short while" anymore. so I'm like okay, I think I know where he's gonna tell me to meet, it's gonna take me about 10 minutes to get there, they tend to be impatient so if if start walking there, by the time i get there he's gonna write me to come, and i'll already be there so he won't have to wait for me, because surely even for him "a short while" can't be more than 45 minutes.
so i get there, wait for 5 minutes... 10 minutes...
so i write him again "approx how much longer? i'm waiting nearby".
and he's like "i didn't call you, i have no idea why you came here, who told you to"
so i tell him "okay, sorry, i'm gonna get myself not nearby and wait there, i thought by the time i get here you're gonna call me anyway, sorry"
nothing.
i wait for half an hour more.
then (two and half hours after he said he's gonna go out "in a short while" and he'll let me know. at the same time 5 hours after the time he said he's gonna be available from), i write him: "so will we actually manage to sort this out today?"
no answer. most likely for the rest of the day.
what the fuck is so difficult about conveying actual information in communication? what the fuck is so difficult about a single fuckin message "at this time, at this place", so i can just be there, he can intersect his route through there, and in a literal minute we're sorted out? instead of fuckin nothingmessages which waste me three hours and make me have to bother him to at least have a chance at getting an idea what the fuck is going on, and him being annoyed at me trying to cover for his fuckin inability to do it like any other sane dude, with one fuckin message in the fuckin form of "this time, this place", which would fuckin sort out the whole thing in two messages and 5 minutes net time invested into the whole thing by both sides, instead of fuckin 3 hours?
fuck.
i miss my old dude.4 -
I setup ELK for our team and went live with it on Production VM.
I'm the only one that knows how it works, is setup... Because no one else cares or wants to know as long as it works...
And well if it doesn't, let's just say they hope that I'm around...
On a side note, I think I'll leave a bit early today since I cut or main projects build process time by 50%.
Root cause: SONAR complains if you implement that using if else to match each field... it is pretty ugly...
And can use Lombok to clean it up, last rant.
So shaved off 10 minutes in each build... And well I'm like seriously? No one else bothered to figure this out for the last year or 2?
I mean I've been pretty busy too but the team had like 20 ppl and at least 4 senior devs and well u don't even need to be senior? Just inquisitive and proactive?2 -
Last week I hired a friend of friend to work on my projects. Hes a young and friendly guy. However he never worked in actual office and it shows. During the meeting he brings his phone and in the middle of explaining he pulls out his phone to respond someone back. Basically lacks professionalism and has this young person cockiness where he thinks he is competent to handle everything while in reality last week he did 2-3 hours worth of work. I want to set up some boundaries but I dont want to seen as a harsh dictator. On the other hand Im paying him over the top even though he doesnt have skills, but the least I want to is a decent attitude and effort. How u would advice me to approach this and teach him to get his shit together? Im already becoming resentful and next week if he keeps treating his work like a school project I will let him go.
Im really trying to setup a nice environment for him to work at, I rented a nice office in a hub space and also bought entirely new laptop plus monitor setup for him to work. I even took him for drinks and lunches but for some reason I start to feel that hes taking that shit for granted and Im being too good.
Hes not proactive, it seems that he will do bare minimum that I give him.8 -
!rant
So one of my coworkers is looking to leave. They are a good worker, proactive and involved on the project, and just finished their Master's degree. But the money isn't good enough/won't be good enough for them here. I'm pretty sure management knows, but they confided in me and I know that they're actively looking to leave.
Should I speak up? This will dramatically impact us in a negative way.3 -
So I'm assigned once again to fix a new someone else created and that seems to be the case whenever there's an issue...
Boss just assigns it to whoever is most likely to be able to investigate it... which is basically me. Other than the little time I can use to develop stuff, I'm usually cleaning up other people's messes.
And these other people are to busy working on new crap to properly explain how their existing code/processes/changes works.
And well the fact that anything breaks in production (that's not due to upstream one off issues) whoever does not think he needs to take responsibility for it.
So everyone else and especially me has to spend time understanding the shit they wrote and fixing it for them.
How do I tell my boss this nicely that we need clearly definitely ownership and whenever a component blows up in prod, the guy that wrote the code fixes it no matter what? Thereby incentivizing him to not write shit code in the first place and be more proactive in making sure it doesn't in the first place since he knows otherwise he's doing overtime to fix it?
Is it just me or is there really no such thing as a dev job where something doesn't blow up due to poorly tested and designed code every other day?3 -
It's amazing how pointless this seems and how tired and noncommittal this makes me
When I was younger I made this insistent and logical comment
Now I'm so burnt out from this stupid shit I just accepted that I'm probably fucked and I'm fearful of being proactive because of these rapists and their system
I should just stab one of the really bad ones that might bring the old me back2 -
How does one get better at responding to issues that occur in production?? I feel the only way I learn is by having the issue occur and then fixing it...any more proactive ways available??3
-
Calling QA/ Test managers for help !
Im a junior dev at a company where im slowly transitioning into also being our test lead. I just got my ISTQB foundation and im starting to write out the test strategy for our company.
Currently we’r doing alot of reactice testing, and to implement more proactive testing i wanted to implement a risk strategy as well.
Problem is that i feel this strategy takes too much time for our organization (doing risk analysis for each story we’r implementing just isnt possivle) , and we don’t have time for me actinh as a full time Test manager while also doing software dev tasks.
Question is: what good proactive strategies can we implement that doesnt require too much time investment - or could we use risk strategy only for specific stories implemented / custom orders / etc and stick with a reactive strategy solely ?
Later this yesr ill be sent on ISTQB test manager course to better qualify my position but until then id really want to get a test strategy somewhat implemented
Any help is MUCH appriciated!10