The purpose of a certification is to formally verify and confirm that you have a set of skills, not as a reason to learn something new. If you want to learn, then you should learn by reading, doing, and asking questions. Building a strong portfolio of projects that you have worked with is just as beneficial as a certification in demonstrating your knowledge and abilities as a software developer.
I would also shy away from certifications that focus on a particular technology or are sponsored by a particular vendor. Technologies change over time. They might evolve, or they might go out of favor. Perhaps you find a new job where having the certification means absolutely nothing because those technologies aren't used. When you get a certification, it should be from a respected organization (which varies depending on your geographic location as well as industry) and be something that helps you develop professionally and advance your career.
If you want to go a certification route, I recommend looking at vendor-neutral and broad-based certifications. For general software engineering knowledge, that would be the IEEE's CSDA and CSDP certifications. For security, perhaps the ISC2 certifications. For project management, the PMI is well respected. Depending on where you work, CMMI, Lean, and Six Sigma training and certifications might be beneficial.