Samu Jukkola

Personally I prefer writing Kotlin as compared to Swift. Kotlin synthax is more familiar.

4

How can I manage my situation best possible. Coding in your free time, after 8 hours of warehouse work, seems quite exhausting. Plus fulltime alone daddy, so lot of extra responsibility, so the gap / energi left is quite low. Had to take another job direction for now, untill I will finally land a programming job here in Denmark. If that case is actually possible though, Lol. So how to get the best out of it with programming 🫣😶‍🌫️🧐🤔 #HowTo #TimeManagement

1

Do not force yourself to work on the next thing if your energy is low. Do this instead. I must admit that sometimes I don't want to work on a ticket next in the queue. It usually happens to me in the afternoons. I worked on something in the morning, and now I feel like browsing the internet.  On the days I really don't feel like it, I find a small thing that will improve our codebase, like a minor gem update or a needed refactor. I enjoy these things, and even though I should be working on something else, I will be more efficient at doing things I enjoy more. So I do. I can do it because I know that the next day, when I start working, I will pick up that ticket I didn't want to work on the day before. And I will be much more efficient and focused. What are your ways to deal with this? #softwareengineering #programming #coding #DevLife #RubyOnRails 

2

1 kommentti

Daily Quick Tip: Tomorrow, when you start your workday, check if the services delivered through HTTP are providing the content in a compressed format. Depending on the traffic, this can save a significant amount of money and only add a small amount of latency, typically around 10-20ms. If you're using a cloud-native load balancer or tools like Traefik, it's very easy to enable compression. If not, you can implement it using a library in your development language or platform. Don't forget to check out the complete benchmark around HTTP compression that Paul Calvano did in his post https://lnkd.in/dVzBFj6n . His research and findings were extremely helpful in providing the insights that can potentially save you a lot of money on data transfer costs. #aws #compression #costs #cost_saving #traefik #cloudnative #tip #quickwin

9

I didn't expect to say it this soon, but I'm enjoying working with TailwindCSS. I have used it for the AutoProject webapp. And with the help of LLMs, writing TailwindCSS has become quite easy. I often just describe the design I want and ask GPT to come up with the TailwindCSS for it. It works well, most of the times. Just a month or so ago, I talked about how I disliked Tailwind for its very long and verbose CSS classes. Every html element in your code will have a long list of class names to get the required design. I still dislike it, but after trying it more, I felt the productivity gain is worth it. Prior to this, I always preferred writing my own CSS because I wanted the design to be very unique and customized to me. In hindsight, that's still good but it reduced my shipping speed and added unnecessary "figuring it out" and "testing" overhead. I am continuing to write my personal CSS + Component library to factor in that uniqueness, but in the meantime, tailwind looks like an excellent tool to iterate very fast and build great looking UIs. With a stable Tailwind version 4 releasing soon, it looked like the right time to pick it up. In version 4, we can expect: - 10x faster builds - 35% smaller in size - Use of lightning CSS (I'm using this for my personal CSS library too!) - A custom parser that's 2X faster than PostCSS. (They literally designed new data structures to achieve this!) If you have been a skeptic like me, to Tailwind or CSS libraries in general, don't sleep on it. I'm thinking of migrating even TechFlix to TailwindCSS.

26

3 kommenttia

I used to have bookshelves crammed with books at my home. I left it a long time ago, but one shelf of untold stories I carry with me. Some are about a young fellow who graduated with a diploma in law, quit that field, and two years later became a mid-level full-stack developer. Others are about senior-level tech challenges I had the chance to solve with my team—problems so unique that the internet offered no solutions. Perhaps these stories should have been shared, with lessons learned and passed on. Six years later, I'm quitting something I once considered my dream job. Definitely in the most turbulent times for IT during my career, with all the layoffs and shifts in the industry. Yesterday was my last day as a hired worker. I want to thank my ex-colleagues for all the moments we shared together and for the challenges we overcame as a team. And today, on my 27th birthday, with a touch of birthday-fueled bravery, I'm stepping into entrepreneurship. Half a year ago, I started an MBA in IT program to learn more about the business side of the industry in pursuit of a role as a solution architect. By then, I had read all the most popular books about solution architecture. Eventually, I discovered that the true solution wasn't a fancy title, but the freedom to build something on my own. I remember sitting with that huge book with a clock on the green cover you all know about and thinking, do I really have to study all these algorithms for the nth time just to pass an interview to go and make someone else richer? So, who knows where this journey will lead? Perhaps back to the familiar comfort of a 9-to-5 in a few months. But that's the beauty of this experiment, isn't it? Like an A/B test, it's a chance to see how the skills gained in the world of IT translate to the business landscape. If you have an entrepreneurial itch, or are an engineer curious about new challenges, you might find my next publications interesting. At the same time, my first priority is business development, building a team, and mastering new skills like marketing and sales. Also, I always wanted to write. I'm curious how this incoherent flow of thoughts above will transform with time. Cheers!

24

8 kommenttia

Traditionally, API management platforms combined different features (like gateways, analytics, and developer portals) into one big package. But this approach has limitations - it isn't very flexible or scalable. Shift toward unbundling API management allows organizations to pick and choose the specific components they need. This way, they can create customized solutions that fit their requirements. However, this approach also comes with challenges, such as dealing with complex integrations and managing different vendors. Feel free to explore the full article for more in-depth insights! https://lnkd.in/eag23q3s #APIDesign #APILifecycle #APIManagement #APIs

5

3 kommenttia

I've built projects from ground up, from zero to production, new architecture, also took projects with crappy code and made it better I had at the beginning of my career ups and downs, but I guess after 5 years on commercial stuff you kinda become expert in the tech industry anyway. Worked with production stuff and high level stuff, clients trusted me because I delivered on time and at the highest quality. I wouldn't trust a junior with production stuff, at least not at the beginning.. A lot of money involved in business side anyway.. --------------------------------------------------------- Someone could learn most of the algo than pass the interview, but then what? I've talked with senior fellows of mine, solving quiz, assessments tests at home, are usually for juniors, or freshers. For seniors, it should be, past experience, portfolio, abstract high level technical discussions, communication skills, soft-skills, leading skills. I've joined companies for senior level where I didn't do quizzes or stupid algorithms at interviews and were the best companies that I've collaborated with, clients/stakeholders were happy and they always gave me more work. 😄

11

2 kommenttia

Software-Engineering-Bits #2 - The theme of today's post is: distributed systems. Event Modeling Anti-patterns, Oskar Dudycz 🔗 https://lnkd.in/dRSREurE ➡ A superb talk on Event Driven Architecture. I've read two books on this topic, so I thought I wouldn't be surprised. But it turned out, that the insights, the conclusions, and the way it was presented... it just impressed me. You can see Oskar's hard won project experience. (It's a pity the video is not available on YouTube though. I hope it won't be deleted from Confluent in the future). Light and Dark Side of the Event-Driven Design • Oskar Dudycz • Devoxx Poland 2021 🔗 https://lnkd.in/dZhMwCjX ➡ This video is a predecessor to the one above. Highly recommended if you haven't seen it yet. Software service granularity: Getting it right, Neal Ford and Mark Richards, Thoughtworks, 🔗 https://lnkd.in/d8nuQ2mb ➡ A podcast from Thoughtworks about modularity vs granularity. I liked it because it underscores that term "microservices" doesn't mean that the service has to be very small, and that lambdas can easily turn into "grains of sand" anti-pattern. Untangling Microservices, or Balancing Complexity in Distributed Systems, Vlad Khononov 🔗 https://lnkd.in/duXGyJdr ➡ The podcast from Thoughtworks reminded me of this outstanding article from Vlad Khononov. His concept of "Global vs Local complexity" (which is really a consequence of Tesler's Law) is very appealing and easy to use as an argument. More importantly, this concept/law works on every level of Software Design (from methods to systems). Real-world Engineering Challenges #8: Breaking up a Monolith 🔗 https://lnkd.in/dZB_Bqem ➡ "A deep dive into how Khan Academy took a 1 million-line Python monolith and split it into ~40 Go services in a more than 3 year-long project.". It's the kind of article that caused the explosion of Pragmatic Engineer's popularity. [Polish only] Boiling Frogs 2020 - Łukasz Szydło - DDD w systemach rozproszonych 🔗 https://lnkd.in/d2Gf7qX4 ➡ I watched it some time ago, but it kinda fits the theme of this post. I like it that it goes down to the code and describes problems that might result from the blind adoption of some popular application architectures. [Extra] The sensible defaults playbook - Thoughtworks 🔗 https://lnkd.in/dCqjH62Y (direct link: https://lnkd.in/dtyfR9gM ) ➡ Thoughtworks again. It's not related to distributed systems, but this guide has insightful and sensible (sic) advice on Software Engineering practices. Software-Engineering-Bits is my little knowledge sharing initiative. I share resources I find interesting and valuable. #distributedsystems #softwaredesign #newsletter

3

Interesting talk. https://lnkd.in/dtqRSRg2 I can also recommend https://lnkd.in/d-QmneSK if it is a subject of interest for you:-) (thanks Jonatan Bech Ingemann Frausing for link)

4

Docky Mc Proxy? What at first sounds like a new burger creation from a famous fast food brand is actually a small open source tool that could save the day for many software developers. In our blog post we talk about the annoying little problems that the tool developed by Keno solves. And for us as developers, it's not just about creativity and innovation, but also about the importance of sharing and open source software development. Click here to read the full blog post: https://lnkd.in/eBNRx-P9 And here are our current open source projects on GitHub: https://github.com/unit214 Follow us to make sure you don't miss a thing! #unit214 #dockymcproxy #opensource #munich

14

1 kommentti

Knowledge Sharing: Day 22 Breaking change if you are planning to upgrade your compileSDK to Android 15 or higher 📢 If you use Kotlin's list.removeFirst() or list.removeLast() extensions in your Android app, then, after bumping compileSdk to 35, your app will crash at runtime on older Android versions. #android15 #android #behaviour #development Kaara

34

3 kommenttia

🌟 Join Us in Shaping a New 3D Creation Platform – Equity Opportunity! #Finland 𝐇𝐞𝐥𝐥𝐨 𝐋𝐢𝐧𝐤𝐞𝐝𝐈𝐧 𝐂𝐨𝐦𝐦𝐮𝐧𝐢𝐭𝐲! I’m spearheading a project that combines innovative 3D technology with smart business strategies. With our MVP already 65% complete, we’re looking to accelerate development and prepare for launch. I’m seeking passionate individuals who are excited to help take this project to the next level from its early stages. ### 𝐖𝐡𝐨 𝐂𝐚𝐧 𝐉𝐨𝐢𝐧: Are you interested in being part of a project from its inception? Whether your strengths lie in business, 3D design, or innovation, there’s a place for you here. We’re especially open to those looking to contribute part-time while making significant impacts. ### 𝐒𝐤𝐢𝐥𝐥𝐬 𝐖𝐞 𝐀𝐫𝐞 𝐋𝐨𝐨𝐤𝐢𝐧𝐠 𝐅𝐨𝐫: - 𝐋𝐚𝐧𝐠𝐮𝐚𝐠𝐞 𝐒𝐤𝐢𝐥𝐥𝐬: Fluency in Finnish is a plus, as we aim to initially make an impact in Finnish-speaking markets. - 𝐁𝐮𝐬𝐢𝐧𝐞𝐬𝐬 𝐄𝐱𝐩𝐞𝐫𝐭𝐢𝐬𝐞: Background in business development, strategic planning, or sales. - 𝐂𝐫𝐞𝐚𝐭𝐢𝐯𝐞 𝐓𝐚𝐥𝐞𝐧𝐭: 3D artists and designers ready to produce engaging visuals. - 𝐂𝐨𝐦𝐦𝐮𝐧𝐢𝐜𝐚𝐭𝐢𝐨𝐧 𝐒𝐤𝐢𝐥𝐥𝐬: Strong communication is key for teamwork and project development. - 𝐀𝐝𝐚𝐩𝐭𝐚𝐛𝐢𝐥𝐢𝐭𝐲 𝐚𝐧𝐝 𝐃𝐫𝐢𝐯𝐞: Excited to engage with a startup and contribute to its growth. - 𝐋𝐞𝐚𝐝𝐞𝐫𝐬𝐡𝐢𝐩 𝐐𝐮𝐚𝐥𝐢𝐭𝐢𝐞𝐬: Ability to lead and inspire others as part of our early team. ### Our Vision: - 𝐈𝐧𝐧𝐨𝐯𝐚𝐭𝐢𝐨𝐧 𝐚𝐭 𝐭𝐡𝐞 𝐅𝐨𝐫𝐞𝐟𝐫𝐨𝐧𝐭: We’re developing tools that will simplify and enhance 3D content creation, aimed at revolutionizing industries like gaming, education, and marketing. - 𝐄𝐱𝐩𝐚𝐧𝐬𝐢𝐯𝐞 𝐈𝐦𝐩𝐚𝐜𝐭: Our goal is to transform how these sectors interact with digital content, providing innovative solutions. This opportunity is not just about joining a new project; it’s about having the chance to shape its direction and growth. As an early collaborator, you’ll be eligible for an equity stake, reflecting the value and trust we place in our foundational team members. 📩 𝐖𝐚𝐧𝐭 𝐭𝐨 𝐋𝐞𝐚𝐫𝐧 𝐌𝐨𝐫𝐞? Drop me a direct message, comment below, or send an email to [email protected] to discuss how we can work together. Let’s build something transformative together! ✨ #StartupJourney #3DTechnology #EquityOpportunity #CoFoundersNeeded #TechStartup #CreativeCollaboration #PartTimeOpportunity

1

Service as software First software ate hardware and now I would agree that there is so much potential to marry services with software. An outcome based model where software developer has a skin in the game and measurable output. Why now? Agentic workflows in repetitive tasks of niche domains makes it possible. This is also a fundamentally different business model, risks, and TAM. Having spent last 10 days in the valley, I must say the acceptance isn’t there (yet) for this concept. People are still building software tools by default and don’t want to mix it with services. Well, just like on-Prem shifted to SaaS and was debated. Are we at a similar moment in time? This is a good paper imho https://lnkd.in/gPfEMVMe What do you think?

12

5 kommenttia

About 6 months ago, my role changed. As a result, coding is no longer a part of my day job. This has been challenging for me because I have come to identify myself as a coder. Unfortunately, this just hasn't been true for the past several months.   I want to get back into the habit of coding, and this is my challenge to do it. For the next few weeks, I am going to post a few of the code repositories I worked on in my last role. My hope is that this will create a habit of talking about and interacting with code, which will hopefully inspire me to write new code.   This first project I'm sharing is the last project I worked on in my previous role. It is a script that uses the Meraki APIs to pull the allowed clients lists from Meraki networks and then generates an Excel spreadsheet report from the results with columns for the MAC address of the client, IP address of the client, the date and time the client last connected, whether the client is currently online or offline, and the name of the network the client is connected to. I wrote this script because a Meraki customer requested a way to quickly generate reports that showed the last time a client from the network allow list connected to the network so that they could remove clients from the list with extended periods of inactivity. While creating this script, I learned that Meraki only saves the data of clients who have connected to the network in the last month. This makes it difficult to keep track of clients who have not connected to the network in an extended amount of time. I also learned that some of the libraries I used in this script needed to be updated to newer versions in order to work with Python 3.12 😅. If I were to add new features to this project, I would look for a way to keep track of clients for longer than the 31 day limit that currently exists. To do this, I think I would need to create a database that stores the activity of the clients periodically so that I am not completely reliant on the Meraki dashboard APIs and their limitations. You can find the source code of the project on my GitHub here (https://lnkd.in/eU7E9Nen). Feel free to download it and test it yourself if you're a Meraki user. Let me know what you think and what you would like from the script!

51

4 kommenttia

2024-12-30: Making Changes in Established Softwares is a Slow Process. As Large amount of Work is already done very less People have clear Picture about & a Long Product Roadmap is already in place with Plans about large number of Tiny Features which need to be included in next Release of Software

🚨 The Peak Hackathon Scandal: A Wake-Up Call for Accountability 🚨 The Peak Hackathon scammers have left many students feeling betrayed and financially burdened which was in partnership with Devfolio. Here's what unfolded: -> Frequent Date Changes: The organizers repeatedly altered event dates, causing confusion and impacting students' schedules, financial planning, and mental well-being. -> Lack of Transparency: Poor communication and a failure to address participants’ concerns eroded trust in the hackathon and its organizers. -> Financial Losses: Many students invested in travel and accommodations for Dharamshala, only to find themselves stranded after the abrupt date changes. -> Impact on the Ecosystem: Such mismanagement not only affects individuals but undermines the credibility of hackathons in India. Transparency and accountability are critical to maintaining the trust of the developer community. 💬 Call to Action: We must unite as a community to ensure fairness and justice: ✅ Demand reimbursements for affected participants. ✅ Raise awareness to prevent others from falling victim to similar scams. ✅ Advocate for higher standards in event organization. 📢 Let’s amplify this issue and support those impacted. Devfolio must take down this asap. Uniswap Aptos Foundation Solana Foundation Solana Labs India Blockchain Week (IBW) Conference Polygon Labs #PeakScam #Hackathons #Accountability #Transparency #Reimbursement

72

2 kommenttia