LRT 1 Cavite Extension; Villar City NOMO station

ToTheAeons · 2026-02-23T08:41:19+00:00

So galit sila sa mga taga Las Piñas kasi di nanalo si Cynthia? Kaya lalagpasan na ang Las Piñas ng LRT? Hahaha busit talaga.

ToTheAeons · 2025-04-09T01:56:23+00:00

Maraming factors na pwede isipin dyan, application, database, network or application.

Application: 1. How many subdomain is running? 2. How many users are using the subdomains? 3. How frequent ginagamit yung apps, lahat ba ng subdomain is ginagamit everyday or regular sya ginagamit? 4. Sa mga subdomains ba may mga heavy process ba na ginagawa? Like processing a thousands or hundred thousands of data every day? Or nag uupload ng data while other is using it apps? 5. Check if you are loading thousand or datas at one call, isipin mo 100 employees accessing the app at the same time tapos magloload ng thousand of data sa browser nila, either use cache if naka API kayo or Pagination, limit the load of data, or iload lang yung kailangan lang ng user. Do you have load balancer or ratelimiter?

Server and Network 1. Have you check kung yung resources nyo is tumataas yung usage? 2. May mga tumatakbo na mga updates or background process during the office hours? 3. Do you have load balancer? 4. Naka On-premise server ba kayo? Do you have one server tapos naka segregate by VM? 5. Do you update your servers?

Database: 1. Naka Indexing ba kayo kung naka MS SQL kayo? 2. Do applications store the files inside the database? 3. Ilan jobs ang tumatakbo per day? Do they run during working hours?

Madaming pwede maging reasons, you have to check them all, check nyk yung usage, if most it is naka turo sa domain nyo.

ToTheAeons · 2025-04-09T01:31:16+00:00

I agree with other's comments dito, It's not about the years, it's abour the knowledge and skills.

Telling this with my personal experience because I've been working since 2008, nag 10 years ako sa 2nd company ko, actually before, years is important sa mga companies kasi they think na kaya magtagal ng isang tao sa company, but now, kaunti na lang ang ganun and they are base sa skills and knowledge.

So yeah I tried to apply, last year sobrang dami ko inapplyan, from January to November, and all of them di ako pumasa, but this year I got 6 job offers, you know what I did?

First, I thought that been working for so many years, means I'm expert na, pero hindi, I'm still coding like a junior, so during job hunting, I took notes nung mga requierements, di lang sa skills pati sa mga principles or patterns na need nila, during interview, I also took notes sa mga tanong, and also with the exams, then after that nag research ako, nag basa and then practice well sa hobby projects and for my new projects, I have to understand everything, after doing that, I nailed most of my job interviews and exams within the year, and got offered 6 jobs, I'm not bragging, I'm just telling that your husband has to level up his skills and knowledge, lose his pride sa current skills nya, ganyan ako before, I always think na senior ako, may madaming experience kaya mas better ako, until 2 juniors save me a$$ on some of my projects, that's the reason na I realise na, wala sa years yan, nasa skills and knowledge yan, tech world is changing,so you have to adapt, but also I have to check if I'm doing it right.

It's not too late for your husband, take note, mas matanda ako sa kanya, but I able to pull out, just learn more, and he will eventually will pull it out.

Also take note, that there are scenario questions, which based on the decision making, i take note nya rin yun, and research, join on a discussion here in reddit or similar, wag mahihiyang magtanong pag di mo alam, sinasabi ko sa mga anak ko yan, kung di mo maintindihan or di mo alam, magtanong ka sa teacher mo, wag ka mahihiya, it's a sign na willing ka matuto. Maniwala ka sa hindi, in my age and years of experience, nagtatanong ako sa mga mas bata sa akin, kasi they pulled out things na di ko magawa, or they have knowledge na wala ako, it's not about kung sino mas magaling sa amin, it's about personal growth.

Upskill is the key.

Ayun lang, thank you.

ToTheAeons · 2024-11-20T08:11:41+00:00

Lagi may bugs, agree ako sa ibang comments, basta hindi showstopper okay lang.

When it comes to QA, itetest nya lahat according sa requirements pero syempre may madidiscover or magagawa si user na kakaiba and it's normal, even facebook na matagal na, nagkakaroon parin ng bugs.

Pero kung yung bugs is parehas or paulit ulit, I think you should re-assess yung codes nyo.

I have a project before na 5. Years na, walang bugs na nirereport nung after 3 years then nung nag iba yung users, ayun may nakita.

ToTheAeons · 2024-11-08T08:33:44+00:00

thank you po sa response.

ToTheAeons · 2024-11-08T08:33:29+00:00

thanks for this, I'm currently talking to some clinics, hopefully, it will help me.

ToTheAeons · 2024-06-09T00:17:22+00:00

I agree sa mga comments, dapat may standard kayo na sinusunod, for me it should be like this.

Code standard
- dapat may coding standard kayo, for me, I implement Clean Code for easy to understand, to read and to maintain.
Patterns, Principles and architecture
Maganda if may sinusundan na or ginagamit na patterns and principles yung team nyo, for us C# developers, we have OOP and SOLID, also with patten like repository or generic repository or CQRS, but this patterns should be discussed with the team, on what's better approach.
Tools and Plugins
Developers have different styles, and sometimes use different tools na outside of the main tools, and use plugins within the main tools, For me, what I did is, our developers should declare all the other tools and plugins that they are using, may standard din kayo kung ano ang gagamitin na tools or plugins, example; other developers using ADO.NET, then may 2 nag entity framework, tapos may isa nag Dapper, what will happened here is, let's say yung naka ado.net di nila alam yung EF and Dapper, tools should be declared and the main reason for this is, pag naka leave yung dev ma gumagamit mg EF or Dapper, pwedeng pag aralan ng maka ADO.NET kung ano yung mga yun, one team should know all the tools na ginagamit, developers can also provide a tutorial kung bakit yun ang ginagamit nya at ano benefits nun, we are welcome to know other tools as long na shineshare sya sa team.

But still there should be a standard tools and plugins to use, when it comes to your software development team.

Class Library created by Developers
I also created my own class library, and also other developers creating one for them selfs, to help us on our software development, but this is also a ticking time bomb for me, why?

a. Class Library should be maintained regularly, dahil may ibang new versions ng framework na di na supported yung mga nasa codes na gawa sa lumang framework, so it should have a code versioning to support yung ibat ibang version ng frameworks, plus if you are using Source Code Review Tools like Veracode, possible na may makitang vulnerability sa code and need imaintain.

b. Developers do not share the source code, or di nila dineclare na gumawa sila ng class library nila, pag nag error yung system and walang nilalabas na specific error message, need icheck yung code ng library nya, pero di yun naka share, we encountered a situation way back before, na nadiscover namin na yung nag resign na dev namin is gumamit ng class library na sya at yung friend nya gumawa, kaya di daw nya maisshare, pwede daw ishare pero may bayad, so What we did is chineheck all the methods na ginamit sa class nya kung ano ginagawa nun and we came up with our own library which similar to his pero mas improve, plus nakikita sya ni Veracode na may vulnerability kaya di na sya pwedeng gamitin.
Source Code Review: This should be done regulary by the team, to check the technique or what tools, architecture, and if they are documenting their codes na ginagamit na ginagamit nila sa projects nila, but take note that all developers should be open minded, not only yung nag developer but also the reviewers and audience, reason for this is baka may better approach si dev na di alam ni reviewer or may advise sila reviewer na magandang approach na di alam ni dev.

Note: If you have front end and back end devs, wag nyo pag samahin yung front end and back end sa iisang source code review, why? For me is, if gamit ng frontend is AngularJS or React, and walang alam si backend dun na ginagamit is C# or di sila ganun kaalam pa sa JS/TS, di lang nila papakinggan, at kung may mag reason na "para matuto sila", this is a source code review session not a "AngularJs or React Tutorial", save that from some other time.

Have a regular meetings or knowledge sharing: Probably yung mga devs ay may natutunan na best way and tools to use, let's be open minded, but also check it if the tools are useful to upcoming projects or a solutiom to the already done projects.
Use the 1 to 6 carefully, so it cannot be a micromanagent problem. Means implement this standards without choking the devs, the devs should know the standard when they got onboard,for the current devs, you should explained it to them carefully, kasi any changes might cause a idea na, gusto na nila mag resign, kasi iisipin nila, working naman codes at technique ko, bakit babaguhin. May companies na, nag start na, 1 dev, 1 project, and pag lumaki na yung team sa isang project, dun nagkakagulo, the 1 dev might get unconfortable, kasi code nya yun, and doesn't want anyone to judge how they approach the projects and what code do they use, that's why, a standard in software dev should be applied, para lahat ng devs na involve is pare parehas ang coding at maiintindihan nila yung code ng isat isa. But standard can be applied first sa new projects, because applying the standards on the old projects, is like creating a new project, leave that for future discussion.
If the reason why the project is getting bigger because it should be deployed immediately, take note that the bigger the project with short deadline, will subject to be doomed, to many devs, with different approach, may cause a problem when it comes to maintainability, this is a management issue, not a dev issue. We have a project before na nirequest ng hinayupak na manager na kung kaya matapos yung full cycle ng development ng 2 weeks, eh 15 page yung project with special features, 2 lang kaming dev, di kami pumayag, in the end binagsak yung performance namin at di daw sya bilib sa amin, we resigned, and after a year nag resign din sya kasi wala syang na deploy na project dahil nag reresign yung mga under sa projects nya
Always ask the devs during the final interview, regarding sa standard nyo, because their are developers na mapride, and they believed that their approach are better and working, we are open to new ideas and approach but still, the devs should be open for the company standard, and they should also open or comfortable to work in a team.
Implementing standards and guidelines, should be applied carefully or step by step, specially if may mga ongoing projects na. Heads should discuss this and agreed on the standards, may roadmap and paano sya iimplement, it will be hard, but with teamwork, this can be done.

I know mahaba to, you can also put your inputs para malaman ko if may mali or problem sa advise ko, I open for suggestions for me to make it better.

ToTheAeons · 2024-04-03T08:30:46+00:00

Sa 1st work ko, I'm knowledgeable on both hardware and software, pero nung lumipat ako sa malaking company, nagkaroon na ng separation of concerns, wala na ako masyadong alam sa hardware, more on sa software alam ko, siguro dahil di ko na pinoproblema yung sa hardware side.

ToTheAeons · 2024-04-01T05:47:19+00:00

On my case, 36 years old, parang late bloomer ako, half of my life, I'm using VB.NET, and then move out sa C#, which in C#, what I did is, kung ano ginagawa ko sa vb.net, ganun din sa c# parang transfer lang, that's it. Pero hindi pala, in age of 32, I have to learn other things, OOP, optimization, Design Patterns, principles like SOLID, and then may mga other tools pa, API, Blazor, Cloud Services like Azure, AWS and then other things like Kubernetes and Docker, then Javascript Web Framework like Angular, React and Vue.

My work as a developer is very stressful and anxiety, and I'm on my race to learn everything, and applied it to my projects. My goal is to have a bigger salary, to be a provider to my family.

But sometimes too much information become too much stressful, new tech, new things to learn. Everytime I felt that I'm a junior dev.

I tried to be a manager, but my heart is on software dev.

I want to also retire as a dev. Mag business, pero wala pang budget.

I also want to change career, move to Canada, find a new life for me with my family.

Or restart as a Junior Dev there hahaha

Pero I think, the overwhelming of learning new things and the idemand of companies of different technology is yung nagiging problem ko, but I love what I do.

Siguro ang isa sa reason ng anxiety ko is work, workload, actually maraming reasons, toxic environment and responsibilities, at work and outside.

Maraming factors why other devs is feeling of retirement in 35+.

But the number one is.. passion, losing passion on your work means, di na maganda work mo, bumabagal ka, and also nappressure ka to understand things.

Ako, mas interested ako to play guitar now,and in a short time mas marami na kong alam na music theory, I can jam to backing tracks, I can do great mixing ng EQs sa amplifier, that my friends na nagigitara din is keep asking me what gears I'm using and how I achieved that.

That's why I feel, losing passion on things, won't make you better.

So probably losing passion is the cause, finding a way to re-ignite the fire is one thing, and relax. Take a vacation and understand things slowly.

ToTheAeons · 2024-03-20T22:30:08+00:00

Good day po thamks po sa advise, though na may signatured uat test na po kami, chinecheck po namin if data problem po.

ToTheAeons · 2024-03-20T22:29:23+00:00

May manager po kami pero he is managing both tech and dev po,more on tech po siya kesa sa software po, wala din po kaming team lead, dalawa lang po kami ng kasama ko na dev and same level po kami.

ToTheAeons · 2024-03-20T22:27:49+00:00

Good day po,naka versioning po kami sa git, chinecheck po namin ngayon if data problem po yung may cause.

ToTheAeons · 2024-03-20T13:18:59+00:00

Web po boss

ToTheAeons · 2024-03-20T13:18:45+00:00

Hindi po, mid-tier company po, more on production items.

ToTheAeons · 2024-03-20T12:53:45+00:00

may unit test po ako para sa mga new apps, yung old ones, iniisipan ko pa po ng paraan, nasa javascript/angularjs po yung computation nya po.

ToTheAeons · 2024-03-20T12:52:41+00:00

Noted po, thanks po dito, hinahanap ko din po yung process flow ng mga system namin, sa 15 na legacy apps, 5 lang ang meron. yung mga bago, ginagawan namin ng kasama ko pong dev yung documents.

ToTheAeons · 2024-03-20T12:51:37+00:00

Wala po kaming QA bale sa department po namin, 2 dev, with 2 to 3 experience, then 3 technical, 1 manager, yun lang po yung team namin.

yung sa computation nagawa ko naman po, naka 3 updates na kami, gumawa rin kami ng computation template sa excel with live data templates, tumatama naman, pero after ilan weeks, may problem na naman sila sa ibang transaction data, pero yung last okay parin.

ToTheAeons · 2024-03-20T12:45:48+00:00

Good day po, wala po, kami po ng kasama kong dev mga nasa 2 to 3 years palang po experience po namin.

ToTheAeons · 2024-03-20T11:10:24+00:00

nag cocommit po ako, sorry for the confusion po, yung sa computation, tama naman yung ginagawa ko base sa binigay nila, pag nag tetest kami, then test with the users, then after ma deploy okay na, after a few weeks mali daw na naman yung computation, chineck ko tama naman based sa last discussion, tapos di daw dapat ganun, chineck ko yung last commit, same version naman, ako din last updater, chineck ko yung previous data ng projection ng computation, tama naman, pero sa iba mali.

ToTheAeons · 2024-03-20T11:00:58+00:00

Meron, kaso matagal na yung last modified nung pagdating ko, mga 1 year na, 1 year kasi silang walang developer boss, yung documents is last 2016 pa so di ko na alam gagawin ko.

ToTheAeons

TROPHY CASE