Suggestions
Paul Mikulskis
Full Stack Teach Lead @ Flipside Crypto | Platform Engineering | NOT available for fulltime hire, please do not message me about this.
Paul Mikulskis is currently serving as the Full Stack Tech Lead at Flipside Crypto, a position he holds in the Greater Boston area. His role involves overseeing the development and support of various projects within the company, focusing on platform engineering and full-stack development.
Professional Background
Before joining Flipside Crypto, Mikulskis accumulated experience in several other companies, including roles as a DevOps Engineer at LogRocket and positions at VMware and Carbon. This diverse background has equipped him with a robust skill set in both front-end and back-end technologies, which is essential for his current leadership role in tech development.135
Current Responsibilities
In his capacity as Full Stack Tech Lead, Mikulskis is responsible for guiding his team through the complexities of software development, ensuring that projects are completed efficiently and effectively. He has expressed a commitment to fostering a collaborative environment where innovation can thrive.24
Additional Information
Mikulskis is not currently available for full-time hire, indicating a focus on his responsibilities at Flipside Crypto. His professional presence can be found on LinkedIn, where he engages with the tech community and shares insights related to his work.26
Highlights
Spent some time recently with our DevOps pro fixing up our logging at Flipside Crypto. Logging was in a rough state: JSON formatting errors, incorrect parsing on CloudWatch, and overall noisy logs. We managed to clean it up, making errors clear, redacting secrets, and ensuring traces are effective for debugging.
Here's what I learned:
-
Think About Audience: Logging is weirdly like product design. Always consider who will be reading the logs and who will be debugging. Logs should tell a clear story, much like user stories in product design.
-
Context Matters: Different parts of the stack may need different logging approaches. Tailor your logs to fit the context they're used in.
-
Let Exceptions Do Their Job: Handle errors at the right levels. Over-engineering error handling can bury issues and make debugging a nightmare.
-
Redact Sensitive Info: Always redact secrets and sensitive information. Logs should be safe to share without exposing anything critical.
-
Be Concise: Too much noise in logs can make the important stuff hard to find. Keep logs concise but ensure they provide enough context.
It's all about clarity, context, and simplicity.
What are your best practices for logging? Would love to hear your thoughts!
Excited to share a recent milestone in my tech journey: successfully integrating TypeScript monorepos with N8N!
This new setup allows me to import custom packages from my monorepo into a custom N8N application, creating custom nodes to enhance the runtime.
One standout example:
- I built a Discord message listener and sender that dynamically refers to channels and monitors activity. This feature isn’t available in the base N8N installation.
It all started with a simple goal—creating a custom trigger node to DM new Discord joiners—and has now evolved into a robust, scalable build process.
The potential here is immense.
- Leveraging years of work in my personal pnpm monorepo, I can now bring those services into custom N8N nodes. This opens up endless possibilities for automation and efficiency.
Last week I made a custom Flipside Crypto node that lets me:
- Query top traders against certain coins using the Flipside Python SDK, wild.
Feeling incredibly optimistic about the future growth this brings to our automation capabilities.
The journey continues! 🌟
