Skip to main content

Java and Project Manager

Java and Project Manager are like bread and jam. We can’t separate both.

Java Technical project manager helps the team in design, troubleshooting and deployment the code.

We need to develop our skills on below:

OOP stands for Object-Oriented Programming.
Classes and objects are the two main aspects of object-oriented programming.     

Core Java:


Core Java starts with Class/Objects, Class Attributes, Class Methods, Constructors,
Modifiers (public, private, default, protected), Encapsulation(getter/setter), package, Inheritance (Subclass and Superclass), Polymorphism, Interface, Exceptions and much more.

Multithreading:

Multithreading in Java is a process of executing two or more threads simultaneously to maximum utilization of CPU. Multithreaded applications execute two or more

threads run concurrently. Hence, it is also known as Concurrency in Java.

Each thread runs parallel to each other.

Multiple threads don’t allocate separate memory area, hence they save memory. Also, context switching between threads takes less time.


Benefits of Multithreading: Improved throughput. Simultaneous and fully symmetric use of multiple processors for computation

and I/O. Superior application responsiveness Improved server responsiveness Minimized system resource usage Program structure simplification Better communication

J2EE:

The J2EE application model is a multi-tier application model. Application components are managed in

the middle tier by containers. A container is a standard runtime environment that provides services,

including life cycle management, deployment, and security services, to application components.

This container-based model separates business logic from system infrastructure.


Design Pattern:

When we are developing software, some common problems like repetitive code, adding extra properties or redundant functions are bound to occur. Design patterns are smart and reusable solutions for these problems, saving considerable time and effort for developers.


Spring Core:

Core (spring-core) is the core of the framework that power features such as Inversion of Control and dependency injection. Beans (spring-beans) provides Beanfactory, which is a sophisticated implementation of the factory pattern.


Spring MVC:

A Spring MVC is a Java framework which is used to build web applications.

It follows the Model-View-Controller design pattern. It implements all the basic

features of a core spring framework like Inversion of Control, Dependency Injection.

A Spring MVC provides an elegant solution to use MVC in spring framework by the

help of DispatcherServlet. Here, DispatcherServlet is a class that receives the

incoming request and maps it to the right resource such as controllers, models,

and views.

Advantages of Spring:

  • It is a lightweight framework.
  • It does not support tag library.
  • It has loosely coupled modules.
  • It is integrated with ORM Technologies using which, lesser coding is required after and before the main logic.
  • It has a layered MVC architecture containing 3 layers for modelling, viewing and controller.

Spring Batch:

A lightweight, comprehensive batch framework designed to enable the development of robust batch applications vital for the daily operations of enterprise systems. Spring Batch provides reusable functions that are essential in processing large volumes of records, including logging/tracing, transaction management, job processing statistics, job restart, skip, and resource management. It also provides more advanced technical services and features that will enable extremely high-volume and high performance batch jobs through optimization and partitioning techniques. Simple as well as complex, high-volume batch jobs can leverage the framework in a highly scalable manner to process significant volumes of information.


Web services SOAP/REST:


Database:
Java Database Connectivity (JDBC) is an application programming interface (API) for the programming language Java, which defines how a client may access a database. It is a Java-based data access technology used for Java database connectivity. It is part of the Java Standard Edition platform, from Oracle Corporation. It provides methods to query and update data in a database, and is oriented toward relational databases. A JDBC-to-ODBC bridge enables connections to any ODBC (Open Database Connectivity) -accessible data source in the Java virtual machine (JVM) host environment.



Comments

Popular posts from this blog

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - archite

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir

Lessons learned from sprint retrospective meeting

Scenario: Team Missed Sprint Goals Challenge: A development team consistently missed its sprint goals, leading to frustration and a drop in morale. Team members felt overwhelmed by the workload and struggled to communicate effectively. Retrospective Insights: During the retrospective, team members openly discussed their challenges and frustrations. They identified bottlenecks in communication, unclear priorities, and unrealistic expectations. The team realized that individual workloads were not evenly distributed, causing burnout for some members. Lessons Learned: Effective Communication Matters: The team recognized the importance of clear communication. They committed to regular stand-up meetings, where everyone shared progress, blockers, and priorities. Balancing Workloads: The retrospective highlighted the need to distribute tasks more evenly. They decided to monitor workloads and adjust assignments accordingly. Setting Realistic Goals: The team acknowledged that setting achievable