ma1iket

Java Developer. I was involved in the development of modular monolith. Base architecture - Java 21, Postgres, AWS. A lot of deferent AI tools and integrations. In PR review such as Cubit, Sentry, Claude and other. You should write code a bit as possible. All should be created with Claude. Project was configured especially for AI development. Main AI config, modular configs. A lot of AI rules, common skills, context optimization recommendations. Was On-call element. Regular I have should be on-call for supports some customer questions and incident fixes. AI also was integrated here (Vanna AI). For supporting of requested SQL queries for customer reports. So customer for begin had asked Vanna AI and then, if it not enough, they ask on-call person. Also was knowlage sharing element. On each friday somebody should to present to team some new interesting information for project upgrade. Usually it was about AI upgrade. How we can to code more quicklly and with higher quaility. Frontend was on web and mobile (React Native). So all soft was testing on IOS Simulator. Also integrated 3d-party services as Adjust, CircleWise for users metrics and analytics.

I've worked on was leading an open-source project for the Polkadot Foundation: building a debugger for smart contracts written in the Ink! framework. Why it was hard. I came into it knowing essentially nothing about three separate domains, all of which I had to learn deeply: DWARF debug symbols and the ELF binary format, the lifecycle of a blockchain node and how contracts execute inside it, and the internals of how a debugger actually works — breakpoints, symbol resolution, stepping through execution. On top of the technical learning curve, it was also my first time working in an open-source community and my first time assembling and leading a team for a project like this. What I did. I recruited and coordinated the team, broke the work into milestones aligned with the Foundation's grant structure, and went deep on the parts none of us had touched before — particularly mapping DWARF symbols onto Ink!-compiled WebAssembly so a debugger could actually attach meaningful state to running contracts. I owned the open-source side of it: communication with the Foundation, code review cycles, milestone reporting. Outcome. We successfully delivered the first milestone, passed the Foundation's code review, and received the corresponding grant tranche. The project stalled after that — but for a structural reason, not a technical one. The Polkadot Foundation cancelled financial support for the Ink! framework as a whole. Continuing would have required the Ink! team on their side to expose DWARF symbols from contract builds (currently stripped because they always compile with --release), and without funding there was no incentive for anyone to do that work. What I took from it. Three things. The willingness to start a project where I don't know the foundational tech yet and learn it on the way. Practical experience leading a small team through a complex, unfamiliar domain. And a much more realistic understanding of how external dependencies — funding, upstream cooperation — can decide a project's fate independent of how well the code is written.

Full stack developer (Java, React) I was involved in the development of micro-service architecture, on Java 8 - 17, and also helped write the frontend on React. All micro-services on Java 8 were running in WebSphere, on Java 17 in OpenShift. The tasks were very different, from implementing some business logic to the architecture of your own service and raising and configuring it in WebSphere or OpenShift. There were also tasks on migrating projects from Java 8 to Java 17. Often from Spring to Spring Boot. Micros-ervices communicated with each other both via REST and through the ActiveMQ broker. It was necessary to optimize large queries in the database, breaking them into smaller ones with indexing and merging all this in multithreading. I also had experience in generating PDF, Word, Excel documents on the backend and displaying them on React. Frontend work was limited to displaying various forms with tables and documents. All communication was in English, except for calls in a team without a client. Communication with the database was via JPA. The database is Oracle.

I was involved in the project from the very beginning on Java 8 (Spring Boot) + Angular. These were 2 monoliths that communicated with each other via the Rabbit broker. One such monolith had to work offline and have the ability to synchronize all data with the other monolith when receiving a connection. A bunch of documents also had to be synchronized. I also worked with the EDS, for signing requests and documents. I also worked with document generation (Excel, PDF, Word). On the frontend, they had to be displayed in the Only Office editor. I also wrote my own mini framework for tracking changes in the database and redirecting all data to the admin panel in Angular. Communication with the database was via JPA. The database is Postgres.