>Paano ba mas maging effective dito?
Good ol' fashion self-study whenever you’re free. Write a document while you're at it, might impress them with the initiative.
Looks like problem mo is understanding ng structure ng codebase/data nila instead of not knowing the stack. Yeah, kung walang proper documentation your options are either to ask someone who knows or try to compare data you query from data that shows up from the system to familiarize yourself.
Dw op, not a big problem imo, it takes time for someone to confidently say they know most of what exists in their team. Heck wouldn't surprise me if no one actually did, ganun talaga pag big team/project ginagawa niyo
>Gusto ko sanang mag ask sa mga seniors namin pero busy rin sila kaya madalas delayed yung response nila
Kahit na busy sila, magtanong ka pa din. Expected naman na di mo alam yan since bago ka palang. Mas maganda itakenote mo yung sagot nila, tapos gawa ka onboarding doc para sa mga newbies tulad mo for next time. That way naoffload mo yung senior devs sa mga mago-onboard na bago. Documentation na din sya ng current system nyo. 👍 Good luck OP! Kaya yan!
Walang madali sa una. Ganyan din ako sa new work to think na may 7yrs akong exp sa past job. Ok lang yan. One at a time. Just take notes mga nagawa mo na para kapag naulit familiar ka na. Wag mo madiliin. Just get experience sa bawat bago na task na dumadating. In time halos lahat yan mafafamiliar ka at makikita din nila ang improvement mo. Basta hindi ka nila tinatrato na underperforming ok lang yan. Intindi nila pero much better makipagclose ka sa mga senior or kahit bago din gaya mo and magshare kayo ng mga nagawa nyong tasks para sabay matuto sa magkaibang fields.
I would try to learn every aspect of the software and while you do, you create a documentation its seems there is some missing so you can do your job correct. You can always argument there is no Documentation and it take so long to learn everything but you document everything now so it will be faster in the future.
Ganun sa una, wag mong sukuan if yung problem mo is yung tables, hingi ng buong schema ng database try to study para ma familiarize ka, try to understand yung business processes. Hingi ka ng documentation if meron, if wala hingi ka ng one on one session to raise your concerns, wag mahiyang mag tanong, mas ok ang nag tatanong, be pro active. Tanong lang ng tanong kahit busy yung seniors in the end kasi if ma miss mo yung deadline sayo yung sisi, so kulitin mo, it will just show yung eagerness mo na maka pag deliver
ganyan talaga. just keep on it. magiging mas effective ka eventually. nobody will expect you to be a super star 1 month in. mga after 6 months malamang kabisado mo na db schema niyo. and its good na nag tatanong ka sa QA kase most likely mas kabisado nila business logic.
> Gusto ko sanang mag ask sa mga seniors namin pero busy
so hindi ka na magtatanong? medyo bopols reason to. 1mo ka palang, asa stage ka palang na dapat magtatanong ka palagi and inonote para di na maulit yung tanong. alam din nung mga senior mo na nag sisimula ka palang.
magiging problema lang pagtatanong if paulit ulit na same question yung tanong mo. pag bago lagi, wag ka matatakot. everyone in the team wants you to succeed para dumali work niyong lahat. if you dont accept your role as a junior na hindi pa alam yung maraming bagay eh mahihirapan ka talaga.
I do still ask of course kung sa simula palang alam ko na di pako familiar dun pero marami cases talaga na di ako narereplyan agad since busy nga sila halos lalo na pag start na yung sprint
What is google ? What is chatgpt ? What is YouTube? What is stack overflow?
The issue na lang dapat is the familiarity ng tables and their relationship.
A query for the report should only take 1 day.
You need to step up.
Of course I know naman yung sa technical side kaya ko naman mag manage dun, nagkaka issue lang since first time ko mag generate ng report dun sa mga tables na yun so si product owner nagbibigay siya ng columns na gusto niya makuha, it sounds straight forward at first pero nung kinukuha ko na siya don na lang nag kaka issue, so madalas nagbaback and forth kami dun sa mga reports minsan need talaga dagdagan, problem ko lang dito is di ko agad na mention nung initial meeting since di nga ako familiar pa
Then you have to document the requirements para walang sisihan sa huli kasi it’s either wala sa requirements or hindi sya clear or it’s so complicated that you need a lot of time.
Other than that reasons, it’s gonna be mostly your fault
>Paano ba mas maging effective dito? Good ol' fashion self-study whenever you’re free. Write a document while you're at it, might impress them with the initiative.
Looks like problem mo is understanding ng structure ng codebase/data nila instead of not knowing the stack. Yeah, kung walang proper documentation your options are either to ask someone who knows or try to compare data you query from data that shows up from the system to familiarize yourself. Dw op, not a big problem imo, it takes time for someone to confidently say they know most of what exists in their team. Heck wouldn't surprise me if no one actually did, ganun talaga pag big team/project ginagawa niyo
>Gusto ko sanang mag ask sa mga seniors namin pero busy rin sila kaya madalas delayed yung response nila Kahit na busy sila, magtanong ka pa din. Expected naman na di mo alam yan since bago ka palang. Mas maganda itakenote mo yung sagot nila, tapos gawa ka onboarding doc para sa mga newbies tulad mo for next time. That way naoffload mo yung senior devs sa mga mago-onboard na bago. Documentation na din sya ng current system nyo. 👍 Good luck OP! Kaya yan!
bat ganto mga gen z konting pressure naiiyak na?
Mga iyakin talaga sila, nasanay kasi sa spoon-feeding frenzy.
Walang madali sa una. Ganyan din ako sa new work to think na may 7yrs akong exp sa past job. Ok lang yan. One at a time. Just take notes mga nagawa mo na para kapag naulit familiar ka na. Wag mo madiliin. Just get experience sa bawat bago na task na dumadating. In time halos lahat yan mafafamiliar ka at makikita din nila ang improvement mo. Basta hindi ka nila tinatrato na underperforming ok lang yan. Intindi nila pero much better makipagclose ka sa mga senior or kahit bago din gaya mo and magshare kayo ng mga nagawa nyong tasks para sabay matuto sa magkaibang fields.
I would try to learn every aspect of the software and while you do, you create a documentation its seems there is some missing so you can do your job correct. You can always argument there is no Documentation and it take so long to learn everything but you document everything now so it will be faster in the future.
Wala naman hindi nag struggle sa una. Maging consistent kalangm Develop good coding practice at early as possible and be resourceful.
Ganun sa una, wag mong sukuan if yung problem mo is yung tables, hingi ng buong schema ng database try to study para ma familiarize ka, try to understand yung business processes. Hingi ka ng documentation if meron, if wala hingi ka ng one on one session to raise your concerns, wag mahiyang mag tanong, mas ok ang nag tatanong, be pro active. Tanong lang ng tanong kahit busy yung seniors in the end kasi if ma miss mo yung deadline sayo yung sisi, so kulitin mo, it will just show yung eagerness mo na maka pag deliver
ganyan talaga. just keep on it. magiging mas effective ka eventually. nobody will expect you to be a super star 1 month in. mga after 6 months malamang kabisado mo na db schema niyo. and its good na nag tatanong ka sa QA kase most likely mas kabisado nila business logic.
95% sa pagiging dev is to learn it on your own or figuring out things yourself. Research at trial and error talaga
di ko sure anu problema. base sa kwento. mas productive ka pa sa isang senior. masyado na bang perfectionist mga junior ngayon? lol
I feel you haha. 2 months pa lang sa work. Stressful sobra. Malalagpasan din natin yan.
Mag take notes ka lang lagi hanggang sa maperfect mo, tapos kapag magaling ka na, share your knowledge.
> Gusto ko sanang mag ask sa mga seniors namin pero busy so hindi ka na magtatanong? medyo bopols reason to. 1mo ka palang, asa stage ka palang na dapat magtatanong ka palagi and inonote para di na maulit yung tanong. alam din nung mga senior mo na nag sisimula ka palang. magiging problema lang pagtatanong if paulit ulit na same question yung tanong mo. pag bago lagi, wag ka matatakot. everyone in the team wants you to succeed para dumali work niyong lahat. if you dont accept your role as a junior na hindi pa alam yung maraming bagay eh mahihirapan ka talaga.
I do still ask of course kung sa simula palang alam ko na di pako familiar dun pero marami cases talaga na di ako narereplyan agad since busy nga sila halos lalo na pag start na yung sprint
What is google ? What is chatgpt ? What is YouTube? What is stack overflow? The issue na lang dapat is the familiarity ng tables and their relationship. A query for the report should only take 1 day. You need to step up.
Of course I know naman yung sa technical side kaya ko naman mag manage dun, nagkaka issue lang since first time ko mag generate ng report dun sa mga tables na yun so si product owner nagbibigay siya ng columns na gusto niya makuha, it sounds straight forward at first pero nung kinukuha ko na siya don na lang nag kaka issue, so madalas nagbaback and forth kami dun sa mga reports minsan need talaga dagdagan, problem ko lang dito is di ko agad na mention nung initial meeting since di nga ako familiar pa
Then you have to document the requirements para walang sisihan sa huli kasi it’s either wala sa requirements or hindi sya clear or it’s so complicated that you need a lot of time. Other than that reasons, it’s gonna be mostly your fault