u/yeeboixD

Ano na, mga paps/mams! Baka may mga taga-South dyan (Alabang, Cavite, Laguna, batangas area) na walang magawa bukas ng umaga at gustong mag-unat-unat ng gulong?

May mabilisang tambike and chill ride lang kami bukas. No fixed route pa naman, baka dumeretso lang somewhere na masarap mag-kape at mag-kwentuhan bago sumabak uli sa Monday breakdown haha.

• Pace: Chill lang talaga, walang karera. Takbong pogi/ganda lang.
• Bike: Kahit ano paps! Scooters, underbones, big bikes—basta safe itakbo, welcome na welcome. Walang iwanan dito.
• Meetup: Target sana namin maaga para iwas sa tindi ng init at traffic. Set na lang tayo ng meetup point sa isang Shell o Petron para sabay-sabay na.

Drop a comment below or DM niyo ako kung g kayo para mai-add ko kayo sa GC and mapag-usapan yung exact time.

Ride safe sa lahat at kitakits bukas! 🏍️☕

Ano na, mga paps/mams! Baka may mga taga-South dyan (Alabang, Cavite, Laguna, batangas area) na walang magawa bukas ng umaga at gustong mag-unat-unat ng gulong?

May mabilisang tambike and chill ride lang kami bukas. No fixed route pa naman, baka dumeretso lang somewhere na masarap mag-kape at mag-kwentuhan bago sumabak uli sa Monday breakdown haha.

Pace: Chill lang talaga, walang karera. Takbong pogi/ganda lang.

Bike: Kahit ano paps! Scooters, underbones, big bikes—basta safe itakbo, welcome na welcome. Walang iwanan dito.

Meetup: Target sana namin maaga para iwas sa tindi ng init at traffic. Set na lang tayo ng meetup point sa isang Shell o Petron para sabay-sabay na.

Drop a comment below or DM niyo ako kung g kayo para mai-add ko kayo sa GC and mapag-usapan yung exact time.

Ride safe sa lahat at kitakits bukas! 🏍️☕

Hello guys, planning kami bumuo ng ride group sa south para sa mga gusto mag rides at tambike na mga taga south. If interested kayo just message me or leave a comment. Lets go!

Hey everyone,

​Quick update from my previous post about officially moving into the network team! I am exactly one week into the new role, and man, my brain is totally fried. Going from passwords and user tickets to enterprise infrastructure feels like drinking out of a firehose. On top of that, my calendar is packed with meetings all day long, and I'm still trying to squeeze in time to study my Jeremy's IT Lab course after hours.

​They already handed me the deliverables for our 2 new floors, and I’m expected to fully handle the project execution this upcoming July and August:

​Network as-built diagram, IP/VLAN plan, port map, & config backups

​Test results, implementation evidence, & CMDB record uploads

​Switches OS upgrade & Vulnerability scans

​Devices configuration change submit, Labeling, & DHCP Vlan Scope

​Design/validate network build for new floors (IP plan, VLANs, trunking, STP)

​Configure/stage switches and coordinate turn-up (fiber links between old - new floors)

​Ensure wireless readiness (SSIDs/security/AP connectivity)

​Execute network testing (LAN/Wi-Fi, VLAN reachability, redundancy) during cutover

​Provide all final network documentation updates

​Between meetings, they’re onboarding me onto daily operations and tools. It's a massive wave of

information:

​Monitoring: NetFlow, Kibana, Zabbix, and Scrutinizer.

​Daily Tasks: Config backups, OS upgrades, VPN setups, and tracking BGP routes.

Cloud: They've also started teaching me Azure cloud networking on top of everything else.

​Admin: Ticket handling, ISP vendor coordination, and ISP billing.

​I’m stoked to be here, but bouncing from calls straight into this checklist while navigating four new monitoring tools and trying to study makes me feel like I know nothing.

​Is it normal for a company to drop a full multi-floor buildout to be executed in the next two months, routing/ops, and four different monitoring tools on a fresh network engineer in their very first week?

Did anyone else feel completely underwater during their first few weeks out of helpdesk, or am I just in the deep end?

Hey everyone,

​Quick update from my previous post about officially moving into the network team! I am exactly one week into the new role, and man, my brain is totally fried. Going from passwords and user tickets to enterprise infrastructure feels like drinking out of a firehose. On top of that, my calendar is packed with meetings all day long, and I'm still trying to squeeze in time to study my Jeremy's IT Lab course after hours.

​They already handed me the deliverables for our 2 new floors, and I’m expected to fully handle the project execution this upcoming July and August:

​Network as-built diagram, IP/VLAN plan, port map, & config backups

​Test results, implementation evidence, & CMDB record uploads

​Switches OS upgrade & Vulnerability scans

​Devices configuration change submit, Labeling, & DHCP Vlan Scope

​Design/validate network build for new floors (IP plan, VLANs, trunking, STP)

​Configure/stage switches and coordinate turn-up (fiber links between old - new floors)

​Ensure wireless readiness (SSIDs/security/AP connectivity)

​Execute network testing (LAN/Wi-Fi, VLAN reachability, redundancy) during cutover

​Provide all final network documentation updates

​Between meetings, they’re onboarding me onto daily operations and tools. It's a massive wave of

information:

​Monitoring: NetFlow, Kibana, Zabbix, and Scrutinizer.

​Daily Tasks: Config backups, OS upgrades, VPN setups, and tracking BGP routes.

Cloud: They've also started teaching me Azure cloud networking on top of everything else

​Admin: Ticket handling, ISP vendor coordination, and ISP billing.

​I’m stoked to be here, but bouncing from calls straight into this checklist while navigating four new monitoring tools and trying to study makes me feel like I know nothing.

​Is it normal for a company to drop a full multi-floor buildout to be executed in the next two months, routing/ops, and four different monitoring tools on a fresh network engineer in their very first week?

Did anyone else feel completely underwater during their first few weeks out of helpdesk, or am I just in the deep end?

Hey everyone,

​Quick update from my previous post about officially moving into the network team! I am exactly one week into the new role, and man, my brain is totally fried. Going from passwords and user tickets to enterprise infrastructure feels like drinking out of a firehose. On top of that, my calendar is packed with meetings all day long, and I'm still trying to squeeze in time to study my Jeremy's IT Lab course after hours.

​They already handed me the deliverables for our 2 new floors, and I’m expected to fully handle the project execution this upcoming July and August:

​Network as-built diagram, IP/VLAN plan, port map, & config backups

​Test results, implementation evidence, & CMDB record uploads

​Switches OS upgrade & Vulnerability scans

​Devices configuration change submit, Labeling, & DHCP Vlan Scope

​Design/validate network build for new floors (IP plan, VLANs, trunking, STP)

​Configure/stage switches and coordinate turn-up (fiber links between old - new floors)

​Ensure wireless readiness (SSIDs/security/AP connectivity)

​Execute network testing (LAN/Wi-Fi, VLAN reachability, redundancy) during cutover

​Provide all final network documentation updates

​Between meetings, they’re onboarding me onto daily operations and tools. It's a massive wave of

information:

​Monitoring: NetFlow, Kibana, Zabbix, and Scrutinizer.

​Daily Tasks: Config backups, OS upgrades, VPN setups, and tracking BGP routes.

Cloud: They've also started teaching me Azure cloud networking on top of everything else. ​Admin: Ticket handling, ISP vendor coordination, and ISP billing.

​I’m stoked to be here, but bouncing from calls straight into this checklist while navigating four new monitoring tools and trying to study makes me feel like I know nothing.

​Is it normal for a company to drop a full multi-floor buildout to be executed in the next two months, routing/ops, and four different monitoring tools on a fresh network engineer in their very first week?

Did anyone else feel completely underwater during their first few weeks out of helpdesk, or am I just in the deep end?

Hey everyone,

​Quick update from my previous post about officially moving into the network team! I am exactly one week into the new role, and man, my brain is totally fried. Going from passwords and user tickets to enterprise infrastructure feels like drinking out of a firehose. On top of that, my calendar is packed with meetings all day long, and I'm still trying to squeeze in time to study my Jeremy's IT Lab course after hours.

​They already handed me the deliverables for our 2 new floors, and I’m expected to fully handle the project execution this upcoming July and August:

​Network as-built diagram, IP/VLAN plan, port map, & config backups

​Test results, implementation evidence, & CMDB record uploads

​Switches OS upgrade & Vulnerability scans

​Devices configuration change submit, Labeling, & DHCP Vlan Scope

​Design/validate network build for new floors (IP plan, VLANs, trunking, STP)

​Configure/stage switches and coordinate turn-up (fiber links between old - new floors)

​Ensure wireless readiness (SSIDs/security/AP connectivity)

​Execute network testing (LAN/Wi-Fi, VLAN reachability, redundancy) during cutover

​Provide all final network documentation updates

​Between meetings, they’re onboarding me onto daily operations and tools. It's a massive wave of

information:

​Monitoring: NetFlow, Kibana, Zabbix, and Scrutinizer.

​Daily Tasks: Config backups, OS upgrades, VPN setups, and tracking BGP routes. Cloud: They've also started teaching me Azure cloud networking on top of everything else.

Cloud: They've also started teaching me Azure cloud networking on top of everything else. ​Admin: Ticket handling, ISP vendor coordination, and ISP billing.

​I’m stoked to be here, but bouncing from calls straight into this checklist while navigating four new monitoring tools and trying to study makes me feel like I know nothing.

​Is it normal for a company to drop a full multi-floor buildout to be executed in the next two months, routing/ops, and four different monitoring tools on a fresh network engineer in their very first week?

Did anyone else feel completely underwater during their first few weeks out of helpdesk, or am I just in the deep end?

Hey everyone,

​Quick update from my previous post about officially moving into the network team! I am exactly one week into the new role, and man, my brain is totally fried. Going from passwords and user tickets to enterprise infrastructure feels like drinking out of a firehose. On top of that, my calendar is packed with meetings all day long, and I'm still trying to squeeze in time to study my Jeremy's IT Lab course after hours.

​They already handed me the deliverables for our 2 new floors, and I’m expected to fully handle the project execution this upcoming July and August:

​Network as-built diagram, IP/VLAN plan, port map, & config backups

​Test results, implementation evidence, & CMDB record uploads

​Switches OS upgrade & Vulnerability scans

​Devices configuration change submit, Labeling, & DHCP Vlan Scope

​Design/validate network build for new floors (IP plan, VLANs, trunking, STP)

​Configure/stage switches and coordinate turn-up (fiber links between old - new floors)

​Ensure wireless readiness (SSIDs/security/AP connectivity)

​Execute network testing (LAN/Wi-Fi, VLAN reachability, redundancy) during cutover

​Provide all final network documentation updates

​Between meetings, they’re onboarding me onto daily operations and tools. It's a massive wave of

information:

​Monitoring: NetFlow, Kibana, Zabbix, and Scrutinizer.

​Daily Tasks: Config backups, OS upgrades, VPN setups, and tracking BGP routes.

Cloud: They've also started teaching me Azure cloud networking on top of everything else.

​Admin: Ticket handling, ISP vendor coordination, and ISP billing.

​I’m stoked to be here, but bouncing from calls straight into this checklist while navigating four new monitoring tools and trying to study makes me feel like I know nothing.

​Is it normal for a company to drop a full multi-floor buildout to be executed in the next two months, routing/ops, and four different monitoring tools on a fresh network engineer in their very first week?

Did anyone else feel completely underwater during their first few weeks out of helpdesk, or am I just in the deep end?

Hey everyone,

​Quick update from my previous post about officially moving into the network team! I am exactly one week into the new role, and man, my brain is totally fried. Going from passwords and user tickets to enterprise infrastructure feels like drinking out of a firehose. On top of that, my calendar is packed with meetings all day long, and I'm still trying to squeeze in time to study my Jeremy's IT Lab course after hours.

​They already handed me the deliverables for our 2 new floors, and I’m expected to fully handle the project execution this upcoming July and August:

​Network as-built diagram, IP/VLAN plan, port map, & config backups

​Test results, implementation evidence, & CMDB record uploads

​Switches OS upgrade & Vulnerability scans

​Devices configuration change submit, Labeling, & DHCP Vlan Scope

​Design/validate network build for new floors (IP plan, VLANs, trunking, STP)

​Configure/stage switches and coordinate turn-up (fiber links between old - new floors)

​Ensure wireless readiness (SSIDs/security/AP connectivity)

​Execute network testing (LAN/Wi-Fi, VLAN reachability, redundancy) during cutover

​Provide all final network documentation updates

​Between meetings, they’re onboarding me onto daily operations and tools. It's a massive wave of

information:

​Monitoring: NetFlow, Kibana, Zabbix, and Scrutinizer.

​Daily Tasks: Config backups, OS upgrades, VPN setups, and tracking BGP routes.

Cloud: They've also started teaching me Azure cloud networking on top of everything else.

​Admin: Ticket handling, ISP vendor coordination, and ISP billing.

​I’m stoked to be here, but bouncing from calls straight into this checklist while navigating four new monitoring tools and trying to study makes me feel like I know nothing.

​Is it normal for a company to drop a full multi-floor buildout to be executed in the next two months, routing/ops, and four different monitoring tools on a fresh network engineer in their very first week?

Did anyone else feel completely underwater during their first few weeks out of helpdesk, or am I just in the deep end?

Just wanted to share a quick win. I officially signed the contract today to transition from my Helpdesk Engineer role into the Network Engineering department, starting this Monday, June 22!

​

​Since I'm the first network engineer in the country for our company, they are handing me full ownership of our upcoming infrastructure expansion. The 37th and 48th-floor server room buildouts haven't started yet, but I am confirmed to handle:

​

​Staging & Config: Leading the complete network configuration for both the 37th and 48th-floor server rooms.

​

​Project Tracking: Managing and tracking the end-to-end project timeline for the network team.

​Vendor & Team Coordination: Communicating with external vendors and aligning deployment needs with the helpdesk.

​

​Future Scale: Hopefully expanding to handle our other upcoming office buildouts across the country down the line.

​

​If you're currently grinding on the helpdesk, keep studying and pushing for infrastructure exposure. It pays off. Time to celebrate this weekend and hit the ground running on Monday! ☕⚡

Just wanted to share a quick win. I officially signed the contract today to transition from my Helpdesk Engineer role into the Network Engineering department, starting this Monday, June 22!

​

​Since I'm the first network engineer in the country for our company, they are handing me full ownership of our upcoming infrastructure expansion. The 37th and 48th-floor server room buildouts haven't started yet, but I am confirmed to handle:

​

​Staging & Config: Leading the complete network configuration for both the 37th and 48th-floor server rooms.

​

​Project Tracking: Managing and tracking the end-to-end project timeline for the network team.

​Vendor & Team Coordination: Communicating with external vendors and aligning deployment needs with the helpdesk.

​

​Future Scale: Hopefully expanding to handle our other upcoming office buildouts across the country down the line.

​

​If you're currently grinding on the helpdesk, keep studying and pushing for infrastructure exposure. It pays off. Time to celebrate this weekend and hit the ground running on Monday! ☕⚡

Just wanted to share a quick win. I officially signed the contract today to transition from my Helpdesk Engineer role into the Network Engineering department, starting this Monday, June 22!

​

​Since I'm the first network engineer in the country for our company, they are handing me full ownership of our upcoming infrastructure expansion. The 37th and 48th-floor server room buildouts haven't started yet, but I am confirmed to handle:

​

​Staging & Config: Leading the complete network configuration for both the 37th and 48th-floor server rooms.

​

​Project Tracking: Managing and tracking the end-to-end project timeline for the network team.

​Vendor & Team Coordination: Communicating with external vendors and aligning deployment needs with the helpdesk.

​

​Future Scale: Hopefully expanding to handle our other upcoming office buildouts across the country down the line.

​

​If you're currently grinding on the helpdesk, keep studying and pushing for infrastructure exposure. It pays off. Time to celebrate this weekend and hit the ground running on Monday! ☕⚡

Just wanted to share a quick win. I officially signed the contract today to transition from my Helpdesk Engineer role into the Network Engineering department, starting this Monday, June 22!

​

​Since I'm the first network engineer in the country for our company, they are handing me full ownership of our upcoming infrastructure expansion. The 37th and 48th-floor server room buildouts haven't started yet, but I am confirmed to handle:

​

​Staging & Config: Leading the complete network configuration for both the 37th and 48th-floor server rooms.

​

​Project Tracking: Managing and tracking the end-to-end project timeline for the network team.

​Vendor & Team Coordination: Communicating with external vendors and aligning deployment needs with the helpdesk.

​

​Future Scale: Hopefully expanding to handle our other upcoming office buildouts across the country down the line.

​

​If you're currently grinding on the helpdesk, keep studying and pushing for infrastructure exposure. It pays off. Time to celebrate this weekend and hit the ground running on Monday! ☕⚡

Just wanted to share a quick win. I officially signed the contract today to transition from my Helpdesk Engineer role into the Network Engineering department, starting this Monday, June 22!

​

​Since I'm the first network engineer in the country for our company, they are handing me full ownership of our upcoming infrastructure expansion. The 37th and 48th-floor server room buildouts haven't started yet, but I am confirmed to handle:

​

​Staging & Config: Leading the complete network configuration for both the 37th and 48th-floor server rooms.

​

​Project Tracking: Managing and tracking the end-to-end project timeline for the network team.

​Vendor & Team Coordination: Communicating with external vendors and aligning deployment needs with the helpdesk.

​

​Future Scale: Hopefully expanding to handle our other upcoming office buildouts across the country down the line.

​

​If you're currently grinding on the helpdesk, keep studying and pushing for infrastructure exposure. It pays off. Time to celebrate this weekend and hit the ground running on Monday! ☕⚡

so ayon nawawala yung keyfob ko and nalaman ko na closed yung home gym ko for about a month. Pano kaya ako makakapag pa replace ng keyfob if sarado home gym? pwede ba ako sa ibang branch mag pa replace ng keyfob?

24M here from the Philippines. I’ve realized I’ve been stuck in a cycle where I keep entertaining multiple women at the same time because I genuinely like different things about each of them, and they also genuinely seem to like me back. That’s what makes it harder for me to choose or let anyone go completely.

The problem is I also know it’s unfair because I can’t fully commit either. Here in the Philippines, exclusivity is a big deal for most girls and we obviously don’t practice polygamy, so I know continuing this setup long term will eventually hurt someone or make me lose all of them.

I think part of me likes keeping my options open because I’m afraid of choosing the wrong person or feeling like I missed out on someone better. But at the same time, I know this mindset is probably preventing me from building something deeper and more genuine with one person.

Has anyone here gone through the same phase before?

How did you eventually become more decisive or learn how to commit without feeling like you were losing everything else?

24M here from the Philippines. I’ve realized I’ve been stuck in a cycle where I keep entertaining multiple women at the same time because I genuinely like different things about each of them, and they also genuinely seem to like me back. That’s what makes it harder for me to choose or let anyone go completely.

The problem is I also know it’s unfair because I can’t fully commit either. Here in the Philippines, exclusivity is a big deal for most girls and we obviously don’t practice polygamy, so I know continuing this setup long term will eventually hurt someone or make me lose all of them.

I think part of me likes keeping my options open because I’m afraid of choosing the wrong person or feeling like I missed out on someone better. But at the same time, I know this mindset is probably preventing me from building something deeper and more genuine with one person.

Has anyone here gone through the same phase before?

How did you eventually become more decisive or learn how to commit without feeling like you were losing everything else?

24M here from the Philippines. I’ve realized I’ve been stuck in a cycle where I keep entertaining multiple women at the same time because I genuinely like different things about each of them, and they also genuinely seem to like me back. That’s what makes it harder for me to choose or let anyone go completely. The problem is I also know it’s unfair because I can’t fully commit either. Here in the Philippines, exclusivity is a big deal for most girls and we obviously don’t practice polygamy, so I know continuing this setup long term will eventually hurt someone or make me lose all of them. I think part of me likes keeping my options open because I’m afraid of choosing the wrong person or feeling like I missed out on someone better. But at the same time, I know this mindset is probably preventing me from building something deeper and more genuine with one person. Has anyone here gone through the same phase before? How did you eventually become more decisive or learn how to commit without feeling like you were losing everything else?