Piotr Daniszewski

#Web applications are the backbone of current #tech. but if everyone knows how to develop them - why do so many companies fail at doing so? We bring you our modern guide on the subject: From known frameworks, typical challenges and even coming trends, our guide provides you the value you've been seeking. https://lnkd.in/e8v6AsTU

1

#Web applications are the backbone of current #tech. but if everyone knows how to develop them - why do so many companies fail at doing so? We bring you our modern guide on the subject: From known frameworks, typical challenges and even coming trends, our guide provides you the value you've been seeking. https://lnkd.in/e8v6AsTU

3

During my attendance in two ruby conferences in Europe, I interviewed top Ruby developers at the conferences about the current job market. Given that Ruby on Rails is a mature framework, I wanted to know: what's the current state of the Ruby job market? These are the  valuable insights I got from industry experts on job prospects, challenges for juniors, and tips for success in the Rails ecosystem. Watch my full video on my YouTube channel (@tillcarlos) for more in-depth insights and discussions.

10

1 Kommentar

Last demo before private beta 🤫🤫🤫 With a very small team at Slite we built a new product in the last 6 months: an AI company search that works with all your tools (yes, even Notion, Confluence, Sharepoint etc 🙄) We've been in pilot phase for a bit and usage starts to kick in! In fact with less than 1% of Slite users piloting it, it accounted for 8% of our AI search queries on all our plateforms 🔥 In 2 weeks this baby is getting in private beta, stay tuned! And if you want to support 1. Leave a like! 2. If you want to be alerted, check out the link to the waitlist in comments 💬 3. And share your takes: mention the teammate that would love it, share the use case you want to try it with! See you in 2 weeks on this and have a terrific week 🙌

110

11 Kommentare

Are you finding yourself frustrated by the fact that OpenAI no longer offers free API tokens, but requires credits? Check out GPT4All, with the mistral-7b-openorca.Q4_0 local LLM file. Works well with Langchain, and while a bit on the slow side, allows you to tinker around and get the hang of things without having to spend a penny. #degreesoffreedom #langchain

1

Attending Berlin Buzzwords? I am happy to share that I'll be speaking at Europe's biggest search conference. The session will focus on the transition to domain specific computing and its benefits over software based search. Join me on on June 10th at 14:50 at the main conference hall, KesselHaus. For the full session outline : https://lnkd.in/d5hznPeP I am looking forward to seeing you there. #search #database #vectorsearch #elasticsearch #keywordsearch

36

3 Kommentare

🚀🚀Here are the top 100 B2B SaaS startups in Europe & Israel - 2024🚀🚀 See which companies are leading the AI and data revolution. 🙏 Thanks to Amy Lewin & Siftedeu 💾 Download the full report now! 🤞 Hope you're own the list #founders #saas #vc #growth #scaling #europe

1

1 Kommentar

"You have to be solid in one market before spreading to a new one. " Had an awesome interview with Shanna Huber founder of My Junna Software about how to expand your SaaS into new markets. Check out the comments for the link to the full interview 👇

5

1 Kommentar

Why we are changing our stack to Rust? We have been working with trading in #Bitmaker for 3 years already. First, our stack was based on pure Python. If you tried to start a business from scratch you know that one of the main targets is fast delivering your product to the market. We choose a Python-based stack as a well-known and fast-to-write. The slow reaction was the greatest problem. Building a trading constructor based on the math operators we quickly got an easy-to-use solution but what about speed? Calculating the grid with 40+ orders was about 50-100ms, of course, we tried to profile code, and replace some parts with C-based libraries, but... It was too slow to use.    The point in the history of the further expansion of the use of Python was the decision to write arbitration. The most important metric for the quality of an arbitrage bot is the time from the order book change on the exchange to the exchange receiving the arbitration order. What caused the delay? Of course, from the network delay both at the level of external interactions and inter-service communication, we want not only fast, but also secure, don’t we? Let's get back to where I started. Rust. Why not Go or something similar, because growth development is very, very expensive. I’ll omit the entire pool of reasons, leaving only the main thing: resources, in addition to speed, growth consumes resources very, very moderately, which just allows you to reduce the number of nodes in the cluster and reduce possible network delays. For us, the difference was about 10 times. The arbitration bot began to consume 80 mc instead of 800. Memory consumption decreased from 400 MB to 30 MB. Thus, we were able to “compact” approximately 10 times more bots into a standard cluster node with 8 cores. What else? Of course, Rust like a Lamborghini, it looks cool, fashionable, and modern, but is it right for you? If you live in conditions of sufficient budgets and you have time to write code that is very difficult to maintain (well, compared to Python), and the response time of your system should be measured in tens of ms, then Rust is your choice. But will you drive your brand new Lamborghini to places where there may not be excellent roads? So here, too, if you don’t have full confidence that you can achieve the desired result with less effort, for example, using the capabilities of libraries of the same python, then taking a Rust just for the sake of writing a beautiful line in the description of your project is not the smartest idea In conclusion, in modern development, it is often said that infrastructure is cheaper than quality development. And it is true. But never forget that horizontal expansion always adds another one or two (sometimes 10) extra ms of delay, which for trading systems can negate many, many hours of optimization in other parts of the system. It is my first try write public post, so welcome to discuss. Best regards, Ruslan #Python #Rust #Architecture #Trading

5

Wow, this is truly impressive from Google! 👏 A generous offer of 1,500,000,000 tokens daily through the Gemini API is a game-changer for developers. The value proposition is unmatched, especially with the added benefits of Google AI Studio. Different tiers ensure that many users can experience the platform's capabilities. #AI #GoogleAI

1

1 Kommentar

Imagine, you installed Telegram or WhatsApp, and you can't send a message to your friends right after registration. Why? Because you didn't deploy a connection contract. It's nonsense, correct? But in the #web3 cross-chain interaction world, it is absolutely normal. That's why we're building YAR - mass-adopt #crosschain interaction for each. No limits, no governance, no hassle, no waiting, no coding... Real freedom for your data and assets. True web3 #interoperability through the real decentralization. https://lnkd.in/dBVAx_wW

3

🌟 The Right Architecture for Your SaaS Platform 🌟 When it comes to building a SaaS platform, the architecture you choose can make or break your project. And guess what? The choice isn’t black and white—it depends on various factors. 🤔 Let’s talk about monolithic architecture first. It’s like a cozy studio apartment where everything you need is in one space. It’s perfect for simpler applications, quick launches, and when you want to keep things straightforward and snappy. Plus, if your team is small and you’re looking to hit the market fast, going monolithic can be like a speedboat—swift and efficient. 🏁 Now, onto microservices. Imagine a sprawling mansion with different rooms for everything. This is the go-to for complex, scalable applications that grow with your user base. If you’re planning to frequently update features, need high fault tolerance, and love the idea of using a variety of tech stacks, microservices are your best bet. It’s like having a team of specialists, each handling their own department. 🏠 For SaaS development, your choice should be tailored to the specific needs of your project, the expertise of your team, and the complexity of the application you’re dreaming up. Whether you’re a startup or a seasoned enterprise, the architecture you choose is the foundation of your service. So, choose wisely! 🧐 What’s your experience with monolithic vs. microservices architectures? Drop your thoughts below! 👇 #SaaSDevelopment #SaaSSolutions #SoftwareArchitecture #TechTalks #TechChoices #BuildingTogether

4

Hey linkedIn 🌞 Last post, I wrote about our database technology choices at Landjourney. Now, it's time to talk about the APIs that make our platform actually do something. You might be wondering how we are building things (or... maybe not, maybe that doesn't interest you that much... either way, just keep reading 😂). Interestingly, as I'm writing this, I'm realizing we're pretty much building things like we are operating a bar. (The following description excludes the gateway) 1. We first validate that the request payload and parameters are what we expect to receive in terms of fields, but also the types of the fields, just like a doorman. By doing that, we ensure that only happy drinkers can get in and that nobody has a dangerous weapon. It helps lowering the risk of troubles... 2. We then detect the tenant that is being queried, based on multiple criteria. It could be DNS routing, a path parameter, or headers. Depending on the tenant, we will inject the proper configuration, as all tenants have their own database, their own buckets for documents, their own encryption keys, etc. See it as using the right card for the proper customer with the proper server and the proper tab. 3. Then comes the time to authenticate the user based on the jwt token. As part of the process, we validate that the token hasn't been invalidated and we extract the different claims and validate that the user really is a member of that tenant... just like ensuring that you don't sell drinks to someone that's already partying too hard and came back through the back door after having being kicked out, or bill to a tab that has been closed. 4. Before executing the API call, we will validate the permissions of the user. Permissions can be validated using groups (System or custom), or atomic permissions set on the user and/or the resource. By doing that, we are supporting both RBAC and ABAC (this part could be the topic of a post). It's pretty much like making sure you don't sell drinks to a minor or someone already partying too hard... 5. We do the work... pretty much like mixing a cocktail. 6. At last, we map the results that are being returned to a response schema, in order to make sure that we never leak something we don't want. Every single piece coming out of an API call must be mapped explicitly. It helps making sure we don't serve the wrong drinks to the wrong group... Like giving a tequila to someone that asked for a mojito. Every service is 100% decoupled, which means we can offer an incredibly high uptime. If something goes wrong with one service, it won't bring down the whole party - just a specific area of the bar (like one of the bathroom after a customer was sick or something). It may sounds complicated, but it's actually pretty straightforward with fastAPI, JWT and Pydantic models. Stay tuned for the next post, where I'm gonna write about the way we're building the different UIs :-) #fastAPI #pydantic #API Image: https://lnkd.in/g2UkNXwk

29

10 Kommentare

For over six months, our incredible growth team at Dashly has been on an epic journey, optimizing inbound funnels for companies focused on meeting requests. In the main roles are:  Vadim, the mastermind behind the numbers and experiments,  Maria, the technical wizard who brings these experiments to life,  and Dmitrii Sergeev, our client success champion ensuring every client achieves their growth potential. We discovered a critical issue: only 20-30% of leads who submit a form actually make it to a meeting. Our initial fix? "Update the lead capture form and pray." 😅 Spoiler alert: it didn’t work. Determined to make a real impact, we set an ambitious goal to double the key metrics, converting traffic into qualified leads and leads into scheduled meetings. This would boost ROMI for ad channels and cut sales team costs, allowing them to focus on high-quality leads and complex tasks. We analyzed six months of client data, defined key metrics, and identified decision-makers in the client's team. We created tailored funnels and built a detailed Customer Journey Map to illustrate Dashly’s integration at each step. Configuring the client’s CMS, CRM, and analytics was no small feat, but we set up events via GTM, GA, and our own analytics, collaborating closely on API tasks. The results were clear: identified stakeholders, a clear CJM, numerical goals, and a rhythm for achieving them.  Of course, almost 100% of the time, something goes awry—technical issues, unapproved changes, missing expertise. But with dedication, we navigate the challenges and stay on track, maintaining a rhythm of launching and evaluating experiments every Monday, Wednesday, and Friday. Ready to grow? 🌟  Our Dashly team can take on two more clients for joint work. If you have an inbound sales funnel generating leads and a sales team handling them, email us at [email protected].

7

Yesterday we bought beep(dot)review for $500. And there is a reason why. This is our most expensive domain yet, and we have big plans for it. As some of you know, Beep is our tool for website reviews and visual tasks and it already has a separate domain. But our goal is to turn Beep into a single hub to review all of your company's assets. I can't tell much, but, it will be like a bot that helps you review any media you have. So the domain is almost like saying, "Beep please review...my website💻, video📽️, ad📢, pdf📄,...."

29

12 Kommentare

It's been long overdue, so here it is: Our relaunched website! AccessOwl started in 2021 as a small side project of Mathias Nestler to solve the pain points he had as a CTO. Back then a startup which wanted to automate their access management had a single choice: Implement Okta and upgrade every single of your SaaS applications to the enterprise-plan. 🦉 Nowadays we are proud that for most non-enterprise companies AccessOwl is actually the better solution ⭐ Shadow IT detection Uncover which apps are used and how often ⭐ Auto-Provisioning Create or revoke access to any tool, no matter what API is available ⭐ Access Requests, Approvals & Reviews In a single click, right in Slack ⭐ Automated On- and Offboarding Triggered by your HRIS to never miss an offboarding again ⭐ Integrates with your IdP No matter whether it's Google Workspace, Microsoft 365 or Okta From the early days to today the product has changed massively and we finally have a website to show for it! www.accessowl.io

54

7 Kommentare

💥Martin Rusnak - Interim CTO joined The $500k CTO Podcast as a VIP guest on Friday. He's worked as an interim or fractional CTO for 15 (!) SaaS companies and shared lots of interesting insights about: 1. The Difference Between Interim and Fractional CTOs: Martin explained how these roles differ in terms of time commitment and responsibilities.💡 2. Importance of Building Trust Quickly: As an interim CTO, gaining trust fast is key. Martin shared how he builds strong relationships within the first few weeks to ensure success. 📝 3. Balancing Technical and Soft Skills: Communication, emotional intelligence, and empathy in leading tech teams is more important than deep technical skills. 4. Continuous Learning: Staying updated with the latest tech trends is vital. Martin talked about how he keeps his knowledge fresh and relevant, even with a packed schedule. 🤓 5. Networking and Getting Clients: If you are looking to enter this field, Martin's tips on networking and finding clients can be useful. Let me know in the comments if you'd like to get notified when it's LIVE. #TechLeadership #CTO #Podcast #TechInsights #Leadership #FractionalCTO #InterimCTO #ContinuousLearning #Networking

8

1 Kommentar