Details
-
Aboutbrick layer
-
Skillsjava, android, web
-
LocationManila
-
Website
-
Github
Joined devRant on 3/17/2018
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
-
Worst part about my job is training junior devs with their supervisor insisting them to write unit tests without prior programming experience2
-
Life is too short to have commented codes; don't want to go back to it once it shows up in the static code analysis scan9
-
Work from home policy is still in our managers discretion - manager can just say to stay within the building and to stop buying coffee outside
Clinic is not giving away masks readily unless an employee has cough or colds7 -
I dunno why but I'm sold by AWS and how anyone may start off on the right note when starting a "startup" project. A lot of IT folks I know have vouched for it as well. Maybe because I'm engineering graduate and I have put the costs and maintainability on top of the checklist. I even plan to take the SAA certification since it was also surveyed as one of top paying IT certs to get. But mostly I care about the stuff I can learn and rely on its ecosystem. Tell me something I should be wary about this cloud provider. Coz maybe I'm just too "sold" by the hype.1
-
It's weird that I feel okay with team leads or managers who I know are lying about facts, just to motivate the team in some way. I mean I might lose respect to that person but I would somehow commend their people skills. A pat in the back goes a long way2
-
Not just for hobbies, better make some money out of it. Otherwise, it becomes more of skills upgrade. Collaborate and try really make $$$. It's all about extra $$$
-
As a noob developer, I once scaffold a sample project using JHipster, left it for awhile, went back, tried to run it again and basically, spent a whole day downloading updates and recreating the project from scratch (not to mention being lost in the whole stack and project itself, enabling it to run but failing to understanding each stack components)
-
Two (2) senior developers and one (1) senior tester left our team and I am left with two (2) Java legacy applications that are hard to maintain. Here is a list of things I hate about these old webapps (let's call them app A and B):
1. App A depends on 80% web services. If one web service for a product or warehouse goes down, work flow is impeded while prod support team checks with the core services team for repair
2. App B is a maven project with multiple modules dependent on libraries that are dependent on company's internal libraries. So if we want to upgrade to OpenJdk 9 and up, the project will definitely produce a lot of errors due to deprecated/unsupported codes
3. App A is dependent on Tibco and I have no experience on that
4. App B's continuous integration build tool is Jenkins and the jobs that build it has a shell script that wasn't updated during the tech upgrade enhancement. The previous developer who did the knowledge transfer to me didn't tell me about this (it should be considered a defect on her part but she already resigned)
5. App A when loaded in eclipse IDE is a pain to work with since it is only allowed to build a war file using ant. I have to lookup in quick search instead of calling shortcuts (call hierarchy) because the project wasn't compiled via eclipse.
6. It's impossible to debug app A because of #5
7. Both applications have high priority and complex enhancements and I have no other teammates to help me
8. You never know what else can go wrong anytime1 -
A senior developer would ask me to drink in the bar where we talk about dev and non dev related stuff, almost every night after work10
-
Nothing gives me more satisfaction in backend development than encountering errors/exceptions. It brightens up my day to know that something is happening and i get to keep my job, too2
-
If you compare a software developer's job with another, let's say a doctor or a lawyer, the former doesn't require mastery and there is continuous chase on fast changing version numbers or an entire platform coming out. Former innovates without question and gets burned out in the process. While the latter demands mastery of certain fields and the specialization isn't diverse enough compared to former. Yet the pay for latter might be higher. What are the pros and cons have you felt as a developer and how do you cope to address it internally? Is it just the thrill and excitement of new things coming out? What fulfillment do we get aside from the satisfaction of clean code, unit test and successful deployments? How much impact have we really given? And is there a place for developers to final settle down? Don't get me wrong; I won't stop until death probably but I hope adulting responsibilites won't make us break.
-
Manager wants to sign me up for sponsored Apigee training and certification and i wasn't sure if it's good or bad (even now)
Me: ohh, nice
Manager: let me know asap. I'll get back to you.
*Manager comes back after 2 mins*
Manager: have you decided?
Me: uhm, yeah i haven't finished looking. I'll get back to you in 30mins
*Manager comes back after an hour*
Me: does this have a bond?
Manager: no
Me: okay, I'll get back to you tom
Poll question: is it a go or no go?1 -
Me: *watching Google i/o 2018*
Me (thinking to myself): wow that looks useful! I'll probably use that use after 5 years at work -
Working on legacy code with Ant/CVS setup. I tried for a day but easily gave up and abandoned the idea of running locally using maven
-
Tester waits for the batch job to take effect by receiving emails, until he realizes that it is impossible to receive any mail since password has already expired
-
When you take a bathroom break thinking of code while absentmindedly soaking your pants and shoes with pee1
-
-release an app (legally)
-stay healthy + avoid sickness
-speak conversational Mandarin
-build passive income (optional)
-get out of toxic work relationship/s (optional)3