Charles L.

Have you noticed the excitement around #Dapps lately? After engaging with several startups and founders through Blockchain Ireland and #hackathons, I can confidently say that It’s a great time to be a Dapp founder in the web3 space. I did some further research to confirm what I saw on the ground. Here's what I've observed: 1. Shift from #Infrastructure to #Application Development The previous few cycles primarily focused on the development of blockchain infrastructure, which included the creation of foundational protocols and platforms. The current cycle shows a noticeable transition towards developing Dapps that leverage existing infrastructure. This can be seen with the significant increase in daily unique active wallets interacting with Dapps, reaching an all-time high of 17.2 million (according to DappRadar) in Q3 2024, a massive 70% rise from the previous quarter. This is also confirmed by the Garnter’s hype cycle where mainstream adoption will peak in the next 2-5 years! 2. Dapp Sectors are #diversifying The Dapp ecosystem is expanding beyond traditional finance and gaming into sectors like social media, supply chain and healthcare. A great example is the social sector which experienced a 66% growth this year! 3. #Faster build to deployment using AI Imagine being able to deploy your first Dapp in days instead of weeks. Founders can now leverage the assistance of AI to automate code generation, testing and deployment. For non-technical founders, we have AI-powered no-code platforms which include no-code smart contract deployment and gasless transaction, reducing the manual effort, greatly improving the user experience and accelerating the development cycle with A/B testing. -- My experience working on the recently finished Blockchain Bootcamp highlighted this growing interest. Passionate founders from Web2 are taking the leap to build something awesome, while talented contributors are eager to gain hands-on experience and drive success. If you’re planning to build a Dapp or contribute to one, check out what BI.Startups.Web3 is doing. It’s a fantastic community bringing founders and contributors together in Web3 -- What sectors do you think will dominate Dapp adoption in 2025? Share your thoughts below! P.S. In my next post, I will share some observations around the biggest challenges for founders in the current landscape so keep an eye out and give me a follow. -- Image from DappRadar #startups #founders #us #europe #asia #hackthons #crypto

8

My latest on Paragraph: Quickstarts Are Recipes - Developers Are Bakers My plea is that developers stop overcomplicating their quickstart guide when building software. Treat your quickstart like a recipe: - Start with a desired outcome, much like a baked good, and get that developer from 0 -> 1 - Set a 'prep time' and 'baking time' that are clear and won't take someone an entire afternoon - Make limited assumptions and make sure you list every single "ingredient" down to what version of a particular library might be a prerequisite or environment constraints - Finally, don't let your quickstart go stale - you want them to buy your cookbook after they follow your recipe. https://lnkd.in/eFDjGR7U

9

1 Comment

If anyone knows any devs - tag away please For a few years now we’ve been building out and using an amazing server provisioning and code deployment tool https://deploy.dev After an extensive 6 month program of rolling it out to Aero Commerce agencies, who all love it, we’re now making it public for the first time - whilst it’s been working in a commercial environment for years now we’re launching it in Beta for a lucky few devs / agencies we know and trust The story : After using combinations of forge and envoyer that didn’t do fully what we wanted, we built our own to provide the missing links. It’s been a real game changer for us in terms of productivity, simplicity and efficiency. You can provison, boot up and manage servers in numerous industry leading hosting providers at the touch of a button. Code can be centrally managed through the major repositories and deployed automatically or manually through our seemelss integrations. There is no charge for this to our friends or friends of friends whilst in beta and we’d love your feedback Just register at https://deploy.dev and have a play

28

15 Comments

Have you been looking on Wrongmove? Most developers waste a whole lot of time looking at ‘deals’ that never stack-up. And, if you do ever buy something that’s On or ‘In’ the market (where you’ll be bidding against competition), the only way you’ll do that is by being the person that pays the most. In a business that’s already so risky, paying too much for things before you’ve even started is the worse thing you can do. To listen to this full episode of the Inside Property Development Podcast, head to the link in my bio now. . . . #propertypodcast #propertypodcasts #propertypodcasters #propertypodcastsuk #propertybusiness #propertytips

6

3 Comments

Clojurists Together has changed some of their process for funding Clojure projects: Members get to directly vote for projects! If you're a Clojurists Together member, you will be getting an email with a link to rank your top 5 projects to receive funding next year! #clojuriststogether #clojure

2

If you're interested in: → A journey from Electronic Engineering -> full stack web development → Insight into how we foster autonomy and empowerment at Sensoteq → Practical tips to maximally leverage AI, particularly in software This might be worth a listen 😉

17

2 Comments

Event-driven architectures are critical for modern multi-user systems. We’ve been building evlua for over 2 years now, and it's fascinating how it handles I/O operations in multi-user systems. When it comes to event-driven I/O, evlua can streamline development cycles when dealing with blocking I/O challenges. Built on Lua, it addresses core issues in thread allocation and connection handling. The implementation keeps the interpreted environment clean while managing system resources - eliminating the need to handle platform-specific constructs. For teams building scalable systems, this approach to event-driven I/O offers a path to optimize performance. Open to discussions on architectural implementation details. #eventdriven #softwaredevelopment #developertools #coding #systemdesign #lua #programming #techinnovation #developercommunity #opensource https://lnkd.in/gcWmCMBm

23

6 Comments

🌟 Check in: searching for React Native/React engineering roles 📈 TL;DR; still going strong with optimism! (mostly) G’day! This iteration of the great hunt has been a bit drier than what I have experienced previously however, I remain optimistic and energised to find the right role where I can make a meaningful impact in an interesting problem space. Whats yo stats?! Weirdly the numbers align with that of a post during my last round of interviewing: ❌ Unsuccessful: 6 - Comprising of rejections, retractions and ghosting. it’s not you, it’s me (maybe :D). There is always something to learn from a failure - bank it and advance! Some will remain on my radar for future rounds when the timing is right. 🚀 Open: 11 - I am fortunate to be progressing with some interesting companies and excited to see where these go! What else ya been up to? - Joined further recruitment platforms; I am now testing the waters with haystack and wellfound (links in the comments). - Amended CV content and structure 3/4 times - Created a cover letter template - this seems more of a requirement than in previous rounds and I wanted something that stood out similar in appearance to my CV. - Studying - with each company employing different stacks and methodologies, there is much to brush up on. - I caught up with some peeps in a similar boat who are building exciting things for themselves - inspiring stuff! I may follow their lead. While this interview process is quite demanding, I am looking forward to taking some time to enjoy the content and inspiration from frontendnation, which runs today until the 7th. Is anyone else tuning in? let me know which talks you are looking forward to. If you would like to discuss opportunities, or a fellow engineer looking to chat through anything of interest, please feel free to reach out. That’s all from me, catch you on the flippity! #lookingforwork #opentowork #fullstack #JobSearch #SoftwareEngineer #CareerJourney #react #reactNative

17

3 Comments

Great to see that CDDO / GDS have updated their guidance page on the use of Progressive Enhancement on UK Government services 😍 https://lnkd.in/esuSVb29 Keep fighting the unnecessary bloat that JavaScript has brought to the modern web! ✊ #a11y #accessibility #webperf #progressive #enhancement

95

7 Comments

TDD is expensive Like many other niche technologies Delivery of software is not only a technical problem It’s logistical and people problem as well It can be using Kotlin in Java company It can be adding a better database engine It can be applying Event sourcing to all systems You can say all of those are great But there are a couple of non-technical problems 🧠 Knowledge The whole team must know the new solution They need space to learn and practice You may get training from an expert Both cost money and time 🚦 Risk You face the bus factor What if the devs will leave? (they will) How will you maintain the niche solution? How much will it cost to hire or train a replacement? 👩 Hiring Adding new technologies narrows the pool of hires The more niche you go the harder is to find a good fit The longer hiring process will strain delivery You'll have to balance with higher salaries ☯️ Alignment What about your current team? 80% of them like tests but aren’t fans of TDD What will you do? Force them to learn or let them go? The culture will take a hit and retention will sink What can you do instead? Keep it simple Keep it boring Focus on the basics Drive incremental improvement Find alignment before picking new tech Get excited about the features and business If you don’t need to fix niche problems You get more time to deliver value

24

13 Comments

Do you want to know how to identify change in HTML, redline HTML documents and how to visualise changes? From text to tables, MathML to SVG, our Product Director, Tristan Mitchell, chats with the Centre for Information Development Management (CIDM) on how you can improve your HTML workflow. Perfect for a 30 minute lunch 'n learn! https://lnkd.in/ejWDQxPE #cidm #html #htmlcompare #documentmanagement #workflow #processefficiency #costreduction #timesaving #deltaxml

8

Are you raising? Whether you're a startup seeking an Angel or VC or an established company with your eye on that sweet PE pie, something is missing from too many pitches. Your TDD. 💸 Your cash flow can be as clear as crystal and fat as a hilarious cat. 💪 Your tech stack can be as resilient as burnt-on lasagna. ⏹ Your market fit can be as perfect as the Tetris piece you've been waiting for. But how's your talent looking? TDD, or talent due diligence, looks at your key players' strengths, weaker points, and potential. If you don't do it, you can bet your bottom (or is that last?) dollar that your potential investors will. Do you know how to iterate a product front and back? Do you have BIG team leadership experience? Have you scaled before? If not, then you have some options. NEDs: Non-Executive Directors provide the strategic oversight and industry insights you need to plug those leadership gaps. Fractional C-Suite: Hire part-time executives with a wealth of expensive experience without the full-time commitment. Talent Development: Invest in coaching to turn your promising team members into powerhouse leaders capable of taking your company to the next level. The most important bit is... Put your talent due diligence into your pitch! Talk about who's on your team and how they will get you where you're going. I'd love to hear from you if you'd like more info on the above.

9

The value of feedback loop on Postman collections over the years can't be understated - it just isn't visible and well understood. I mentioned the importance of this in my writing today on editors Dave Shanley and Florian Martens - I get a regular stream of these. https://lnkd.in/ecjSxZZe

13

Does Screenshotbot save on build times? This was a question that surprisingly came up a couple of times at #dcbln24. It probably had something to do with the large number of platform and DevEx folk at the conference. In any case, the answer turns out to be "Yes". More specifically: You'll save 19% in build times on average, and 49% in build times in the P95 case. The savings come from avoiding re-runs when screenshots change. Read my blog post with the analysis, and I'd love to hear your thoughts: https://lnkd.in/eEh4zqkN

6

Often hidden and ignored, although having significant impact in long term, costs in software development - lost opportunity cost and total cost of ownership (TCO or cost of maintaining and scaling software long term). #software #productdevelopment #technology

12

"If you haven't been able to maintain and improve the quality of the current codebase, how can I trust that a rewrite won't lead to the same issues?". This single rejection changed the way I approached software improvement forever. Whilst I was passionate that a refactoring needed to happen and I strongly believed that my proposed structure would be superior to the existing one, I could not refute my manager's point. The code didn't become unmaintainable because it had lacked an elegant design in the first place. It had become unmaintainable because we'd failed to implement and evolve it whilst maintaining quality. The problem we needed to solve was not designing elegant solutions up front and implementing them. And then waiting for the code to degrade over time until we had no option but to go back to the drawing board and rewrite the whole thing from scratch. The problem we had to solve was how to manage change whilst maintaining quality indefinitely. By creating the constraint that we would not be allowed time for large refactorings and rewrites, my manager forced our team to think of better strategies to evolve the code and improve quality a little every day. He effectively introduced me to the concept of Continuous Improvement.

179

28 Comments

Your dev team is under resourced Spoiler - it always will be Don't get trapped thinking if you just had two more (or fifty more) devs you'd be able to work through the backlog and get ahead. The problem is that teams try and filter and prioritise *down stream* on outputs. 100's of outputs. Try filtering and prioritising *up stream* on strategic outcomes that matter to the business (and across the business).

12

9 Comments