#back end

[xpc-web-dev]

100 days of code: Day 2 and Day 3

(23/02/2023)

Day 2

Yesterday I continued my studies through MDN and tested this example.

Of course I didn't understand almost anything, but I found it interesting. But after that I went to see the Odin one and I found it more accepted to first do its fundamentals (and it references mdn articles) and then see where I follow.

Day 3

Today I finished odin fundamentals 1 and these were the assignments

Today was a tiring day and I really didn't want to study.

BUT besides being obsessed with not breaking the sequence of green squares on my github , I also remembered that I need to do what has to be done even when I'm tired. So I studied this and other tasks.

And you, how are your studies?

I wish you a great night/day/Friday, take care of your mental health, don't be stupid with people on the internet just because there's a screen protecting you, and drink water.

[why-tap]

Interested in learning Front-End Development?

[eribytevt]

I have created the schedule V2 page, aka this part of that diagram I made

The CRUD service and DB took about an hour, the frontend took about 4 hours because man I hate front end. On the brightside I think it also works on whatever timezone ur on

Also I learned that calling an HTTP address from an HTTPS address is "Bad" and "susceptable to man in the middle attacks" and "most browsers block it" so I panic added HTTPS to the CRUD endpoint

[ganralnet]

Software development / Digital marketing Agency.

General.net the leader in Dubai and Egypt for services Web/App Design & Development services and the best Marketing Services.

                        With us you can Build…Market…Compete

Our company specializes in providing comprehensive software solutions for businesses and excel in today's digital landscape and And many digital marketing services.

Building robust social media accounts, creating impactful advertising campaigns, developing cutting-edge mobile applications, and designing engaging websites.

The most important services we provide:

Social Media Marketing

Search Engine Optimization

Search Engine Marketing

Google Ads

Paid Social Marketing

Influencer Marketing

Email Marketing

Branding

Graphic Design

Website Development

Web Design

Mobile App Development

Mobile App Design

[priya-joshi]

My Perspective on Distinguishing Between Full Stack Developers and Web Developers

I can’t help but go back to my own experience as a web developer as I sit down to write about the difference between full stack developers and web developers. This subject has a special meaning to me since it captures the essence of navigating this fast-paced industry. In order to better appreciate the contrasts between these two jobs, let’s set out on a voyage, and I’ll share my viewpoint and experiences along the way.

We frequently mix the terms “full stack developer” and “web developer” while discussing web development. They stand for several jobs, each with their own set of tasks and abilities. Whether you’re an experienced developer, a newcomer in the industry, or someone pursuing a career in technology, it’s vital to comprehend these contrasts.

Defining Full Stack Developers and Web Developers

Developers who work on the complete stack: Let’s start by defining a full stack developer. In terms of web development, a full stack developer is essentially a jack of all crafts. Both front-end and back-end technologies are familiar to them. This implies that they are capable of managing databases and server-side functionality in addition to designing the user interface. They are essentially the Swiss Army tools of web development.

Web Developers: known as front-end developers — concentrate mostly on the client side of web development. They are masters in using HTML, CSS, and JavaScript to create stunning and engaging user interfaces. Their main objective is to provide a smooth and visually pleasing user experience on a website.

I had a basic comprehension of these jobs when I first started working as a web developer. Like many novices, I mistakenly believed that web programming was solely about producing visually stunning websites. But I quickly understood there was much more to it.

Common Ground: Overlapping Skills

It’s important to acknowledge the areas of overlap between web developers and full stack developers before we get into their distinctions. A solid foundation in front-end development is necessary for both professions. HTML, CSS, and JavaScript proficiency are essential. These languages are your building blocks whether you’re creating a user interface or incorporating sophisticated capabilities.

These front-end abilities were the start of my adventure. I devoted endless hours to polishing my HTML structures, honing my CSS stylesheets, and exploring JavaScript’s potential as an interactive language. These abilities laid the foundation for my profession and are still crucial today.

Delving into Full Stack Development

Let’s now explore full stack development, where the distinctions are more apparent. In addition to being experts in front-end technologies, full stack developers are also knowledgeable in back-end technologies. This covers database management as well as server-side programming languages like Python, Ruby, or Node.js.

Making the switch to back-end development was a turning point for me. Working with databases and server logic first made me feel uneasy. I took the challenge, though, and began studying server-side languages and databases. Even if things weren’t always easy, every challenge I overcame helped me become a better developer.

Web Development: Focusing on the Front End

Web developers, on the other hand, focus on the front end. Their area of expertise is designing captivating, engaging user interfaces. They take great care in website design, making sure that it is aesthetically pleasing, responsive, and user-friendly.

I still clearly recall my first front-end-focused web programming project. Making an interactive and practical design come to life was thrilling. Web developers enjoy the particular high of witnessing a beautifully designed website in use.

Bridging the Gap: The Versatility of Full Stack Developers

The capacity to integrate front-end and back-end development is one of the defining traits of full stack engineers. This adaptability is revolutionary in the tech sector. Full stack developers are able to handle all aspects of development, taking a project from inception to conclusion.

Being a full stack developer has provided me with access to a variety of projects. I’ve had the honor of working on anything from data-driven applications to e-commerce websites. This versatility has improved my skill set and given me the ability to take on a variety of difficulties.

My Personal Journey

I can’t help but thank the mentors, classes, and resources that have molded my perspective as I consider my career as a developer. Participating in coding groups, taking full stack developer courses provided by ACTE Institute, and learning from seasoned developers have all been extremely beneficial to my development.

Realizing that no one becomes a full stack developer or web developer over night is essential. It is a path of ongoing learning and development. And keep in mind that each person’s journey is distinctive, formed by their experiences and decisions.

The Ever-Changing Tech Landscape

The only thing that is consistent in the tech sector is change. Both web developers and full stack developers need to keep up with the latest trends and technology. Adaptability is essential, from the emergence of new programming languages to the development of front-end frameworks.

I’ve seen firsthand how quickly tools and techniques for web development have advanced. In this always changing sector, adapting to change and remaining curious have been essential.

In conclusion, anyone navigating the IT sector needs to be aware of the differences between full stack engineers and web developers. Each role has its own advantages and difficulties. Remember that your path as a developer is an ongoing discovery whether you decide to focus on one or embrace the variety of the other.

[projectbatman193]

This is the very first program I've coded, and it's basically a D20 😊

[thecoolergoj]

As a programmer, I find myself yelling at servers quite often

[dbajaj48]

From Startup to Scale: A No-Nonsense Guide for Real-World Growth

Let's be real, choosing a tech stack is like picking what to eat at an all-inclusive resort. There are so many options, and while it might seem tempting to just pile everything onto your plate, you know that's a recipe for disaster. Similarly, you can't just pick every trendy tool out there for your business. If you do, you might end up with a bloated, dysfunctional mess that doesn't do anything particularly well.

The goal here is to help you pick the right tech stack for your business, allowing it to scale efficiently without giving you heartburn. Whether you're a startup just figuring things out or an enterprise looking to streamline, this guide is for you.

The Tech Stack Basics: What Are We Even Talking About?

Let's get one thing straight: a "tech stack" is not a literal pile of technology (though that would be cool). It's the tools, programming languages, and frameworks your business uses to build and run applications. Think of it as your company's digital toolbox. And just like with real tools, you don't use a chainsaw to assemble IKEA furniture—so you need to pick the right tools for the job.

Your tech stack is always divided into two parts

Front-end

This is the stuff your customers see and interact with. It's like the shiny chrome on a sports car—it looks nice, but if it doesn't perform well, people will quickly notice.

Common tools: React, Vue.js, HTML, CSS

Back-end

This is the engine of your operation. The invisible stuff powers your business and keeps everything running smoothly.

Common tools: Node.js, Python, Ruby on Rails

But enough with the definitions—let's get into how you can pick the right tech stack for your business. Spoiler alert: there's no one-size-fits-all answer.

Start with your Business needs (not your cousin's tips)

It's tempting to go with whatever your cousin or that random guy on LinkedIn is raving about, but let's be honest—just because a tech tool works for them doesn't mean it's the right fit for you. Would you wear your cousin's jeans? No. So don't copy their tech stack, either.

First things first: what are your actual business needs? Are you a startup trying to build the next Uber for cat-sitting (we've all thought about it), or are you an established company looking to streamline operations? Here's what you need to consider

Your Growth Goals

Are you planning for world domination or just happy to expand locally for now? The tech stack you choose should support both your short-term needs and long-term aspirations.

Your Industry

What industry are you in? If you're in e-commerce, you'll want tools that make online transactions easy and secure. In healthcare, you need technologies that comply with privacy laws like HIPAA. And if you're in finance, good luck with that.

Your Team's Skillset

Who will be using this tech stack? If your team is fluent in Python, don't make them suddenly learn Ruby on Rails unless you want a mutiny on your hands. Pick tools that fit your team's existing skillset—or be prepared to invest in serious training.

Think About Scalability (Because Growth Happens Faster Than You Think)

One minute, you're a cozy little startup, and the next thing you know, your app has gone viral, and your server has crashed more times than you can count. Growth is exciting, but if your tech stack can't handle it, you will have problems. Big ones. Scalability is the magic word here. You need a tech stack that evolve with your business, not one that buckles under pressure. When considering scalability, here is what you need to know

Cloud-Based Solutions

Hosting your infrastructure on cloud platforms like AWS or Microsoft Azure can give you the flexibility to scale up or down based on demand. It's like adding more chairs to the table when unexpected guests arrive—except, in this case, thousands of users are hitting your platform all at once.

Performance

Some programming languages and frameworks are great for large-scale operations. If you're dealing with a high volume of transactions or users, choose something built for speed. Node.js, for example, is known for handling multiple connections simultaneously, making it great for real-time applications like chat apps or online games.

Database Choices

Your database is where all the magic (or chaos) happens. For startups, a simple database like MySQL or PostgreSQL might be enough. Still, as you grow, you'll need something that can handle larger data loads—think MongoDB for non-relational data or Oracle for enterprise solutions.

Don't Forget About Integration (Because No One Likes a Silo)

Ever tried to put together a jigsaw puzzle where none of the pieces fit? That's what it feels like when your tech stack doesn't integrate well with your existing systems. And trust me, nothing grinds productivity to a halt faster than a bunch of disjointed tools that refuse to work together.

When choosing your tech stack, consider how it will integrate with the tools you already use. Does your CRM need to interact with your email marketing platform? Are you planning on syncing your sales data with your accounting software? The right integrations can save you hours of manual work—and possibly your sanity.

Here's the secret sauce: APIs (Application Programming Interfaces). They're like the universal translators of the tech world, helping different tools communicate with each other. When evaluating a new tool, check if it has an API that plays nicely with your other systems.

Example: HubSpot is a great all-in-one marketing platform that integrates with dozens of other tools. HubSpot's smooth integrations can make life much easier if you're already using a CRM or email marketing service.

Budgeting for your Tech Stack (Spoiler Alert: It's going to cost way more than you Thought)

Let's talk about money. Every business has a budget—unless you're backed by a billionaire who's just in it for the fun, in which case, please introduce me. For the rest of the world, picking a tech stack means balancing performance, scalability, and cost. You don't want to go broke paying for shiny new tools that only make things marginally better. Here's the deal: open-source technologies like React or Node.js are great because they're free. Yes, free! But there's a catch-free doesn't always mean zero cost. You must still consider maintenance, updates, and the cost of developers who can work with these tools.

The Airbnb Approach for cost saving

Take Airbnb, for example. The company used Ruby on Rails for its web platform in its early days. Rail is an open-source framework that helped Airbnb get started without sinking too much money into licensing fees. As the business grew, the team heavily invested in infrastructure and switched to React for the front end to handle the scaling needs of their user base. The lesson here? Start small with cost-effective solutions, and be prepared to invest in your tech stack as you grow.

Now, let's talk about enterprise-level tools. These often come with hefty licensing fees. If you're considering Salesforce or Oracle, know you're entering premium territory. These tools provide advanced features, but they come at a price. If you're a small business, this might not make sense yet—but for larger operations, these solutions can pay off in the long run by streamlining processes and reducing human error.

Shopify's Early Tech Stack Struggles

Shopify initially relied on PHP and MySQL to power its platform, which worked fine when serving smaller e-commerce stores. But as it scaled, it ran into performance issues with large traffic spikes. Shopify then transitioned to Ruby on Rails and focused on horizontal scaling to handle requests more efficiently. The learning is that budgeting for future growth and tech debt will save you headaches later.

Make sure your Stack is secure (or pay the price later)

We've all seen those scary headlines: "Massive Data Breach Exposes Millions of User Accounts." No one wants to be the next headline, especially when the damage to your reputation (and your wallet) can be severe. Security must stick in your mind when choosing a tech stack.

Some technologies are more secure than others. For instance, large enterprises often favor Java for its robust security features. Similarly, Python has excellent libraries for encryption and data security.

But security isn't just about picking a tool; it's about implementing the right practices. Ensure your developers regularly update your tech stack, apply security patches, and follow best practices like two-factor authentication (2FA) and encryption for sensitive data.

Target's Massive Data Breach

Remember Target's massive data breach in 2013? Hackers were able to access 40 million credit card numbers just because of a vulnerability in their network access system. They may have avoided that disaster with more secure protocols and better monitoring practices. Don't be like Target.

Keep an Eye on Trends, But Don't Chase Every Shiny New Tool

The tech world is always changing. Every week, a new "next big thing" promises to revolutionize how we do business. Blockchain, quantum computing, AI, Web3—it's easy to feel FOMO when you hear about these groundbreaking technologies. But just because something is trendy doesn't mean it's the right fit for your business.

The Slack Boom

Look at Slack. It became the go-to communication tool almost overnight, pushing out older tools like email and Skype. It was not only because it was shiny and new. It was because it effectively solved a pain point for businesses, making communication faster and more collaborative. However, not every tool has a lasting impact, like Slack, so pick your tech wisely.

That said, you want to pay attention to trends. In an industry where innovation is key, like fintech or healthcare, you may need to adopt new technologies faster than others to stay competitive. The trick is to strike a balance—stay current without feeling like you must overhaul your tech stack every six months.

The Talent Factor (because even the best Tech is useless without the right people)

You could have the most advanced, scalable, and secure tech stack on the planet, but you're sunk if no one on your team knows how to use it. When choosing your tech stack, consider the talent pool. Can your current developers work with this stack? If not, are you willing to invest in training or hire new developers specializing in those tools?

Netflix's Engineering Talent Strategy

Everybody knows it: Netflix hires the best engineering talent to manage its complex tech stack, which includes everything from Java and Node.js to Kubernetes and AWS. By focusing on hiring top-notch developers, Netflix ensures that their tech infrastructure runs smoothly, scales efficiently, and adapts to new trends.

But let's be real: hiring top tech talent is tough, especially if you're not on Netflix. Tha's why choosing a tech stack that aligns with your team's existing skills is smart. If your team is well-versed in JavaScript, don't force them to learn Python unless there's a compelling reason to switch. You'll save time and money and avoid unnecessary headaches.

Future-proofing your Tech Stack (because the future is coming whether you're ready or not)

Ah, the future. It's unpredictable, exciting, and a little terrifying. When choosing your tech stack, you want to pick tools that will grow with you and adapt to future innovations. No one wants to be stuck with a tech stack that becomes obsolete in two years.

Adobe's Move to the Cloud!

Take Adobe, for example. A few years ago, they shifted from selling standalone software (like Photoshop) to offering Adobe Creative Cloud. This switch to a subscription-based model helped them scale and ensured they could keep up with the industry's shift to cloud computing. They might have fallen behind if they had stuck with the old model.

So, how do you future-proof your tech stack? Look for tools that are modular and flexible. Think of Microservices architecture as one that allows different parts of your system to scale independently. That way, when one part of your app becomes a runaway success (fingers crossed!), you won't need to rebuild your entire system to handle the load.

Concluding Thoughts: The Tech Stack Balancing Act

Choosing the right tech stack balances meeting your current needs, planning for future growth, and monitoring costs. But with the right approach, you can build a scalable tech stack that's secure, and ready to handle whatever comes your way. Remember, it's not about picking the shiniest or most popular tools—it's about finding what works for you and your team.

So, move forward and start building that tech stack! And if you ever get overwhelmed, remember that even Amazon started as a small online bookstore with a simple tech setup. They scaled, and you can, too!

We can put you on track!

Feeling a little overwhelmed by your tech stack choices? Don't worry—we're here to help. Contact our team today for a free consultation, and let's build the perfect stack for your business's future growth.

[muffinlevelchicanery]

[xpc-web-dev]

Learn Ruby: Day 6

(18/02/2023)

Today I learned Each.do (which to me looked like a para ), and break and next (I found them very useful) .

And now I wanted to share about mistakes, I was doing this exercise and it wasn't working.

After failing, I went to see the correction and made a silly mistake, in this case it was because I had not informed the key and value inside each one since this is a hash.

Then it wasn't informing the hash in hash format in the condition (I hadn't even done that until now) So it's nice to share that sometimes they are silly detention errors and not stupid HEUHEUEH.

How are you?

I wish you have a great Sunday, drink water and stay well mentally.

[xamitras]

For many of years I had this tradition of drawing Wirt and the beast once a year to see how much I have improved, then depression hit in 2023 and couldn't continue, but it left so really amazing art in the process

[singswan-springswan]

In a happy world where Jason is legally resurrected and gets to go to college like he's always dreamed of

[bluejayscrying]

Jason not even stopping as he walks past Tim and/or Damian, and just grabbing them by the back of the shirt and lifting them so he can carry them by the scruff like kittens to make things easier for him.

Tim, halfway thru an argument: you're not listening! i really don't think-

(Jason just walking past and grabbing him and walking away)

[ruporas]

dragon meat, you, and me

[novaneondream]

it’s our turn to make you smile

[rebel-girl-queen-of-my-world]

With international attention focused on Israel’s genocide in Gaza, Israel is violently and rapidly stealing more and more Palestinian land in the West Bank.

Israel’s most genocidal leaders are seeing through plans to force as many Palestinians out of their homes as possible in order to ensure they can never return.

“For every country that unilaterally recognizes a Palestinian state, we will establish a [illegal] settlement,” said Israeli Finance Minister Bezalel Smotrich.

Let’s be clear, stealing Palestinians land has been Israel’s goal since day 1. It’s illegal, it’s wrong, and it must be stopped.

No one is above international law. The Biden administration should be pushing Israel to abide by international law, not enabling its war crimes against Palestinians.

Like all people, Palestinians deserve to be safe and free in their homes.