Because this is one of those rare moments in the industry when the often-repeated phrase “those who stay out will fall behind” stops being a cliché and becomes reality. Many engineers already feel the pressure of keeping up, and the pace shows no signs of slowing down. New models, new agent frameworks, new evaluation methods, and new architectural implications appear almost weekly. Those who invest in understanding these changes will accelerate. Those who don’t may find the gap widening faster than expected.

Craft Conference 2026 is designed around this inflection point.

AI-Native Software Engineering: When AI Is Not a Tool, but a Teammate

At the heart of the conference is its largest thematic pillar: AI-native software engineering.

AI-native development means designing software, workflows, and teams with the assumption that AI is part of the default environment. It’s no longer about occasionally asking an AI assistant for help. Instead, it means building development processes where AI actively participates in coding, reviewing, testing, and even architectural exploration.

Engineers from companies such as Anthropic, NVIDIA, Meta, Amazon Web Services, and IBM will share how their teams are adapting workflows, code review practices, and system design principles to this new reality.

From Anthropic’s Claude Code team, Kashyap Murali presents two highly anticipated talks. One focuses on making AI coding agents trustworthy – a crucial challenge as teams increasingly rely on AI-generated code. The other explores one of the fastest-emerging disciplines in AI development: evaluating and improving the reliability of AI-driven engineering workflows.

At NVIDIA, Aaron Erickson addresses one of the industry’s most complex technical challenges: how to combine deterministic software systems with probabilistic AI models in production environments.

From Meta, Ian Thomas explores what it truly means for entire engineering teams to become AI-native – not just more productive, but fundamentally different in how they collaborate with intelligent systems.

Architecture, Platforms, and the Human Factor

As AI accelerates coding, architecture becomes even more important.

A well-structured system enables AI tools to be effective. Poor architecture, on the other hand, can make AI-generated outputs confusing, inconsistent, or even unsafe.

Experts such as Gregor Hohpe, Neal Ford, and Mark Richards will explore how software architecture needs to evolve for AI-driven systems and rapidly accelerating development cycles.

Michael Feathers will address another critical challenge: legacy systems. His talk explores why healthy codebases are the first step toward becoming truly AI-ready. Without maintainable foundations, AI can amplify complexity instead of reducing it.

But Craft also focuses on the human side of these transformations.

Rapid technological change inevitably creates stress, uncertainty, and pressure for engineers and organizations. Talks on mindset, cognitive bias, and team psychology examine how developers and leaders can navigate these challenges.

Michelle Brush from Google explains the Jevons paradox in the context of AI: when automation makes certain tasks easier, the remaining problems often become significantly harder.

Meanwhile, Sander Hoogendoorn describes what he calls the exponential era – a time when technological change accelerates so rapidly that standing still effectively means falling behind.

Guiding Through Change: Voices That Shaped the Industry

Craft 2026 also brings together some of the most influential thinkers in modern software engineering.

• Kent Beck, creator of Extreme Programming and Test-Driven Development, and author of Tidy First? returns to Craft to share his perspective on how foundational engineering principles evolve in an AI-powered world.
• Gergely Orosz, one of the most widely read technology writers and newsletter authors today, will provide both historical context and practical insight. His talk explores which engineering practices remain timeless and which must evolve as AI reshapes the development landscape.
• Veronica Clark, a mindset coach working with engineers and technology leaders, offers a complementary perspective. Her sessions focus on managing the mental and emotional challenges that accompany rapid technological change – a topic increasingly relevant as many developers experience uncertainty about the future of their profession.

Together, these speakers represent architects of past transformations who are now engaging with the next major evolution of the field.

The New Era Has Already Begun

More than 2,000 engineers from over 50 countries will gather in Budapest for Craft Conference 2026.

Developers and leaders from companies such as Netflix, Adobe, Shopify, Nubank, BBC, Google, Anthropic, NVIDIA, and Meta will come together not only to present ideas but to think collectively about the future of their profession.

The software industry stands at a crossroads similar to the early days of the internet.

The key question is no longer whether AI will transform software engineering – it already has.

The real question is how we respond.

Will we adapt intentionally?
Or react too late?

Craft Conference 2026 is where that conversation happens. Where engineers explore the new realities of their profession and discover practical ways to move forward.

Not about fear. Not about hype. About responsibility and readiness in the exponential era.

A Craft 2026: Engineering in the Exponential AI Era bejegyzés először CraftHub-én jelent meg.

This kind of setup characterizes most hackathons, which are all about ideation, challenge, and shared experiences. The Minds & Machines hackathon, taking place on February 27–28, 2026, is organized by CraftHub in collaboration with GDE MIT, with the support of Microsoft. During the event, participants will be tasked with creating AI-based solutions to challenges in healthcare and education.

But what exactly is a hackathon? And why is it worth applying?

Give yourself a chance for professional growth by solving real-world problems

Hackathon challenges are usually designed by professionals who, through their experience and expertise, understand what constitutes realistic and relevant problems. Participants must develop solutions to these challenges, ranging from coding and artificial intelligence to UX/UI design.

These tasks are especially important because real-world scenarios require well-thought-out solutions from every perspective. As a result, professional development becomes inevitable – and therefore invaluable – since participants are required to create outside their comfort zones. This can be intimidating, but it is absolutely worth it, as the experience gained can be leveraged in the future.

Meet our mentors and build your network

Hackathons evaluate the realization of participants’ own ideas, but no one has to rely solely on themselves. On site, numerous professionals offer mentorship, providing guidance on questions, obstacles, and suggestions that arise along the way. Mentors are happy to help ensure that solutions are as strong as possible by the end of the 30 hours.

The Minds & Machines hackathon stands out because Microsoft is present as an official partner of the event. Participants will have the opportunity to meet Microsoft employees, as well as fellow participants and industry experts, making the event highly valuable from a networking perspective.

“To be able to meet and learn with some of the most prominent people in the software area is something like nothing else. And to be able to solve real-life challenges in 24 hours is a unique sensation.”
— Joao Anastácio da Rocha Almeida, Student Developer

Work in a team to create something truly great

Although it is possible to apply individually, a team’s combined ideas can lead to even greater progress. Team members learn together, solve problems, generate ideas, and strive toward a shared goal: creating the best possible solution. This experience is invaluable, as the ability to work effectively in a team is essential later in one’s career.

Teamwork is crucial because members continuously motivate each other to use their full potential, opening new doors and opportunities. Creating value together with others is an incredible experience – especially through such an intense challenge.

Win prizes and be the best

While gaining knowledge is already a major reward at a hackathon, the Minds & Machines hackathon also offers financial prizes for the most outstanding teams, along with valuable tech accessories:

• Grand Prize: €6,000
• Challenge Winner: €3,000 for the best teams in each category
• Audience Award: €1,000

The top 3 teams from each challenge advance to the final, where they can present their solutions in more detail. Based on these presentations, the winner of the grand prize will be selected.

If the four points above sparked your interest, you’re in the right place!
Register for the Minds & Machines hackathon and give yourself the chance to grow, gain unforgettable experiences, and win!

More information: https://bit.ly/gdemithackathon
Registration: https://bit.ly/gdemit_register
Join the conversation on Slack: https://bit.ly/gdemit_slack

A GDE MIT Minds & Machines Hackathon: 30 Hours to Innovate, Learn, and Win bejegyzés először CraftHub-én jelent meg.

Location: Budapest, Hungary
Next event: February 27-28, 2026

The GDE MIT Hackathon is an intensive, ~30-hour offline innovation marathon that empowers participants to harness the power of AI to create solutions with real impact in healthcare and education. Organized by CraftHub and hosted at Gábor Dénes University in Budapest, the event brings together around 100 participants, from experienced developers to ambitious newcomers. Working in teams, they tackle real-world challenges designed by GDE MIT experts. Over two days, teams brainstorm, develop, and refine their ideas before presenting their solutions to a professional jury, with the most outstanding projects receiving valuable prizes and recognition.

Visit website

A GDE Minds & Machines Hackathon bejegyzés először CraftHub-én jelent meg.

In today’s fast-moving digital world, teams often rush to build – chasing deliverables without fully understanding the problem, the users, or what success actually looks like.

In her insightful talk at Craft Conference 2025, Chisara (Chisa) Nwabara challenged this pattern by redefining testing not as a QA task, but as a strategic mindset that can shape product thinking, improve collaboration, and prevent costly missteps.

This wasn’t about unit tests or coverage metrics. It was about thinking before doing – slowing down to go faster, using testing principles to create clarity, alignment, and real momentum in product and service development.

Make testing a strategic advantage

At its core, Chisara’s message was about understanding testing as a strategic tool: something to apply before code is written, before teams are spun up, and before resources are committed.

A testing mindset helps answer critical questions:

• Are we solving the right problem?

• What does success look like?

• Who needs to be involved and when?

By shifting testing earlier, teams can avoid many of the pitfalls that derail projects later on.

Start with readiness: test before you build

Before building anything, ask: Are we actually ready?

“If you don’t have what you need, don’t start.”

Readiness isn’t just having a backlog. It’s having the right inputs. This is where the Definition of Ready comes in. Develop a checklist to ensure that:

• The problem is clearly defined.

• Assumptions and expected behaviors are known.

• Dependencies are understood.

• Stakeholders are aligned.

Without this, even the best-intentioned build can lead to rework, confusion, or outright failure.

Frame before building: define outcomes first

A key part of readiness is clarity on expected behaviors and outcomes. Chisara introduced the Given-When-Then model to structure that clarity:

• Given: the context or state before an action

• When: the action or trigger

• Then: the expected result or outcome

If you can’t describe this clearly for a story or feature, you’re not ready to build. And if those outcomes don’t align with broader organizational goals, you may be building something that doesn’t matter.

Avoid common pitfalls with a testing mindset

Chisara highlighted several traps that derail projects – and how a testing mindset can prevent them:

• Jumping to solutions too quickly
  Starting with solutions feels fast but often sends teams in the wrong direction. Test and validate the problem first.

• Disconnected doers
  When team members don’t see how their work connects to the mission, it’s a sign of weak framing. Good tests tie the “why” to every “what.”

• Confusing a brain dump with a plan
  Listing tasks isn’t planning. Testing helps create structure, priorities, and shared understanding.

• Assuming shared understanding
  If everyone doesn’t get it, you’re not ready. Alignment is part of testing.

  • Who needs to be in the room?

  • What do they need?

  • How do you know they got it?

• Doing too much, too fast
  Tackling everything at once prevents learning. Ruthless prioritization is essential. One clear test at a time, not ten blurry ones.

• Building in the wrong order
  If there’s no agreement on expectations, you’re on shaky ground. Define first. Test the understanding. Then proceed.

From chaos to clarity: a repeatable mindset

Chisara ended with a clear, practical sequence teams can adopt:

1. Start with an opportunity and a hypothesis
   Don’t just build. Define what you’re trying to learn or prove.

2. Ensure clarity and alignment
   Everyone involved should understand what you’re doing, why it matters, and how success is defined.

3. Prioritize and iterate
   Focus on the most valuable thing first. Test it. Then move on.

4. Follow the correct order of operations
   Get agreements, definitions, and validations in place before you build.

Conclusion

Chisara’s talk was a powerful reminder: testing isn’t just about catching bugs – it’s about preventing waste. It’s about framing problems clearly, making deliberate decisions, and empowering teams to build with purpose.

When testing becomes a mindset applied throughout the entire lifecycle – not just the code – teams create stronger products, better collaborations, and far fewer surprises.

Slow down to test, and speed up delivery.

A Why delivery projects fail: transforming testing from a task to a strategic mindset bejegyzés először CraftHub-én jelent meg.

In the modern software world, Artificial Intelligence is no longer just a futuristic dream – it’s embedded in the very fabric of our technology, from autonomous vehicles to recommendation engines, cybersecurity tools, and even code generation platforms. But what happens when the machines we trust become vulnerable to manipulation? And how do we, as developers, navigate this evolving digital landscape?

Yossi Sassi’s engaging talk at Craft Conference 2025 – “AI: The Basics”—offered a sobering yet inspiring look into the world of AI, adversarial attacks, and the future of code trust. With decades of experience in InfoSec and cyber-defense, Sassi provided not only a technical overview but also a human-centered lens on the rise of machine intelligence.

AI and the Human Touch

Sassi began with a powerful reminder: “Everything around us today, from culture to consumer products, is a product of intelligence.” But unlike traditional software, AI systems don’t just follow static rules – they learn, adapt, and generalize, which opens the door for both innovation and manipulation.

AI is shaped by research, regulation, industry pressure, geopolitics, and uncertainty. It evolves at the intersection of culture, ethics, and security. And in a world increasingly reliant on deep learning, it’s not enough for machines to be smart – they must also be safe.

Patch the Road, Trick the Car

One of the most eye-opening segments in Sassi’s talk focused on adversarial physical attacks—where small changes in the environment trick AI vision systems into misinterpreting the world.

In a powerful example, two workers lay down a simple physical road patch that looks innocuous to humans, but can confuse lane-keeping assistance systems, causing them to veer off course. These aren’t theoretical attacks – they are real-world exploits using basic tools like adhesive stickers or fabric patches to manipulate neural network perception.

“What the human sees as a pothole patch, the machine sees as a lane boundary.”

This leads to critical questions: How resilient are our models? How easily can our cars, drones, and robots be misled in the physical world?

Attack of the Drones (and the Datasets)

Sassi also highlighted a chilling scenario – projected traffic signs injected into the scene using drones, confusing advanced driver-assistance systems (ADAS) into thinking a stop sign or a speed change is real.

These semantic attacks exploit the gap between human logic and AI perception. They don’t just alter pixels; they alter meaning. Whether it’s by changing lighting, projecting fake signs, or manipulating angles, the adversary plays a psychological game – not with humans, but with the AI itself.

From Assistants to Authors: The Future of Coding

In another futuristic twist, Sassi explored how AI is changing not just how we see the world, but how we write it – especially in code.

From simple automation scripts to full-stack AI-generated applications, the trajectory looks something like this:

1. Humans write code
2. Humans + machines write code
3. Machines write code; humans review
4. Machines write everything; humans intervene only in critical areas
   

But there’s a caveat: as code becomes more machine-authored, it becomes harder for humans to understand. What happens when we can’t trace logic? When a tragedy occurs due to a “pure machine” error that no human can debug? As Sassi provocatively framed it:

“Code trust becomes the ultimate challenge of our time.”

Red vs. Blue: Cyber Tango in the Age of AI

The cybersecurity implications are vast. As offensive cyber operations integrate AI, machine learning, and automation, the balance between Red Teams (attackers) and Blue Teams (defenders) becomes more dynamic. We no longer fight just with exploits – we fight with training data, model drift, prompt injections, and inference manipulation.

In this new battleground, the tools are evolving faster than the doctrines. Developers must adopt time-focused, architecturally aware, and ethically grounded approaches to building safe AI systems.

What It Means for Developers

For developers, AI security means more than patching bugs. It means:

• Understanding how models interpret the world
• Anticipating edge cases and attack vectors
• Writing explainable code
• Building fail-safes and audit trails
• Staying informed about the philosophical and political dimensions of AI

In short: We may no longer write all the code, but we are still responsible for what the code does.

Final Thoughts: Ask Better Questions

Yossi Sassi’s final message resonated deeply:

“Computers are getting better and better at answers, but humans still ask better questions.”

The future of AI will be shaped not by the power of machines alone, but by the curiosity, responsibility, and clarity of those who design, question, and safeguard them.

As we step into this AI-augmented future, we must remember: the real superpower is not intelligence – it’s understanding.

A When Code Sees Red: AI, Adversaries, and the Evolving Role of Developers bejegyzés először CraftHub-én jelent meg.

At this year’s Craft Conference in Budapest, renowned software engineer and Agile pioneer Kent Beck delivered a keynote that stood out not through technical detail, but through metaphor. His talk, “The Forest and the Desert Are Parallel Universes,” reimagined leadership, productivity, and organizational culture through two starkly contrasting environments: the forest and the desert.

This wasn’t just a poetic analogy. Beck’s metaphor reveals how companies build processes, how teams are led, and why organizations often fail — not because of incompetence, but because they try to apply the rules of one universe in the terrain of another.

Context Over Competence

Beck traces the metaphor back to the early 2000s, during the height of Extreme Programming. He recalls working in a high-performing team: skilled, aligned, and productive. And yet, the entire team was let go.

It wasn’t underperformance. On the contrary, they were delivering quality software. But their success didn’t align with what the company valued at the time. From this came Beck’s provocative question:

“If we know how to do everything, will anyone still want us?”

The realization that followed forms the basis of his metaphor:

“The problem is rarely the problem. The problem is the context.”

Two Worlds: The Forest and the Desert

Beck presents the forest and the desert as two fundamentally different universes of work.

🌵 The Desert

The desert is structured, urgent, and survival-driven. Inspired by Hobbes’s view of people as selfish and in need of control, it emphasizes predictability, pressure, and authority.

• Leadership relies on deadlines, metrics, and consequences.

• Planning is rigid; dependencies shift blame.

• Metrics are manipulated to avoid accountability.

In this world, leadership feels easier — but only because it runs on fear and scarcity. Success may even be punished, as exceeding expectations can disrupt hierarchies.

🌲 The Forest

The forest, by contrast, is alive, unpredictable, and collaborative. Grounded in Rousseau’s belief that people are inherently good, it values trust, purpose, and shared accountability.

• Leadership fosters autonomy within a shared vision.

• Planning is adaptive: half structured, half emergent.

• Dependencies are minimized to enable learning and speed.

• Accountability is celebrated, not enforced.

The forest is harder to lead — there are no clear paths or guaranteed outcomes. But it is where real innovation and lasting value grow.

As Beck puts it:

“Without the roots, you won’t get the fruits.”

Communication and Metrics: Lost in Translation

Many organizational struggles come from working in different “places.” As Beck notes:

“We didn’t fail to communicate — we communicated in two different places.”

In the desert, metrics are weaponized to enforce control. In the forest, they are learning tools — guiding better decisions rather than replacing them. Dependencies, too, diverge: deserts use them to diffuse responsibility, while forests avoid them to preserve agility.

The Challenge of Leadership

The contrast between universes is clearest in leadership.

• In the desert, leadership is straightforward: goals are imposed, urgency is the motivator, and enforcement is the method.

• In the forest, leadership is subtle: leaders enable rather than command, align values with goals, and help communities thrive.

The forest may be messy and slow, but it is where deep value and resilient teams take root.

From Survival to Purpose

Beck doesn’t dismiss the desert entirely. Its urgency and structure matter in critical, high-risk contexts. As he admits:

“The forest made me appreciate the desert.”

The key is recognizing that these are not variations on a single theme. They are parallel universes. Confusing one for the other creates conflict, misalignment, and failure.

Even if you can’t escape the desert, you can bring a forestry mindset into it:

• Use metrics as insight, not weapons.

• Encourage accountability, even under pressure.

• Build trust and purpose inside rigid structures.

Conclusion

Kent Beck’s forest and desert metaphor moves beyond the surface debates of agile versus traditional management. It offers a framework for understanding context, culture, and consequence.

The question isn’t which universe is better, but which one you’re in — and whether your methods fit the terrain.

You don’t always choose the landscape.
But you can choose how to navigate it.

A The Forest and the Desert: Parallel Universes of Work and Leadership bejegyzés először CraftHub-én jelent meg.

Details

🚀Join our FREE Craft software meetup in partnership with Lufthansa Systems Hungária! Craft Conference is back on May 29-30 2025, and before the main event, you can attend a free software meetup – connect with like-minded professionals, exchange ideas, and get a taste of the engaging community that defines Craft!

In the first talk, Gábor Pécsy, Chief Architecture Owner at Lufthansa Systems Hungária, will discuss scaling software for airline operations. Then, Daniel Moka, Software Craftsman at Moka IT, will explain Mutation Testing and demonstrate how to use it through a live coding session.

Giveaway!
Five fortunate attendees will be selected on-site to receive an autographed copy of Gergely Orosz’s “The Software Engineer’s Guidebook”, courtesy of Lufthansa Systems Hungária.

📅Date & venue:

• 29 January 2025, Wednesday, from 6 pm
• Create26, Budapest, Király u. 26, 1061

To participate in the meetup you need to complete a short Google form!
🎟️ Register now for free to reserve your spot!🌐
Please note that the event’s official language is English!

Schedule
5:30 – 6:00 Registration
6:00 – 6:45 First talk by Gábor Pécsy
6:45 – 7:30 Second talk by Daniel Moka
7:30 – 8:30 Networking

DDD for Skies: Scaling Software for Airline Operations
by Gábor Pécsy (Chief Architecture Owner, Lufthansa Systems Hungária)
In his famous blue book, Eric Evans discusses how you can create and refine your domain model as a bounded context in detail. But how do you break up a system into bounded contexts? How do you tackle really large systems? The NetLine product family of Lufthansa Systems is a collection of over a dozen, originally independently developed, products that cover the vast domain of airline planning and ground operations. In order to transform to a coherent product family we need tear down data siloes and create alignment between NetLine components. In this session we will discuss how we began to untangle 30+ years of software legacy.

Mutation Testing in Action
by Daniel Moka (Software Craftsman, Moka IT )
Code coverage is not a quality metric. You can have 100% code coverage without any test assertions. Code coverage can help to detect untested areas of the code, but it doesn’t tell anything about the tested areas. How can we measure the quality of our tests then?

The answer is: Mutation Testing.

In this session, I will explain what Mutation Testing is and demonstrate how to use it through a live coding session. I will also present why Test-Driven Development (TDD) is the most optimal approach for writing code with the most reliable test suite.

Don’t write tests to increase code coverage. Write tests to gain confidence.

Join us, and discover the opportunities of crafting better software through innovative techniques, insightful strategies, and hands-on experiences.

Sponsors and partners

• Create26: A coworking space in the heart of Budapest with a thriving community and extraordinary benefits.
• Lufthansa Systems Hungária: Creating smart solutions to help airlines unlock their full potential. LinkedIn

Event website

A Craft Meetup by Lufthansa Systems Hungária bejegyzés először CraftHub-én jelent meg.

Who Is Dr. Cat Hicks?

Dr. Cat Hicks is the founder and principal scientist at Catharsis Consulting, where she leads research on the psychology of technical teams. With a background in cognitive science and a focus on evidence-based organizational change, she brings deep expertise in developer experience, learning culture, and team resilience.

Debunking the Lone Genius Myth

In a deeply moving talk at Craft Conference, Dr. Hicks dismantled the myth of the lone technical hero and replaced it with something far more compelling: a vision of healthy software teams built on evidence, resilience, and belonging.

Drawing on research with over 5,000 developers and engineering managers across 12+ industries, Hicks made a provocative case: the real technical risk isn’t a lack of brilliance. It’s the psychological gap created when organizations obsess over short-term performance.

The Hidden Costs of Invisibility

“Only 24% of developers,” she revealed, “believe their technical work is actually seen.” That number is even lower for those in less ‘traditional’ roles like DevOps or QA.

This invisibility, she explained, breeds distress and avoidance. Her research uncovered a 40% avoidance rate in code reviews among individuals with high Code Review Anxiety – a silent cost that undermines productivity, learning, and retention.

The LABS Model: Building Resilient Productivity

To counter this, Hicks introduced the LABS model – Learning culture, Agency, Belonging, and Self-efficacy – a framework that predicts resilient productivity. She stressed that these psychological metrics aren’t “soft” extras but essential foundations: “When something breaks, brittle productivity collapses. Resilient productivity adapts.”

AI Skill Threat and the Brilliance Myth

Hicks also coined the term AI Skill Threat – a measurable fear among developers that the accelerating pace of technological change will outstrip their ability to remain valuable. This fear is amplified by toxic contest cultures and “brilliance myths” that glorify innate genius over collective development. “If programmers believe their value lies in being born clever,” Hicks warned, “they’re less likely to ask for help, to give back, or to innovate inclusively.” These beliefs aren’t just demoralizing – they’re unsafe.

Designing Adaptive Team Environments

So what’s her antidote? Design environments that foster adaptive mindsets. Use rigorous psychological science to create spaces where learning is expected, risk-taking is supported, and team membership feels real. Interventions, she argued, must be evidence-based, peer-reviewed, and transparent. “We can run scientific experiments in real-life development,” she said. “And we have to.”

From Brains-in-Jars to Prosocial Teams

Hicks closed with a powerful call to action for leaders and practitioners alike: protect the problem-solving community. “Software development is not antisocial,” she reminded us. “It’s deeply prosocial.”

One of the stickiest myths she skewered was the brains-in-jars model: the idea that developers are just floating intellects, churning out code in isolation, devoid of emotion, context, or connection. It’s a sci-fi fantasy, not a workplace reality. “We’re not brains in jars,” she implied. “We’re humans, shaped by our teams, environments, and beliefs.” Clinging to this myth doesn’t just make work less joyful; it actively undermines collaboration, learning, and long-term success.

In an age of hyper-speed technological change, Dr. Cat Hicks didn’t just offer hope – she offered a map. A map that shifts the focus from who’s the best developer to a far more important question: do our systems allow everyone to thrive?

A Beyond the Brain-in-a-Jar: The Psychology of Software Teams bejegyzés először CraftHub-én jelent meg.

Location: Budapest (Hungary) and online
Event date: 24-26 February, 2023

Our very first crypto and Web 3.0-related hackathon. K&H HACK3 aims to connect young tech enthusiasts with companies interested in the future of Web 3.0. We brought challenges related to cryptocurrency, blockchain, artificial intelligence, and more!

Visit website

A K&H HACK3 bejegyzés először CraftHub-én jelent meg.

Location: Budapest (Hungary) and online
Online semi-final: 10‑30 October, 2022
Offline finale in Budapest: 9‑10 November, 2022

Shaping the future of business, and finding the secret to sustainable success together during Yettel’s 2-round hackathon event. Young developers, engineers, and startuppers were invited to solve a challenge in the following topics: sustainable urban mobility, SMB supporting digital platfroms, and energy efficiency in office and home. After the online semi-final the jury selected the TOP 12 teams that got the chance to take part in the offline finale. With the support of 19 amazing mentors, the teams benefited from 46 hours of mentoring sessions and perfected their projects in 24 hours winning € 12,500 in total!

Visit website

A Hack it your way bejegyzés először CraftHub-én jelent meg.