Dev team: Using Jira, Trello, other collaborative tools.

Boss: -"Progress?"

Dev team:

A: Can you tell me your opinion about this? Please, be honest.
Me: Ok, I think you could do it in a different way, but let's talk about what you did and see how to make it better...
A: I don't think so, I think this is the best way to do it.
Me: Oh, OK.
A: Why are you always complaining about my job?
Me: Well, you just asked me, and I work on this too, so I thought...
A: I don't think you're collaborative enough with me!
Me [walking away]: Oh, OK...

We have a Miro collaborative whiteboard where product managers map functionality and user flows.

It currently has 89442 post-its & arrows.

A collaborative devRant poem by devRanters.

I hate fucking fellow students that don't do anything in collaborative projects...

A collaborative writing platform

A made a realtime collaborative fireworks webapp ;) Happy 4th of July! It uses websockets on a Node.js server.

The emphasis on "team" to the exclusion of the individual (thanks in no small part to Scrum) is destroying the software developer career. It's a pendulum. There are always team/company goals AND personal goals. However, these days, the rhetoric is ALL about the team: everybody on a team has the same title, get rid of people who don't conform to some "collaborative", "open space", "colocated" ideal, etc. OKRs are entirely about giving everybody the exact same goals. I remember sitting down with managers throughout my career to talk about where I want to be in a year. What skills I wanted to explore. There were no guarantees, but the generally accepted idea was that nurturing the employee helped retain the employee. Now, there is only the idea that every developer should have the same "T-shaped" skillset, that all team members are the same, that all teams are interchangeable, that all developers are nameless cogs. It is demoralizing. If I were to give any advice to those looking to enter the industry as a developer right now, it would be "Don't". Because you will be told that being a "hero" is a bad thing. In what other industry does management tell its producers that they don't want people to go "above and beyond", and that if they do, they won't get credit for it because the credit always belongs to everybody.

My company is (supposedly) all about collaborative work, pair programming, getting on calls and cRaCKinG tHinGs ToGEtheR. Also (and rightfully so) we’re not supposed to approve any PRs if tests weren’t created/updated.
Of course that applies to all but the old timers in the company who simply act like lone cowboys. They fall off the face of the earth for two-three days then reappear with monster PRs full of untested code.

Leave it up to the plebe then to try to make sense of the mess they’ve created, to challenge them with the fact that the PRs are lacking tests (only to be met with excuses about not having anymore time to spend on the subject).
Reprimand the plebe for not reviewing PRs thoroughly enough. Leave it up to them to fix the resulting bugs.

I’ve lost all trust in our managers, tech leads, lead devs and their guidelines and rules that only apply to others but rarely to themselves. These people that then have the audacity to criticize the tech team in it’s entirety for not being rigorous enough in its processes.
Fuck them all

In the mix for today: 5 devs testing MS Teams collaborative drawing for a GaphQL API project structure, with Halloween and coronavirus in mind

just got rejected after interview because I just cracked on with the coding exercise and didn't ask for the interviewers help (trying to create a collaborative environment) even though I smashed out the solution.... maybe dodged a bullet there

*leaning back in the story chair*

One night, a long time ago, I was playing computer games with my closest friends through the night. We would meet for a whole weekend extended through some holiday to excessively celebrate our collaborative and competitive gaming skills. In other words we would definitely kick our asses all the time. Laughing at each other for every kill we made and game we won. Crying for every kill received and game lost. A great fun that was.

Sleep level through the first 48 hours was around 0 hours. After some fresh air I thought it would be a very good idea to sit down, taking the time to eventually change all my accounts passwords including the password safe master password. Of course I also had to generate a new key file. You can't be too serious about security these days.

One additional 48 hours, including 13 hours of sleep, some good rounds Call of Duty, Counter Strike and Crashday plus an insane Star Wars Marathon in between later...

I woke up. A tiereing but fun weekend was over again. After I got the usual cereals for breakfast I set down to work on one of my theory magic decks. I opened the browser, navigated to the Web page and opened my password manager. I type in the password as usual.

Error: incorrect password.

I retry about 20 times. Each time getting more and more terrified.

WTF? Did I change my password or what?...

Fuck.

Ffuck fuck fuck FUCKK.

I've reset and now forgotten my master password. I completely lost memory of that moment. I'm screwed.

---

Disclaimer: sure it's in my brain, but it's still data right?

I remembered the situation but until today I can't remember which password I set.

Fun fact. I also could not remember the contents of episode 6 by the time we started the movie although I'd seen the movie about 10 - 15 times up to that point. Just brain afk.

!rant

"Are you okay if I put you as the capability building lead for mobility?"

OMG! A lead role for the whole mobility.
Even if it's possibly an interim, this is overwhelming. Anyway I suggested 2-3 others to be my co-leads so that we can have collaborative efforts to meet the responsibilities.

Hey, a bit of a dumb question.

When can someone call themselves a "real" programmer? I'm not one to gatekeep and say dumb shit like "iF yOu OnLy KnOw PyThOn Ur NoT a PrOgRaMmEr!", but I guess I want to know when I can call myself one. All I've done so far is make unpolished games in Unity for school that are created only to meet some requirements. I've also worked in my class' team for collaborative Unreal games, which has been painful to say the least. So, when I can stop gatekeeping myself over it? What sorts of experiences should I have? I understand that it's not a list of requirements like my projects are, but I'd like a general idea of when I can call myself a real developer.

I had a coding interview with Amazon. I had to implement a depth-first search algorithm with no prior experience while 2 devs watched me code on a collaborative IDE. To make it worse, the connection was terrible on the conference call and one of the interviewers had a very thick accent. I barely understood what they wanted me to do until I typed out:

Breadth-first search || Depth-first search?
// Sorry, phone keeps cutting off and I can barely hear you

Yeah, I didn't make it to the next round. :(

Completing my first truly collaborative project. Was with one of my friends, learnt a whole lot about git.

Just saw that the University of Hawaii has a Collaborative Software Development Lab, I think that's one of the more useful things in university

I've been training a few junior devs for about a month in the use git and adopting to a collaborative team workflow. My blood is boiling at this point. As part of the training we had the junior team build an iOS app. Their solution was for each of the to have a git repo of their own and a master repo for everyone. If they can get it to work in their individual repos, they would move that code over to the master repo. This seemed to have worked for them but it's completely wrong in trying to understand how integrating their work by the hour or so would benefit everyone involved and ultimately how that can influence the quality of the product. So I highlighted the problem with the individual repos and encouraged the use of a single remote repo. OOP is none existent all the code is slapped into a view controller. I have about given up. Let's see what this week will bring.

My team decided to do a MOB programming in one of our tickets.

New joiner: Perfect we did a mob yesterday .

Me: Great, that's good. How did it go?

New joiner: Well, we work together in the gaming room next to each other and trying to solve the issue. I think it's very productive.

Me: Awesome! Let's do it again today... When we started the MOB, all of them are using their own laptop. And I was like.. so, this is how you did the MOB yesterday?

New guy: Yes.

Me: This is not a MOB programming... MOB programming uses only 1 screen, 1 driver and everyone work together, will tell the driver what to do, we need to exchange the driver every 10 to 15 minutes, everyone can be a driver. (devs, qa, ux, product) and do a retro after.

New guy: ah.. wow! Interesting.

Note to self: *ALWAYS* pull updates from upstream before starting to add or fix stuff in a GitHub project. Or any other collaborative project for that matter.

Now, it's time to slap myself for forgetting...

👋 Collaborative drawing of devRant logo on Canvas!

Is there a collaborative tool to make a project plan, with UI mockups and other designs? Not a something like issue tracker or project timeline.

Working with a great collaborative team.

Is anyone interested in finding a collaborative online game? I have a lot here

*Sees an article with the headline 'The simple approach to building a real-time collaborative text editor'"
Before I can finish the thought that "I don't need this shit" a design idea pops up in my mind and I stop myself and say "Fuck", meaning another project for my imaginary projects list. Yay... I need help. I look at certain things and get ideas. Seriously becoming a problem.

Coming home fully energized to work on a collaborative project, turn on linux pc (quite old, but works best with git), open github, start git pull, open vs code, click on reminder to download new version -> open new chromium tab (takes longer than normal...?), open start menu
....
....
? ... pc frozen😔😥
forcing shutdown, restart ... wifi gone😓? oh come on!!😑😣

Hello to everyone!

I was wondering, how to find mate for collaborative programming projects ?

I would like to keep me trained with new challenges during the summer, and I know there’s a section here on DevRant for collaborative project but I find this a bit confusing.

Top Benefits of Using Data Loss Prevention in Microsoft 365

Data Loss Prevention (DLP) in Microsoft 365 offers numerous benefits to organizations aiming to protect sensitive information and ensure compliance. One of the top advantages is enhanced data protection, where DLP policies help identify, monitor, and restrict the sharing of sensitive information like credit card details or personal identification numbers across Microsoft 365 apps (Outlook, SharePoint, OneDrive, and Teams). This proactive security measure prevents unauthorized access or accidental sharing of confidential data.

Another key benefit is regulatory compliance. DLP helps organizations comply with data protection regulations such as GDPR, HIPAA, and CCPA by enforcing policies that limit data exposure and unauthorized sharing, reducing the risk of costly fines.

Microsoft 365 DLP also offers visibility and control. IT administrators can monitor user actions and identify potential risks in real time, making it easier to enforce security measures. Additionally, user education is integrated through policy tips, which educate users about data protection during daily tasks.

Finally, DLP offers seamless integration across all Microsoft 365 platforms, making it easy to manage and enforce consistent security policies across emails, documents, and collaborative tools, ensuring comprehensive protection for the entire organization.

Duet AI: Revolutionizing Collaborative Music Creation
In the realm of music creation, collaboration has always been a cornerstone of innovation and artistic growth. With the advent of artificial intelligence (AI), a new era of collaborative music composition has emerged. Duet AI, a groundbreaking AI-powered system, is transforming the way musicians collaborate, enabling seamless interaction between human artists and AI algorithms. In this article, we will explore the concept of Duet AI and its impact on collaborative music creation.

H1: The Power of Duet AI in Collaborative Music Creation
Duet AI harnesses the capabilities of AI to facilitate real-time collaboration between musicians, composers, and AI algorithms. This innovative system acts as a virtual partner, responding to human input, providing creative suggestions, and adapting to the evolving musical dynamics. By integrating human creativity with the computational power of AI, Duet AI opens up new possibilities for artistic expression and the co-creation of music.

H2: Seamless Integration of Human and AI Musical Expertise
Duet AI seamlessly integrates the musical expertise of human artists with the analytical capabilities of AI algorithms. The system analyzes vast musical databases, identifying patterns, harmonies, and rhythms from various genres and eras. It uses this knowledge to generate musical ideas, chord progressions, and even complete compositions that complement and interact with the human artist's input. The result is a harmonious collaboration that pushes the boundaries of musical creativity.

H2: Enhancing Inspiration and Idea Generation
Duet AI serves as a valuable tool for musicians seeking inspiration and idea generation. It can offer suggestions, variations, and alternatives to human artists, fueling their creativity and sparking new musical directions. Whether it's exploring different melodies, experimenting with harmonies, or discovering innovative arrangements, Duet AI provides a constant stream of musical possibilities that can be integrated into the collaborative process.

H2: Real-time Adaptation and Musical Sensitivity
One of the key strengths of Duet AI lies in its ability to adapt and respond in real time to the human artist's input. The system listens and analyzes the music being created, dynamically adjusting its suggestions and responses to maintain coherence and musical sensitivity. This adaptability ensures that the AI component of the collaboration remains in sync with the human artist, enhancing the fluidity and natural flow of the music being created.

H2: Expanding Musical Horizons and Genre Blending
Duet AI enables artists to explore new musical horizons and experiment with genre blending. By incorporating AI-generated musical ideas, artists can transcend traditional boundaries and fuse elements from different styles and genres. The system's vast knowledge base allows it to generate musical segments that authentically capture the essence of diverse musical traditions, enabling artists to create unique and innovative compositions that push the boundaries of genre conventions.

H2: Preserving the Artist's Creative Vision
While AI plays an active role in the collaborative process, it is essential to acknowledge the artist's creative vision and maintain artistic ownership. Duet AI functions as a supportive collaborator, offering suggestions and ideas, but the final artistic decisions remain in the hands of the human artist. The system respects the artist's autonomy, ensuring that the collaboration is a true partnership that amplifies the artist's creativity rather than overshadowing it.

H1: Conclusion
Duet AI represents a significant leap forward in collaborative music creation. By combining the artistic expertise of human musicians with the computational power of AI, this innovative system opens up new frontiers of creativity and musical expression. Duet AI enhances inspiration, expands musical horizons, and enables seamless interaction between human and AI collaborators. As this technology continues to evolve, we can expect even more transformative possibilities in collaborative music creation, leading to a new era of artistic innovation.

Building Fortresses, not Firewalls: Ethical Hacking Meets Software Development

In the digital age, security is no longer an afterthought; it's the bedrock upon which our online world rests. Yet, traditional security measures often resemble fortresses – imposing, but vulnerable to unseen cracks and tunnels. To truly safeguard our systems, we need to think like the enemy, like the nimble figures scaling those walls: ethical hackers.

Enter the exciting realm of DevSecOps, where ethical hacking practices are woven into the very fabric of the software development lifecycle (SDLC). This proactive approach is akin to building castles with security in mind, each brick meticulously laid to withstand even the most cunning siege.

Why Ethical Hacking in SDLC?

Imagine developing a critical piece of software, only to discover a gaping security hole after launch. The damage could be catastrophic, exposing sensitive data and eroding trust. Ethical hacking flips this script. By integrating penetration testing, vulnerability assessments, and threat modeling throughout the SDLC, we proactively hunt for weaknesses before they can be exploited.

Think of it as a friendly sparring match, where the ethical hacker throws their best punches to expose vulnerabilities, allowing the development team to fortify the software's defenses. This constant testing and refining leads to robust, secure systems that can withstand real-world attacks.

Benefits of DevSecOps:
1. Reduced Costs and Risks: Early detection and patching of vulnerabilities are far cheaper than dealing with a full-blown data breach.
2. Improved Software Quality: Security becomes an inherent part of the development process, leading to more reliable and trustworthy software.
3. Enhanced Brand Reputation: Demonstrating a proactive approach to security builds trust with customers and stakeholders.

Putting it into Practice:
Integrating ethical hacking into the SDLC requires a cultural shift. Developers, security professionals, and testers need to work together seamlessly, sharing knowledge and fostering a collaborative environment. Here are some key practices:
1. Threat Modeling: Identify potential threats and attack vectors early in the development process.
2. Static and Dynamic Code Analysis: Use automated tools to detect vulnerabilities in code.
3. Penetration Testing: Simulate real-world attacks to uncover hidden weaknesses.
4. Security Awareness Training: Educate developers and other stakeholders about security best practices.

Tools of the Trade:
A plethora of tools empowers ethical hackers and security professionals in their quest for a more secure digital world. Some popular options include:

1. Kali Linux: A distribution packed with security tools for penetration testing.
2. Burp Suite: A web application security testing platform.
3. Metasploit: A framework for developing and executing exploit code.
4. Wireshark: A network traffic analyzer for identifying suspicious activity.

The Future of Security:
As technology evolves, so too must our security practices. DevSecOps, with its embrace of ethical hacking, is at the forefront of this evolution. By building security into the very fabric of software development, we can create a safer, more resilient digital world for everyone.

Remember, in the ongoing battle against cyber threats, ethical hackers are not the enemy; they are our allies, the architects of digital fortresses that stand strong against the shadows. So, let's embrace DevSecOps, sharpen our ethical hacking skills, and build a future where security is not just an afterthought, but a fundamental principle.

I encourage you to explore the world of DevSecOps and ethical hacking. Whether you're a seasoned developer or just starting your journey, there's always more to learn and contribute. Together, we can build a more secure digital future, one line of code and one vulnerability patch at a time.

Do you have any questions about DevSecOps or ethical hacking? Share your thoughts and experiences in the comments below!