Guilherme da Silva Almeida

🚀 Happy Workers Day! 🎉 Did you know that today is a holiday in Portugal? 🇵🇹 While enjoying some time off, I'm diving into TypeScript on Codewars. 💻 Here's a quick tip: revisiting the basics is key for any developer's growth. Strengthening your foundation ensures smoother progress in complex concepts. So, whether you're relaxing or coding today, remember the value of building on strong fundamentals! #typescript #coding #holidaylearning

6

Hello Developers 🚀 🏖️ I've been on vacation this past week, hence the lack of posts from me. 💬 This is something I really want to impose on social networks (just linkedin for now) because I want to create the habit of wanting to share with the community positively, and of course learn from all of you. 💥 "Together we are stronger" 🌍 That's what I believe in, and that's why a few years ago I started a group to share experiences and knowledge. And that's exactly why I started with other mates the freeCodeCamp Lisbon. 🤝 I met some great people that I'll carry with me for life, namely Luís Lota, João Petinga and many others that I'll keep with me forever. 🫠 I remember feeling stagnant at the time. ☕ So I started doing Saturday events in a café in Lisbon, and I even did events in the middle of the mall... 🌐 Later, we got partnerships with Connect Digital (former Edge Portugal). And we kept evolving over time, until I felt really happy with what I was doing. 📝 And maybe I'll share the not-so-good part of all this in another post. 😊 But I do know that the feeling of community and sharing is something that makes me happy and fulfilled. Should I go back to that? 💬 Leave a comment, share with me what you think and what I can do to improve. If you know me well, go ahead and expose me without fear. 🔗 You can find out more about me at https://pedropcruz.pt #freecodecamp #techcommunity #community #it #frontend #devjourney #developer #coding #programmer #sharingiscaring #knowledge

3

1 comentário

Just saw some Brazilian dev influencer giving tips to beginners: they should avoid PHP and React, but learn C, Ruby(?), HTML and CSS(?????). I'm wondering how this person will build a modern website without knowing JS.

6

3 comentários

Here is a new framework to build your frontend: https://lnkd.in/dXhYUNYr After months of working on this, it is finally out. The XSO COM is a crazy one, with all the features we are used to seeing in React, Vue, Svelte, and more... But it is pure JavaScript with no compilation! And with support to run directly in HTML. I hope you enjoy and try to play with this. Any feedback or improvement is very welcome. #javascript #react #vue #svelte #framework #frontend

6

Airbnb prices are wrong. A few months ago, I published an article about UX responsibilities for a front-end developer. After looking back, I noticed that one of the topics didn't receive enough attention: how to render prices. So I went back to work and I investigated the international conventions and evaluated dozens of large companies from various business sectors like Apple, Airbnb, Air Canada, Amazon, Booking.com, British Airways, Delta Airline, Nike, Walmart, Uber, and Zara. I extracted the best practices in a new article (link in the first comment ⬇️). It also includes how to do it in JavaScript. You will see it becomes so easy to code a price supporting all the languages and the currencies! I also added a small demo.

9

1 comentário

The release of Node.js 22 is available now! ​​Highlights in Node.js 22 include require()ing ESM graphs, WebSocket client, updates of the V8 JavaScript engine, and more! #nodejs #websocket #javascript

14

I see some posts complaining about Javascript missing a killer framework. Here are my takes about this. ⬇ Keep reading ⬇ I have three main arguments to explain this: 👉 The most relevant in my opinion, is that Node.js started from the beginning with a great package manager. Take PHP for example: if Composer (http://getcomposer.org) had existed in the early years, Laravel might not have become as successful. The ability to easily add components as needed (and only when needed) would have significantly reduced the demand for a large, all-encompassing framework. 👉 Node.js was released 15 years after the second-newest language on that list. Dust may need to settle first. 👉 JavaScript wasn't designed as a general-purpose language, and only recently has it been considered as such. Maybe the JS world just doesn't need a killer framework. Switching components as needed, adapting to new requirements with ease, may just be the stronger argument for using it. -- This was originally posted in my 𝕏 profile, follow me there for more takes like this! https://x.com/josecanciani

3

1 comentário

Even time zone is not a problem when we listen to Tadeu's Light Talk. By the way, from sunny Brazil. At least look at this vibe in the photo 😎 This time he talked about "User perception in software development" 👉🏻 User perception and its importance in the context of software development: it's the perception a user builds about an application. It contributes to user engagement and builds brand loyalty, improving ROI. 👉🏻 Different approaches to understanding user needs and expectations: the approaches used depend on the context in which the company is involved. They guarantee a product that meets user expectations. 👉🏻 Strategies used by companies to improve user perception: It's about making users feel good about themselves, their choices, and their interaction with the product.

8

There is a very constructive conversation happening around innovation vs legacy for node.js right now. The debate which has been getting alot of community input is around navigating the delicate balance between maintaining legacy code and fostering ecosystem evolution for node.js. Most software engineer's who use node are aware that over the past few years there have been multiple occasions where dependencies and long standing bugs go unaddressed due to the fear of breaking modules. On the other-hand there has also been an increase in adoption of new runtimes like Bun.sh, however I believe eventually when mass adoption of an open source runtime takes place, you run into the same issue that node.js does. Some interesting data we've collected over the years by monitoring meta data for javascript repos: - Organizations have longer package upgrade cycles due to not being able to upgrade their run times without major breaking changes. On average this timeline is around 8-10 months for upgrading runtime versions from previous to current. In enterprises this time line is even longer. - Both serverless and containerized Cloud infrastructure lags behind in runtime adoption of latest node versions due to dependent SDK's facing breaking changes often. - When dependencies start to get in the way of abandoned packages then forking and fixing is the path often taken. - Vulnerability patching in packages is usually the catalyst for runtime upgrades - Most organizations are unaware of their deeply nested dependencies when adopting new packages, npm and other package managers make it easy to install the packages but make it hard to understand the implications of its addition.

11

Application Update! Exciting news for jessepiccione.info - the user interface has been refreshed with custom CSS animations and transformations. The result? A more engaging and visually appealing experience for our users. Check it out now! #UIupdate #CSSanimations #WebDesign

9

2 comentários

Ever written Node.js code that feels like it's stuck in a loop? You send an API request and wait for a response, but your program just keeps running along without a clear end in sight. This asynchronous dance can be a real head-scratcher, especially when you need tasks to finish within a specific timeframe. Before jumping on solutions let's understand "Why do we need tasks to finish within a specific timeframe?" 𝗣𝗿𝗲𝘃𝗲𝗻𝘁 𝗕𝗹𝗼𝗰𝗸𝗶𝗻𝗴: Without deadlines, your program might wait indefinitely for a slow response, blocking other tasks from executing. 𝗨𝘀𝗲𝗿 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲: If responses take too long, users experience delays and frustration. Setting deadlines ensures a more responsive application. 𝗘𝗿𝗿𝗼𝗿 𝗛𝗮𝗻𝗱𝗹𝗶𝗻𝗴: Timeouts can trigger errors, alerting you to potential issues with external services like APIs. 𝗣𝗿𝗲𝗱𝗶𝗰𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆: Deadlines help maintain control over your code's execution flow, making it easier to predict behaviour and troubleshoot problems. Node.js shines with its asynchronous nature, handling multiple tasks concurrently for optimal efficiency. But when dealing with external services like APIs, we often need to guarantee a response within a certain time limit. Think of fetching user data – you need that information before proceeding, but the API might take its sweet time responding. Feeling stuck in coding limbo? Not anymore! Here are some proven tools you can rely on in Node.js to establish order in the chaos of asynchronous tasks: 𝟭. 𝗣𝗿𝗼𝗺𝗶𝘀𝗲𝘀 𝘄𝗶𝘁𝗵 𝗧𝗶𝗺𝗲𝗼𝘂𝘁𝘀: Promises allow you to chain asynchronous operations, but what happens if one gets hung up? We can leverage timeouts within promises. If the operation doesn't complete within the set timeframe, an error is thrown, preventing your code from getting stuck. 𝟮. 𝗔𝘀𝘆𝗻𝗰/𝗔𝘄𝗮𝗶𝘁 𝘄𝗶𝘁𝗵 𝗧𝗶𝗺𝗲𝗼𝘂𝘁𝘀: Similar to promises, you can pair setTimeout with async/await functions to define a maximum wait time for asynchronous operations. 𝟯. 𝗧𝗵𝗶𝗿𝗱-𝗣𝗮𝗿𝘁𝘆 𝗟𝗶𝗯𝗿𝗮𝗿𝗶𝗲𝘀: Libraries like bluebird or async offer even more control over asynchronous operations. These tools provide functionalities like timeouts and cancellation capabilities, allowing for fine-tuned management. By implementing deadlines for asynchronous operations, you ensure your Node.js applications run smoothly and avoid unexpected delays. See the attached code snippet of Promises with Timeouts. #javascript #NodeJS #AsynchronousProgramming #APIs #codingtips

18

My work to make the OpenAI API (built on Nelson Ferraz's OpenAPI::Client::OpenAI module) is going well. I now have working example of transcribing audio using OpenAI's whisper-1 model.[1] Using a 7.7M file which is about 16 minutes long, the API call takes about 45 seconds to run and costs $0.10 USD to transcribe. The resulting output has 2,702 words and seems accurate. Next step is using an instruct model to transcribe the output. Fortunately, we already have working examples of this. Instruct models tend to be more correct in their output, following well-written prompts carefully. Anecdotally, they may have smaller context windows because they're not about remembering a long conversation. Think about the ROI on this. The transcription and final output will cost about 10 cents and take a couple of minutes. You'll still need someone to review it. However, think of the relatively thankless task of taking meeting minutes and producing a BLUF email for the company. Hours of expensive human time become minutes of cheap AI time. When building AI apps, OpenAPI::Client::OpenAI should be thought of as a "low-level" module, similar to DBIx::Class. It should not be used directly in your code, but hidden behind an abstraction layer. Do not use it directly. I tell my clients that their initial work with AI should be a tactical "top-down mandate/bottom-up implementation." This gives them the ability to start learning how AI can be used in different parts of their organization, given that marketing, HR, IT, and other departments all have different needs. Part of this tactical approach is learning how to build AI data pipelines. With OpenAI publishing their OpenAPI spec, and with Perl using that, we can bring much of the power of enterprise-level AI needs to companies using Perl. It's been far too long that Perl has languished in the AI space. Next, I need to investigate doing this with Gemini and/or Claude. Thanks also to Avishai "Veesh" Goldman for his help with this. The OpenAPI::Client::OpenAPI module is built on top of Mojo tools and frankly, I don't know them very well. This is the beauty of open source. People will diverse skills working towards a common goal can create great things. #AI #AIAdoption #LLMs #OpenAI #OpenAPI #ChatGPT 1.

14

Another useful update coming to the App Store Connect app (iOS / iPadOS)! A new feature is on its way: you'll soon be able to share your app directly to social media platforms. Automatically generated assets in various layouts will accompany a direct link to your app, making promotion easier than ever. (Spotify's social share way of promoting your apps) #iOS18 #AppStoreConnect #SocialShare #AppStore

87

3 comentários

*This post may be triggering Typescript is unnecessary and a big old waste of time It's unnecessary because, if your frontend works then you've got types under control. It's a big old waste of time because it's a whole lotta extra work for just a little bit of return on investment. #software #juniordeveloper

6

7 comentários

It's exciting that Ruby on Rails is back on the map with version 7, which includes Hotwire and Turbo. The JavaScript ecosystem, while vibrant, has often been criticized for its fragmentation and the constant influx of new tools and frameworks that add complexity to development. DHH (David Heinemeier Hansson), the creator of Ruby on Rails, emphasized that modern web development could benefit from reducing this complexity. With Hotwire and Turbo, Rails aims to simplify the development process by minimizing the need for extensive JavaScript toolchains, bundling, and transpiling. This approach contrasts with the chaotic nature of the JavaScript ecosystem, which frequently introduces new libraries and frameworks. Thus, while React currently dominates, the fragmented nature of the JavaScript ecosystem suggests it could eventually be replaced by new innovations. Rails, on the other hand, aims to streamline development without the added complexity of modern JavaScript tools. This is why I would like to lean more toward Ruby on Rails over the next years versus learning several JavaScript frameworks.

1

💥 𝗔 𝗰𝗼𝗺𝗺𝗼𝗻 𝗧𝘆𝗽𝗲𝘀𝗰𝗿𝗶𝗽𝘁 𝗽𝗶𝘁𝗳𝗮𝗹𝗹 💥 Defining a new type for an API response is a very common and useful practice in our Typescript projects. What many developers (myself included) forget about that approach is, that this only allows us to use the response data properly and typed inside our code. But it doesn't make sure, that the data is actually correct and satisfies our type definition. When something in the response changes, we get to know it when using the data, which often can be too late. I wrote a blog post about that topic and show you one way on how to fix that problem using schema validation! 👇 https://lnkd.in/eV2Wdw4Z Have fun!

6

1 comentário

What do the top 1% of software engineers do that the other 99% do not? To be a bit pedantic, there is only a marginal difference between a 99th-percentile software engineer and 98th-percentile one. In my view, the path to mastery of software craftsmanship consists of several levels. Level 1: Writing simple code A surprising number of salaried software engineers actually struggle to write working code for anything but the simplest features. It requires a baseline of talent and motivation to progress beyond this. Level 2: Solving advanced problems At this level, a software engineer is able to tackle basically any problem coming their way. The solution won't always be pretty, and it will probably include a few hacks along the way, but it will get the job done. These guys can be good to have on your team to get new features quickly out the door. The drawback is that the technical debt will pile up. Level 3: Writing elegant code With some experience, the more talented software engineers will eventually be able to write elegant code that is maintainable, testable and production-worthy. Sometimes they run the risk of over-engineering and taking too long to finish relatively simple task. These types of engineers are good to have on your team when you have a mature, mission-critical system. Level 4: Writing simple code At this point, we come full circle. The best software engineers know how to reduce complex problems to something simple. When you read their code, you'd think “I could have written that”. That only comes from years of experience and an uncanny ability to see the forest for the trees. If you're familiar with the “midwit meme”, it illustrates things nicely: #javascript #reactjs #nextjs #mern #hooks #coding #ReactHookForm #NextJS #WebDevelopment #JavaScript #FrontendDevelopment #Forms #DeveloperTips #ReactJS #CodeTutorial #Programming #TechArticles #WebDevTips #javascript #angular #react #vue #CodingLife #Programming #JavaScript #WebDevelopment #FrontEndDev #FullStackDeveloper #SoftwareEngineering #CodeNewbie #TechCommunity #CodeIsLife #DeveloperCommunity #LearnToCode #JavaScriptDeveloper #CodeEveryday #ProgrammingLanguages #CodeChallenge #TechSkills #SoftwareDeveloper #CodeQuality #DevLife #github #git

3

I am taking on #React with #TailwindCSS for styling, already grasping the main concepts. So I recreated my thoughts and goals app, but this time with more emphasis on #Responsive #Design, there are still some bugs that needs fixing, but I am happy with this start toward Front-End development with #React. I learned about components, states, and effects so far. #SelfTaught

2

The Three Cs of Refactoring: Concision, Consistency, and Clarity 1. Concise code essentially lowers the cognitive load for developers. Even with the great design patterns, when it starts to get verbose, it makes people space out. 2. Consistency gives a good bit of educated guess and it helps make decisions about where to place a certain component in your project. I cannot imagine managing kernel code, for example, without consistency as the lines of code for that are over 15M. In this regard, convention in a team outweighs the importance of all the buzzes of architecture although it is good to talk people into what's good and what's bad. 3. Clarity is the most ambiguous, subjective, and relative yet important. Unlike concision and consistency which are, simply by definition, enough to claim their importance since the first one is about "how short" and the other being "how uniform", claiming one to be clear often comes with a lot of different aspects. For example, when people start learning programming, they may find Python or Javascript to be the one with which they can "clearly" express what they want. But when the system requires to allow business logic changes, the type system will save you a lot and some of them may gravitate more towards typed language because you can "clearly" locate where to change. Ultimately, clarity is pinned on your experience, the conventions you follow, and your programming expertise.

5