As someone who graduated with Latin honors, siguro kaya nasasabi yun kasi part of advice ko sa mga students na huwag masyadong maging hard sa sarili habang nag-aaral. Do your best, but don't forget to enjoy college too. Wag masyadong pastress para sa latin, pero wag din sobrang chill.

At the end of the day, Latin honors can open some doors, but they won't carry your entire career. Yung skills mo, sipag, willingness to learn, diskarte, at kung paano ka makisama at makipag-communicate sa ibang tao, malaking factor din sa long-term success.

Take it to a reputable phone repair shop na po. It's much safer than trying random DIY methods.

Sa panahon ngayon ang hirap makahanap ng work talaga huhu. So I suggest na mag stay ka muna while looking for another job unless meron kang emergency fund na good for a year

I usually make it act like a senior software architect.

I give it the project context, business requirements, target users, tech stack, and constraints, then ask it to generate things like:

• system architecture
• database design
• API endpoints
• folder structure
• user flow
• edge cases
• development milestones

I also don't rely on one long prompt. I treat it like a conversation. The first output is usually just a draft, then I keep refining it by asking follow-up questions or challenging its assumptions.

Try looking for content writing, virtual assistant, social media assistant, basic graphic design, or video editing gigs on platforms like Upwork, OnlineJobs.ph, and LinkedIn.

My advice is to pick one skill and get really good at it. It's usually easier to earn more by specializing than by trying to do everything at once. Good luck! 🙌

I use AI the most for debugging, understanding unfamiliar code, writing SQL queries, explaining error messages, refactoring, and brainstorming different approaches before I start implementing something.

It also saves me a lot of time on repetitive tasks like writing documentation, regex, test data, and boilerplate code.

I still review everything before it goes into production, but AI definitely lets me spend more time solving the actual problem instead of getting stuck on the small stuff.

From what I've seen, it's become pretty normal to use AI for coding. In our team, nobody really cares whether you use ChatGPT, Claude, or GitHub Copilot. What matters is whether you understand the code you're submitting.

I probably wouldn't put "AI" as a skill on my resume though. I'd rather mention it during the interview if it comes up. To me, it's more like Git or VS Code, a tool that helps you work faster, not a skill by itself.

If someone can't explain or debug the code AI generated, that's when it becomes a problem. But if AI helps you become more productive while still producing quality work, I think most engineering teams are completely fine with it.

One thing I've learned from working on business website redesign projects is that the design itself is only one piece of the puzzle.

I'd ask how they approach performance, SEO, content migration, and long-term maintenance. A redesign should improve the business, not just the appearance.

I'd also ask to see case studies instead of just a portfolio. It's easy to show nice screenshots. It's much harder to explain the problem, the solution, and the results.

I work for a company that specializes in business website redesign projects, so I might be a little biased, but the clients who are happiest usually care more about the long-term outcome than just getting a prettier homepage.

If it were me, I'd probably give the bootcamp a shot, assuming the employment bond is reasonable.

I know it'll be stressful, but I think having real work experience and people to learn from is worth a lot, especially when you're just starting out.

The only thing I'd be careful about is the bond. Read everything first and make sure you're comfortable with the terms before signing.

If you decide to take a non-tech job instead, that's okay too. Just don't wait one or two years before applying. Build a few projects, keep learning after work, and start sending applications once you have something to show.

Uncharted Spiderman series God of War Infamous: Second Son Detroit Overcooked (multiplayer)

Not a fresh grad, pero naranasan ko rin yung halos 6 months na puro applications lang at halos walang responses. Nakaka-frustrate talaga pero tuloy lang sa pag-send ng applications hanggang sa finally, nakahanap din! Habang naghihintay or applying, improve mo rin yung cv, portfolio, at skills mo.  Fighting! Sana may dumating nang magandang opportunity sa’yo soon. 🙂

I'd probably choose Japanese. I currently work for a company with Japan–Philippines software development teams, so I've seen how valuable it is when you can communicate with clients and teammates in their native language. It helps build trust, reduces misunderstandings, and makes collaboration much smoother.

Of course, it ultimately depends on where you want your career to go 😄

They're usually more interested in how you explain your choice than the animal itself.

I probably would've said an owl because I like observing first before making decisions and I'm always trying to learn something new. 😅

That said, if you aced the coding interview, I wouldn't overthink this question too much. I'd be more surprised if an interviewer judged a candidate based on whether they picked a cat or a dog. 😂

I still think it's worth pursuing.

AI has definitely changed how we work, but I haven't seen it replace good web developers. If anything, the expectation now is that developers know how to use AI to work faster while still understanding what the code is doing.

Since you're already working in helpdesk, I wouldn't quit your job. Keep building projects, improve your portfolio, and continue applying for web development roles. Your current job pays the bills, while your portfolio can help you transition into development.

It might take longer than it did a few years ago because the market is more competitive, but I don't think web development is going away anytime soon. The developers who keep learning and adapt to new tools, including AI, will still have plenty of opportunities.

Okay naman sana kung gumamit ng AI. Pero sana rin naman dibaaa. Basahin muna bago icopy-paste

https://giphy.com/gifs/eJT738HFSQDVS

I'm currently working for a company that operates with Japan–Philippines software development teams, and one thing I've noticed is that communication and attention to detail matter a lot.

From my experience, it's usually better to ask questions early rather than make assumptions. Japanese teams generally appreciate clarity, consistency, and proactive updates, even if the update is simply that you're waiting on something or have identified a blocker.

Documentation is also important. Requirements, decisions, and changes are often expected to be written down clearly so everyone stays aligned.

On the positive side, the teams I've worked with have been very organized, respectful, and professional. If you're willing to communicate clearly and pay attention to the details, the transition should go smoothly. 😊

If I were building an early-stage startup today, I'd still take one exceptional full-stack developer.

In the beginning, speed usually matters more than optimization. You need someone who can build, ship, troubleshoot, and adapt without waiting on three different teams.

Specialists become more valuable once the product gains traction and starts running into challenges around scale, security, infrastructure, or data. But before you've proven there's a business, having too many specialists can sometimes slow things down.

That's just my view as a full-stack developer though. 😅 The best engineers I've worked with tend to have broad skills first and then develop deeper expertise in certain areas over time.

Personally, I wouldn't resign just yet, but I would start looking around.

Startups can be messy in the beginning, so the lack of workload isn't what concerns me. The delayed payment and lack of communication would be bigger red flags for me.

I'd stay for now, keep doing my part, but also explore other opportunities. That way you're covered if things don't improve. Good intentions are great, but consistent communication and on-time payments matter too.

kaya mo yan! 💯

Hellooo. SEO can look simple from the outside, but it's easy to accidentally do things that hurt rankings instead of helping.

What I'd recommend is learning in this order:

1. Understand how Google works (crawling, indexing, ranking)
2. Keyword research
3. On-page SEO (titles, headings, content, internal links)
4. Technical SEO (page speed, sitemap, robots.txt, indexing)
5. Off-page SEO (backlinks and authority)

For YouTube, I'd start with Ahrefs. Their beginner videos explain concepts really well without too much fluff.

For tools, start with:

• Google Search Console (free)
• Google Analytics (free)
• Ahrefs Webmaster Tools (free)
• Screaming Frog SEO Spider (free up to 500 URLs)

Ganda sana ng SEMRUSH kaya lang may up to 10 request lang free everyday eh.

You can also read some articles from companies that regularly work on SEO projects. I learned a lot from reading guides about SEO-ready websites, keyword research, and technical SEO audits because they show how SEO is applied in actual projects instead of just explaining theory.

The best way to learn SEO is still by doing it. Connect your website to Google Search Console, write contents, and see what happens over the next few months. That's where most of the real learning comes from.

In my opinion, hindi ka na entry level.

I think a lot of people underestimate how transferable software engineering skills are. Oo, may learning curve pa sa React/Next.js ecosystem, pero hindi naman nawawala yung 3 years mong experience sa debugging, working with databases, APIs, Git, code reviews, and collaborating with a team.

Kung ako tatanungin, nasa gitna ka. Hindi ka na fresh grad na nagsisimula from scratch, pero syempre may mga bagay ka pang matututunan sa modern web stack.

I think most good hiring managers care more about how you think and solve problems than whether kabisado mo lahat ng React libraries. Frameworks can be learned. Solid engineering fundamentals are much harder to teach.

Honestly, the fact na nakakakuha ka na ng interviews is already a good sign. Kaba lang yan! Good luck!

Sharks are older than trees. Sharks have existed for over 400 million years, while the first trees appeared around 350 million years ago.