Leaker Majin Bu has noticed something in looking at screen protectors for the iPhone 17 line.

The screen protector for the alleged iPhone 17 Air has its camera cutout shifted from the right side of the Face ID sensors to the left side. The obvious implication is that the usual front sensor layout—an oval cutout for TrueDepth sensors on the left and a round cutout for the front camera on the right—will be reversed in the iPhone 17 Air. The camera will be on the left with the TrueDepth sensors on the right. Screen protectors for the other models show the camera in the usual position.

It’s unclear why Apple is shifting the camera on only this phone, though it likely has something to do with internal engineering. In order to make a phone so thin, Apple will need to shift some components. Of course, the two cutouts on the front of modern iPhones are joined into a single “pill” shape by the Dynamic Island, and that should be nearly, if not exactly, the same size on all iPhone 17 models. A small shift to the camera position, still hidden in an identical Dynamic Island, won’t have any impact on users.

Over the years, the iPhone front camera has regularly shifted position. On the iPhones 4 and 5, the first iphone with a selfie camera, it was on the left, then moved to the center for the iPhone 6, 7, and 8. When Apple introduced Face ID and screen notch with the iPhone X, the camera was positioned on the left side, where it has remained since.

The change may speak to some new internal design considerations intended to help make the iPhone 17 Air thinner, however. That means we could see the same arrangement on future iPhones.

The following article is a guest post and opinion of Yurii Kovalchuk, Senior Blockchain Engineer at Forte Group.

Three and a half years ago, I made a decision that completely changed the trajectory of my career. I left the familiar world of Web2 and stepped into the deep, chaotic, and exhilarating space of blockchain development.

It wasn’t an obvious move. I wasn’t chasing pump or overnight success. I was searching for meaning – for technology that aligned with my values, challenged my thinking, and gave me a reason to keep building.

Since then, I haven’t looked back. Web3 became more than a job – it became the lens through which I now see the future of the internet.

In this piece, I want to share why I made the leap, what I’ve learned from it, and how other developers can approach the switch with clarity and intention.

What to Expect from Web3

Flexible Compensation & High-Stakes Incentives

One of the first things that stood out to me when switching to Web3 was how different – and often more rewarding – the compensation structure is compared to traditional tech.

Instead of fixed salaries and HR paperwork, Web3 projects often offer a mix of stablecoin payments, on-chain invoices, and token-based incentives. In many cases, you’re paid directly to your wallet. Sometimes it’s a clean invoice; other times, it’s a hybrid model.

Then there are the tokens.

Much like equity in startups, project tokens give you a stake in the product you’re building. If the project succeeds, so do you. That adds a layer of motivation that’s hard to replicate in Web2. But of course, tokens can also drop in value just as fast – market volatility is real, and so are the risks.

That said, the upside potential is often much greater. Based on my own experience, senior-level Web3 engineers often earn more than traditional tech leads – especially when combining base comp with token incentives.

Still, there’s a tradeoff: stability.

Web3 moves fast. Projects pivot, funding shifts, markets crash and rally. It’s not the place to just “ride the paycheck.” But if you’re comfortable with change, the flexibility and upside can be worth every bit of the chaos.

True Remote, Not Just a Perk

While traditional companies slowly nudge employees back into offices, Web3 never left remote. Distributed teams aren’t a trend here – they’re the default.

For many, that means the freedom to work from anywhere, set your own rhythm, and structure your life around more than just work hours. It’s not “remote-friendly,” it’s remote-native – built into the DNA of how the industry operates.

Another standout feature? Anonymity is often the norm. In many projects, you’re not asked for legal names or personal documents. Payments go straight to your wallet, and that’s it. Especially in roles like smart contract auditing or white-hat security, contributors often remain pseudonymous. On my current project, I don’t know the real names of most teammates – some use voice changers during calls, and I have no clue where they live.

Of course, if you’re someone who thrives on in-person collaboration, Web3 might feel isolating. Offices are rare. Physical meetups are occasional, not expected. The culture is built around async communication and autonomy.

But if independence, flexibility, and privacy are high on your list, Web3 delivers that in full.

A Different Development Mindset

Web3 isn’t just a new industry – it’s a new paradigm. It’s a space where cutting-edge ideas are shaping the future of cryptography, distributed systems, decentralization, and consensus algorithms. And because the rules haven’t been fully written yet, traditional development approaches often don’t apply.

This is a world where experimentation isn’t optional – it’s expected. Many core tools are still evolving. Languages like Solidity are relatively young, with frameworks that may not even have a stable version yet.

If you’re the kind of developer who thrives on learning, tinkering, and building in uncharted territory, Web3 is the perfect environment. It’s messy, exciting, and full of opportunity.

But it also demands agility and a high tolerance for change. If you’re looking for predictability, legacy tools, or clearly defined roadmaps, Web3 might test your patience. Here, adaptability is a skill just as important as writing good code.

Open Source at the Core

In Web3, transparency isn’t just a nice-to-have – it’s the foundation. Around 80-90% of all code written for blockchain projects is open-source by default. That means anyone can dive into a protocol’s logic, explore its mechanics, or even start contributing directly.

But this openness isn’t just about collaboration. It’s also a trust-building mechanism. In an industry where scams and rug pulls still exist, reputation is everything – and publishing your code is one of the clearest signals of integrity.

Open code invites scrutiny. It encourages community contributions. It enables public, zero-cost code reviews that can help you catch minor issues long before a formal audit.

If open-source has ever felt like more than a side project to you – if you see it as a philosophy or a craft – Web3 gives you the space to live that out fully. It’s a rare place where building in public isn’t just encouraged – it’s expected.

Regulation Is Catching Up

Despite its rapid growth, Web3 still operates in a landscape of legal uncertainty.

Regulation varies wildly from country to country – while the EU has introduced clear frameworks like MiCA (Markets in Crypto-Assets), other regions still treat crypto as a legal gray zone.

That said, we’re starting to see real momentum. Last year marked a major milestone with the approval of Bitcoin and Ethereum ETFs in the U.S., and 2025 is expected to bring similar developments for other digital assets.

Web3 comes with endless possibilities, but also its fair share of challenges. It demands adaptability, curiosity, and the willingness to grow through uncertainty.

So how do you make the leap from Web2 not just smooth, but successful?

9 Tips to Succeed in Web3

Tip #1: Leverage Your Web2 Experience

When I started working on my first Web3 project – a blockchain-based supply chain solution built on Corda – my background in Kotlin and Java turned out to be a real asset. Since Corda is a private blockchain, much of the infrastructure was familiar. Even more important? The leadership skills I had developed in my Web2 roles as a team lead.

When hiring developers for that project, I wasn’t looking for deep knowledge of smart contracts or decentralized systems. What mattered most were strong fundamentals: solid programming skills, understanding of databases, and a grasp of networking principles.

So if you’re a JavaScript backend dev looking to break into Web3, the best move isn’t to pivot into something entirely new like protocol engineering. Instead, find a role that mirrors your current skill set within a Web3 context. It’ll be a much smoother and more sustainable transition.

Don’t try to change everything at once – that’s the fastest way to lose both momentum and income. Think of it as a step-by-step evolution, not a full reset.

Tip #2: Master the Fundamentals – Languages, Tech, and System Design

Before Web3, I was a die-hard JVM fan – Java, Kotlin, Groovy. I laughed at JavaScript memes and jokingly saw .NET devs as part of the “corporate dark side.”

But everything changed with my second Web3 project – a crypto wallet asset management system. One of the first hurdles? Learning to work with JavaScript and TypeScript libraries. The deeper I went into Web3, the more I realized that JavaScript – and increasingly, Python – were everywhere. Now, I use both almost every day.

If you’re preparing to enter Web3, add these languages to your toolbox. They’re not only essential in blockchain, but widely used across tech.

Just as important: don’t neglect core technologies and system design. In one hiring round, we chose a candidate with weaker Web3 knowledge but stronger design thinking and engineering fundamentals. Frameworks can be learned. Solid engineering instincts take longer to build – and matter more in the long run.

At the end of the day, what matters most is being an engineer who can solve problems, regardless of the stack. That mindset is your strongest asset – in Web3 or anywhere else.

Tip #3: Build Strong Relationships — With Teammates and Managers

In tech circles, it’s not uncommon to hear developers throw shade at managers, calling them useless, blockers, or just people who keep asking, “How’s that task coming along?”

That mindset usually comes with finger-pointing: the bug is QA’s fault, the deployment is on DevOps, the deadline pressure is all on management.

But over the years, working as both an IC and a lead, I’ve learned something simple but powerful: success in any role starts with taking responsibility and building trust with everyone around you.

Some of my best opportunities came not from CVs, but relations. One engineering manager I worked well with put me on the radar for the project I’m on today. And as a lead, I’ve offered flexibility and support to engineers I knew I could count on, whether that meant a day off or space to work in their own rhythm.

This isn’t about being nice for the sake of it. It’s about mutual respect and shared accountability. Strong relationships make teams more resilient and open doors that skills alone often don’t.

In Web3, where teams are distributed and fast-moving, relationship capital is real capital. Invest in it early.

Tip #4: Take Initiative, Own Your Work, and Share What You Know

This builds directly on the previous point – because strong relationships thrive when they’re backed by action, accountability, and a willingness to lead.

There’s an old saying that goes like “initiative gets punished,” but in my experience, that only happens when someone steps up without following through. I’ve learned a different rule: initiative gets rewarded.

Throughout my career, I’ve launched internal workshops, hosted guilds, kicked off side projects, and built community initiatives. More often than not, those efforts paid off – not just in recognition, but in real growth. For example, my work on corporate learning programs laid the foundation for my teaching role at the university.

In every project I’ve worked on, those who take ownership – the people who don’t wait to be told what to do – are the ones who get promoted, earn bonuses, and get looped into high-impact work. I’ve even seen cases where such people continued to receive raises during company-wide freezes. And when hard calls had to be made, like downsizing, they were always last on the list. I say that not just as a developer, but as someone who’s had to make those decisions.

In Web3, where the pace is volatile and teams grow and shrink quickly, being proactive, reliable, and generous with your knowledge is your best job security – and your fastest path to advancement.

It’s not just about getting ahead. It’s about becoming someone others want to build with, even when the road gets tough.

Tip #5: Build Your Personal Brand

No, this doesn’t mean you need to become a full-time influencer or share your life on Instagram (unless you want to). Building a personal brand isn’t about having a million followers. It’s about having a unique perspective, sharing it through public channels – online or offline – and making your expertise visible.

In a competitive market, your personal brand can be the edge that gets you noticed. When recruiters or clients are choosing between candidates, they’re more likely to go with someone who speaks up, shares knowledge, and brings something distinct to the table.

Let’s be honest: we all want to work with cutting-edge tech, on exciting projects, alongside top-tier people. A strong personal brand helps put you on the radar for exactly those kinds of opportunities. It shows you’re not just clocking in and out – you’re curious, engaged, and not afraid to share what you’ve learned.

Start small. Post occasionally on LinkedIn. Share a lesson, a tool you liked, or a technical insight. It’s enough to get going.

Not into tying your ideas to your real name? That’s fine – especially in Web3. Anonymous accounts on X (formerly Twitter) thrive in the dev and meme culture. Some of the most influential voices out there don’t even have a face attached. It’s not my path, but it’s a valid and powerful one if it resonates with you.

And if you want to take that visibility even further – the next tip will come in handy.

Tip #6: Follow Crypto Twitter (Seriously)

Crypto Twitter (or “CT”) is the heartbeat of Web3. It’s where the latest trends, tools, debates, and opportunities emerge – often before they make it to blogs, newsletters, or mainstream media.

To be blunt: if you’re serious about a Web3 career, being on X (formerly Twitter) isn’t optional – it’s essential.

I’ll admit, I used to overlook it. The trolls, the anonymity, the Elon factor – it all seemed like a buzz. But over time, I realized something: CT is where the signal is. Founders, builders, VCs, and core devs – including Ethereum’s own Vitalik Buterin – share their thoughts and product drops here first.

It’s not just a source of alpha. It’s a place to build your brand, grow your network, and unlock new opportunities. Right now, I’m part of Uniswap’s incubator program, and nearly all communication for the cohort (120+ people from 50+ countries) happens on X. Everyone there is active, plugged in, and engaged.

In fact, many employers and hackathon organizers now ask for your Twitter handle during the application process. And if you’re planning to launch your own project? Your community starts on X. No traction there = no traction at all.

Tip #7: Join Hackathons

Hackathons are a cornerstone of Web3 culture. Dozens happen every week – online and offline – with prize pools that often stretch into the hundreds of thousands of dollars. But the real value isn’t just in the cash.

Many hackathons offer investment opportunities, grants, or incubator invites for promising MVPs built during the event. It’s one of the most accessible ways to break into Web3, especially if you’re just starting out.

You don’t need to be a Solidity wizard to join. Teams usually include backend devs, frontend builders, deploy wranglers, and someone to handle the pitch. Even students or self-taught devs can contribute meaningfully. Every role counts. Beyond product hackathons, there are also security contests and CTFs (Capture the Flag), where the goal is to break things before they hit the mainnet. These challenges can pay extremely well – like the $2.35M bounty from the Uniswap v4 contest – and help improve the safety of the entire ecosystem.

Personally, I’ve taken part in several hackathons. Not every project was a winner, but the experience was game-changing. I met collaborators, stepped into new roles, and learned how to build under pressure. Hackathons aren’t just events – they’re launchpads for careers, connections, and ideas that can change your life.

Tip #8: Contribute to Open Source

As mentioned earlier, 80–90% of Web3 code is open source. And eventually, your code will likely live on-chain, fully visible to the world.

But beyond that, contributing to open source is one of the best ways to showcase your skills, signal good intentions, and build your reputation within the community.

It’s also a powerful way to get noticed. On my current project, a few teammates started out simply submitting GitHub pull requests. Now, they’re full-time contributors.

Another underrated benefit? It forces you to write better code. Knowing that other developers will read, review, and rely on your work raises the bar – and sharpens your craft.

If collaboration, transparency, and shared ownership matter to you, Web3 is your playground. So start small: comment on issues, propose changes, commit code to projects you admire. It’s not just a good experience – in many cases, it’s your ticket into Web3.

Tip #9: Use AI to Supercharge Your Workflow

There was a time when using AI tools felt like cheating, or at least something to hide. Some developers ignored them. Others downplayed their usefulness.

But by 2025, that mindset is outdated. If you’re still not using AI in your workflow, it raises serious questions.

Ignoring AI today is like refusing to write tests or use a linter. And in a space like Web3, where most of the code is open-source, tools like GitHub Copilot and AI pair programmers have access to massive training sets that can dramatically boost your output.

These tools don’t just help you write code. They speed you up, reduce mental load, and let you focus on real problem-solving instead of boilerplate. With the right setup, you really can become that “10x engineer” we all used to joke about.

And we’re not stopping at autocomplete. In 2025, AI agents are stepping in – smart assistants that don’t just generate code, but check their own work, analyze failures, automate tasks across platforms, and even communicate with teammates (or other agents). They’re capable of handling complex workflows that used to require multiple people.

So don’t snooze on AI. Embrace it, integrate it deeply, and let it amplify what you’re already great at.
Final Thoughts

Transitioning from Web2 to Web3 isn’t just about switching tech stacks – it’s a mindset shift. It means embracing uncertainty, staying adaptable, and becoming part of a fast-moving, global community.

Web3 offers developers unprecedented freedom, innovation, and ownership, but it also demands continuous learning, resilience, and a bias toward action.

If you’re ready to take charge of your career and lean into change, Web3 can take you further than you imagined. The tips I’ve shared here won’t cover every challenge, but they’ll give you a solid head start.

Welcome to the frontier.

Mentioned in this article

Caroline Pham, the acting chairman of the U.S. Commodity Futures and Trading Commission, has openly discussed an intention to leave the commission once she’s permanently replaced, people familiar with her plans have said, leaving significant questions about the future track of agency policy.

If President Donald Trump’s nominee for the chairmanship, former Commissioner Brian Quintenz, is confirmed by the Senate to take the job, the departure of Republican Pham could coincide with the planned exit of fellow Republican Commissioner Summer Mersinger to run the Blockchain Association.

Who’s left? The new Republican chairman — who served as a policy head for a16z after leaving the agency — would find himself alongside a single fellow commissioner: Democrat Kristin Johnson.

This leaves Quintenz with practical control of the agency’s agenda and staffing, because almost all of its employees will report to his office. But the CFTC could be hamstrung to make new policy as Congress is working on legislation that could assign the regulator new powers over the crypto industry. The longer it waits before the White House picks nominees to face Senate confirmation, the longer the potential delay of higher-stakes policy work that requires commission involvement.

The CFTC normally has five members — a chair and two others from the majority party plus two commissioners from the minority party. If Quintenz gets the Senate nod, he’s taking over the spot currently held by Christy Goldsmith Romero, a Democrat who said she’s leaving her extended stint in government service when this role ends.

The sole Democrat, Johnson, hasn’t cultivated a reputation for her digital assets views, like the sharper rhetoric associated with the Securities and Exchange Commission’s lone Democrat, Caroline Crenshaw. It’s unclear what common ground, if any, would be carved out between Johnson and Quintenz if they were to serve as a two-person commission.

Mersinger will start as CEO of the crypto lobbying group Blockchain Association at the start of next month, according to board president and chair Marta Belcher’s remarks highlighting the new hire on Wednesday at Consensus 2025 in Toronto, calling her a person who could take crypto “to the next level in policy.”

“This decision is not easy, and it breaks my heart to leave the agency that I have grown to love so much over the last five years,” Mersinger said in a statement. She’ll soon be lobbying on policy that is likely to one day direct her former agency to regulate the spot markets for the bulk of crypto trading in the U.S.

As the interim head of the agency appointed after Trump reclaimed the White House, Pham, a former executive at Citigroup Inc., has taken an aggressive stance to ease the CFTC’s use of enforcement actions to steer crypto matters and to rethink some of its policy positions.

The acting chairman didn’t immediately respond to a request for comment after hours on Wednesday.

Before Pham and Mersinger arrived in a slate of four appointees that also included Democrats Johnson and Romero, the CFTC had been down to two commissioners. The recently departed Chairman Rostin Behnam, a Democrat, had served for a time with Dawn Stump, a Republican.

It’s unclear what the president’s nomination strategy may eventually be for the CFTC’s potential three vacancies if Pham departs, which would include one position for a Democrat. So far, Trump has sought to remove Democratic appointees from federal regulatory agencies, such as at the Federal Trade Commission and the National Credit Union Administration.

Read More: CFTC Commissioner Mersinger to Be CEO at Blockchain Association

By late 1967, Fairchild Semiconductor had become a shadow of its former self, facing severe budget cuts and the loss of key personnel. These challenges triggered an exodus of talented engineers and executives, ultimately resulting in the formation of over fifty new technology companies. However, none of these spin-offs achieved success as rapidly or significantly as Intel Corporation.

The ease with which Intel was brought into existence was in large part due to the stature of Robert Noyce and Gordon Moore. Noyce, widely credited as the co-inventor of the integrated circuit alongside Jack Kilby of Texas Instruments, was already an esteemed figure in the semiconductor industry. Moore, also a co-founder of Fairchild Semiconductor, was recognized for formulating Moore’s Law, accurately predicting the exponential growth of transistor density on integrated circuits.

Initially, the new venture was named “Moore Noyce Electronics” when the founders filed the company’s incorporation documents. However, they soon reconsidered and selected the name “Intel,” short for “Integrated Electronics.”

Interestingly, to secure this name, they had to purchase rights from a motel chain operating under the same title in the American Midwest. Thus, the stage was set for Intel’s ascent as a global leader in semiconductor innovation.

Continue reading the History of the Microprocessor and the Personal Computer.