<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Vygandas Pliasas</title>
    <description>The latest articles on DEV Community by Vygandas Pliasas (@vygandas).</description>
    <link>https://dev.to/vygandas</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F957988%2F7bdb610a-5e0a-4212-8802-94f45288bb1b.jpeg</url>
      <title>DEV Community: Vygandas Pliasas</title>
      <link>https://dev.to/vygandas</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/vygandas"/>
    <language>en</language>
    <item>
      <title>Navigating the Challenges of Hybrid Work: Strategies for a Successful and Disruption-Free Experience</title>
      <dc:creator>Vygandas Pliasas</dc:creator>
      <pubDate>Tue, 07 Feb 2023 10:58:00 +0000</pubDate>
      <link>https://dev.to/vygandas/navigating-the-challenges-of-hybrid-work-strategies-for-a-successful-and-disruption-free-experience-3eek</link>
      <guid>https://dev.to/vygandas/navigating-the-challenges-of-hybrid-work-strategies-for-a-successful-and-disruption-free-experience-3eek</guid>
      <description>&lt;p&gt;Remote work and on-site work have become more prevalent in the modern era of work. With the advent of technology, employees have the opportunity to work from anywhere with an internet connection, making it possible for companies to have a more flexible and distributed workforce. While remote work offers many benefits, it is also different from on-site work in several key ways.&lt;/p&gt;

&lt;p&gt;One of the biggest differences between remote work and on-site work is the lack of physical interaction. In an on-site work environment, employees have the opportunity to interact with each other and their manager in person, but this is not possible in remote work. This can make it more difficult to build relationships, establish trust, and communicate effectively.&lt;/p&gt;

&lt;p&gt;Another difference is the way in which employees are managed. In an on-site work environment, managers have the opportunity to observe their employees and monitor their progress. In a remote work environment, managers must rely on other methods to assess the productivity and progress of their employees. This can lead to confusion and miscommunication if not managed effectively.&lt;/p&gt;

&lt;p&gt;The concept of a hybrid work environment, where some employees work on-site and others work remotely, can bring a lot of confusion and disturbance. For example, an on-site manager may drag someone into a meeting without considering other events scheduled on their calendar, which can be disruptive for remote employees who may have already planned their work schedule around their calendar. This lack of coordination and consideration can lead to frustration and decreased productivity for both on-site and remote employees.&lt;/p&gt;

&lt;p&gt;Remote work and on-site work offer unique benefits and challenges. The hybrid mix of the two can lead to confusion and disturbance, but with proper communication and collaboration, it can be a successful and effective solution for companies. Companies need to understand the differences between remote work and on-site work and implement strategies to ensure a seamless transition to a hybrid work environment.&lt;/p&gt;

&lt;p&gt;As someone who has been working remotely long before it became popular, I have learned a few key strategies that can help make hybrid work a better and less disruptive experience for everyone.&lt;br&gt;
Communication: Effective communication is key to making hybrid work successful. Companies should invest in tools that make it easy for employees to communicate with each other, regardless of where they are located. This includes video conferencing, instant messaging, and project management tools.&lt;/p&gt;

&lt;p&gt;Flexibility: Hybrid work requires a high degree of flexibility from both on-site and remote employees. Companies should provide employees with flexible schedules and the tools they need to be productive, whether they are working from home or in the office.&lt;br&gt;
Collaboration: Collaboration is an important part of any work environment, and it is especially important in hybrid work. Companies should encourage collaboration by providing opportunities for employees to work together on projects and initiatives, and by making it easy for employees to communicate and share information.&lt;/p&gt;

&lt;p&gt;Clear expectations: Companies should establish clear expectations for both on-site and remote employees, including what is expected of them in terms of availability, work hours, and communication. This will help to reduce confusion and ensure that everyone is on the same page.&lt;/p&gt;

&lt;p&gt;Respect for each other's schedules: On-site managers and remote employees should respect each other's schedules and plan accordingly. For example, on-site managers should not drag someone into a meeting without considering other events on their calendar, as this can be disruptive for remote employees who may have already planned their work schedule around their calendar.&lt;/p&gt;

&lt;p&gt;In conclusion, making hybrid work successful and less disruptive requires a combination of effective communication, flexibility, collaboration, clear expectations, and respect for each other's schedules. By implementing these strategies, companies can create a hybrid work environment that is productive, efficient, and enjoyable for all employees.&lt;/p&gt;

</description>
      <category>announcement</category>
      <category>web3</category>
      <category>devto</category>
    </item>
    <item>
      <title>Breaking into the CTO Role: Opportunities Beyond Founding and Board Appointments</title>
      <dc:creator>Vygandas Pliasas</dc:creator>
      <pubDate>Sun, 05 Feb 2023 18:28:20 +0000</pubDate>
      <link>https://dev.to/vygandas/breaking-into-the-cto-role-opportunities-beyond-founding-and-board-appointments-9oi</link>
      <guid>https://dev.to/vygandas/breaking-into-the-cto-role-opportunities-beyond-founding-and-board-appointments-9oi</guid>
      <description>&lt;p&gt;As the technology industry continues to grow and evolve, the role of the Chief Technology Officer (CTO) has become increasingly important. However, the perception that the only way to attain this role is through being a founding member or being appointed by a board can be limiting for those aspiring to become a CTO. The truth is, there are several paths to the CTO role, and one of the most promising is through consulting. Of course, I don't want to say that these are the only ways, but more like it's the most common I have met myself.&lt;/p&gt;

&lt;p&gt;Consulting CTOs and fractional CTOs offer an alternative path to the traditional route of becoming a CTO. These professionals work with leadership teams to optimize processes, identify areas for improvement, and provide a fresh perspective on problems. As a result, they are able to bring a wealth of experience and knowledge to the table and play a critical role in shaping the technology strategy of an organization.&lt;/p&gt;

&lt;p&gt;One of the key benefits of becoming a consulting or fractional CTO is the opportunity to gain a broad range of experience across a variety of industries and technology domains. This allows individuals to build a diverse skill set and broaden their network, positioning them well for future CTO opportunities. Additionally, consulting CTOs are often able to work with organizations at various stages of growth, from start-ups to mature enterprises. This provides a unique opportunity to work with different types of technology, at different scales, and in different contexts.&lt;/p&gt;

&lt;p&gt;Another advantage of this role is that it allows individuals to bring their expertise to multiple organizations, rather than being limited to one company. This provides the opportunity to work on a variety of projects and gain a deep understanding of different industries and technology domains. This, in turn, makes consulting and fractional CTOs highly sought after by organizations looking to stay ahead of the curve.&lt;/p&gt;

&lt;p&gt;It's important to note that the role of the consulting or fractional CTO is not limited to technology strategy. These professionals also play a critical role in leading and mentoring technology teams, fostering a culture of innovation, and driving change within organizations.&lt;/p&gt;

&lt;p&gt;In conclusion, the CTO role is no longer limited to founding members or board appointments. The consulting and fractional CTO roles offer a promising alternative path, providing opportunities to gain a broad range of experience, build a diverse skill set, and play a critical role in shaping the technology strategy of organizations. For those aspiring to become a CTO, these roles are worth exploring as they provide a unique opportunity to build a foundation for future success.&lt;/p&gt;

&lt;p&gt;In addition to the benefits mentioned above, being a consulting or fractional CTO also provides individuals with greater freedom and flexibility in their work. As a consultant, you are able to use your knowledge and expertise across a variety of industries and technology domains, making your work more interesting and dynamic.&lt;/p&gt;

&lt;p&gt;However, it's important to note that this role also brings with it more challenging and demanding requirements. As a consultant, you are expected to deliver results and to be an expert in your field. You must be able to quickly understand complex problems and develop solutions that meet the needs of the organization. Additionally, you must be able to communicate effectively with leadership teams, stakeholders, and technology teams, and be able to lead change within the organization.&lt;/p&gt;

</description>
      <category>announcement</category>
      <category>devto</category>
      <category>offers</category>
    </item>
    <item>
      <title>First time open-source experiences</title>
      <dc:creator>Vygandas Pliasas</dc:creator>
      <pubDate>Thu, 03 Nov 2022 07:48:37 +0000</pubDate>
      <link>https://dev.to/vygandas/first-time-open-source-experiences-3a6n</link>
      <guid>https://dev.to/vygandas/first-time-open-source-experiences-3a6n</guid>
      <description>&lt;p&gt;Some might ask why we contribute to open-source projects, especially when we are not getting paid for doing so. It is something for which we willingly sacrifice our free time and spend hours of work reviewing, investigating, thinking, fixing, commenting, reviewing again, and finally merging. I still need to become an expert in this field, and I've just started building my open-source project. So far, I have learned a lot of things, and the more I get involved, the more I like it and the more I see the benefits list growing.&lt;/p&gt;

&lt;p&gt;So far, with my open-source project, there's not much of a business element involved, well, at least, no direct business. The fun part is that the operations are more or less the same. &lt;/p&gt;

&lt;p&gt;A successful project will unlock three future opportunities for the whole team working on it. My belief in this new way gets more robust the more time I spend on this.&lt;/p&gt;

&lt;h3&gt;
  
  
  🚀 Exposure and career opportunities
&lt;/h3&gt;

&lt;p&gt;I've been hiring a lot and working with recruiters. Skilled recruiters who want to avoid spam on LinkedIn are looking for senior engineers on Github. That makes sense because good software developers tend to contribute here and there when they have time. Whether it's a sports interest or a desire to help or learn something - it all works. Now, the tricky part is that if you do only private projects, top secret super business code, nobody will ever see that. A successful open-source project is proof of leadership, culture, team play, and development skills.&lt;/p&gt;

&lt;h3&gt;
  
  
  🚀 A strong and synchronised team
&lt;/h3&gt;

&lt;p&gt;If the squad manages to build one project, maintains it, and cherishes a positive vibe and communication, this team can develop more products and solutions in the future. And it means it can be something other than open-source! Think about it - how many people do you know to whom you could share your startup idea and start working on it? Think about the tech stack, ways of contributing, PR reviewing, presenting, sharing ideas, brainstorming, and all other operations needed. Remember you're going to make some new friends too!&lt;/p&gt;

&lt;h3&gt;
  
  
  🚀 Big user base, the platform to launch
&lt;/h3&gt;

&lt;p&gt;So, we discussed exposure and team, and now it's time to talk about clientele! There must be some traffic and usage if there's a product and contributors. Imagine if you can pull it off and there are thousands or even more users; that could be a launchpad for something else in the future. Whether it's consulting, custom solutions, paid features, or total pivoting from the free idea - if you have users you can tell about your next thing, you're in the good zone.&lt;/p&gt;

&lt;p&gt;Even though I started this project not so long ago, I have received some interesting LinkedIn messages. I didn't expect that, but it's getting interesting so far.&lt;/p&gt;

&lt;p&gt;And to add, in the end, I wanted to share one more thought that spins in my head. Venture Capitalists always ask how you will build a team, and hiring sound engineers are expensive. And I'll leave this to lay in your minds a bit.&lt;/p&gt;

&lt;p&gt;Thanks for reading till the end. I hope you like it. The project I was referring to is called Isomera &lt;a href="https://github.com/cortip/isomera"&gt;https://github.com/cortip/isomera&lt;/a&gt;.&lt;/p&gt;

</description>
      <category>opensource</category>
      <category>programming</category>
      <category>career</category>
      <category>contributorswanted</category>
    </item>
    <item>
      <title>My first decent open-source project! 🎉 Isomera, the headless CMS for business representative websites</title>
      <dc:creator>Vygandas Pliasas</dc:creator>
      <pubDate>Sat, 29 Oct 2022 06:51:44 +0000</pubDate>
      <link>https://dev.to/vygandas/my-first-decent-open-source-project-isomera-the-headless-cms-for-business-representative-websites-1c80</link>
      <guid>https://dev.to/vygandas/my-first-decent-open-source-project-isomera-the-headless-cms-for-business-representative-websites-1c80</guid>
      <description>&lt;p&gt;Building a headless CMS. 😎 It's called Isomera.&lt;/p&gt;

&lt;p&gt;Reason - got tired of setting up Strapi again and again and again.&lt;/p&gt;

&lt;p&gt;Usually, CMS needs are the same. News, contacts form, some text variables... Thinking of adding a visual builder for data structures too.&lt;/p&gt;

&lt;p&gt;Other cloud-hosted headless CMS getting damn expensive when looking at features like roles.&lt;/p&gt;

&lt;p&gt;The ideal scenario is that I configure my data structures, add content, then build a website on Next.js, deploy on Vercel, add the client to the CMS with limited permissions, and that's it. The pretty standard one, I suppose.&lt;/p&gt;

&lt;p&gt;And also, always thought it would be cool to have some decent opensource project anyway.&lt;/p&gt;

&lt;p&gt;So I started, got one active contributor already, some interested potential contributors, and everything is set up, even the production environment.&lt;/p&gt;

&lt;p&gt;This will be community-built and deployed on production. And also, I'm thinking of keeping it accessible for all. There's a sponsorship feature on GitHub for those who'd like to help, too 😊&lt;/p&gt;

&lt;p&gt;How cool is that? You use a SaaS product for your day-to-day operations, need a feature, make a PR, and it's there! That's the vision. ✨&lt;/p&gt;

&lt;p&gt;Let me know if you want to be a part of this project. Everyone can contribute. Yes, I'm talking about engineers, designers, content creators, marketers, managers, you name it!&lt;/p&gt;

&lt;p&gt;&lt;a href="https://github.com/cortip/isomera"&gt;https://github.com/cortip/isomera&lt;/a&gt;&lt;/p&gt;

</description>
      <category>javascript</category>
      <category>opensource</category>
      <category>cms</category>
      <category>github</category>
    </item>
  </channel>
</rss>
