#software development

[geminisee]

x

[la-principessa-nuova]

I made a support request with a vendor asking if there’s a way to leverage the logic they already have for determining what counts as a business day (it is very critical that this is done exactly correctly and that it never breaks in the future if nobody is maintaining it) when using their API since I didn’t want to have to maintain a separate source of truth for it, and in their response they said:

it is not too hard to do date/timestamp arithmetic

which any developer who has done date/time arithmetic knows is the understatement of the century

Famously everyone thinks so until they take down an important system by forgetting about DST, or leap years, or that leap years don’t happen every 100 years, or that they do happen every 400 years, or not considering implications of people using different calendar systems, even if they’re just slightly different like having weeks start on a different day, or they consider whether the first week of the month is the first full week or the partial week before that, or they format it in a different order.

Then when they finally think, “OK, but I know about that,” then they learn about the leap second, or the negative leap second.

So yes, date math is “too hard”.

[nixcraft]

[mlembug]

the current landscape of webdev needs to know that I don't need web applications that scale up to millions of users, I need web applications that scale down to 5 users or less

[heart-ghost-studyblr]

Getting old is interesting. I've always been a middle ground between sports (skateboarding, surfing, jiu-jitsu) and an avid student. Over time, it's clear that you can't keep trying the same tricks, just as you can't study the same way.

Today, as I'm writing an article about event-driven architectures, I realize that final exams in college were much easier, just like it's not as easy to jump the same stairs on a skateboard as I did when I was 18. In the image, you can see my favorite note-taking app, Obsidian, and my Neovim terminal. I'm diving deep into Java, and for that, I'm taking a Spring Boot bootcamp offered by Claro through the DIO Innovation One platform.

[techtimechronicles24]

🇺🇲 Dive into the history of the Apple III (styled as apple ///), a computer that marked an ambitious step forward for Apple Inc. Released in May 1980, the Apple III was designed to be a successor to the highly successful Apple II series, aimed at the business market.

💻 The Apple III was envisioned as a business-oriented machine that would bridge the gap between personal and professional computing. Apple sought to improve upon the Apple II's capabilities, both in terms of hardware and software, while maintaining backward compatibility. Steve Jobs, who was heavily involved in its design, emphasized aesthetics and functionality. The Apple III featured a sleek design and was intended to be more robust and reliable, with enhanced performance.

⚙️ The Apple III was powered by a 2 MHz Synertek 6502A processor, an improvement over the Apple II's 1 MHz processor. It came with 128 KB of RAM, expandable to 512 KB, which was a significant upgrade at the time. The computer featured an internal 140 KB 5.25-inch floppy disk drive. An external floppy drive could also be connected for additional storage. The Apple III supported a variety of display modes, including 24 lines of 80-column text and multiple graphics modes. It ran on Apple SOS (Sophisticated Operating System), which offered advanced features such as hierarchical file system and support for multiple users.

💡 The Apple III introduced several innovations, including a built-in clock, advanced sound capabilities, and a new keyboard design. However, it also faced significant challenges: The Apple III initially suffered from severe overheating problems due to the lack of a cooling fan. This led to hardware failures, with chips often becoming dislodged from their sockets. Early units were plagued by reliability issues, which hurt the computer’s reputation in the business market.

💔 Despite its rocky start, Apple released an improved version in 1981, known as the Apple III Plus, which addressed many of the initial issues. The Apple III ultimately did not achieve the commercial success Apple had hoped for, with only about 65,000 units sold. Nevertheless, the Apple III played a crucial role in Apple's development. The lessons learned from its challenges influenced the design and engineering of future Apple products, including the highly successful Apple Macintosh.

💾 The Apple III stands as a fascinating chapter in the history of computing. While it may not have achieved the commercial triumph of its predecessor or successors, its ambition and the innovative spirit behind its design left an indelible mark on Apple’s evolution. Today, the Apple III is remembered as a symbol of both the challenges and the relentless drive for innovation that characterize Apple's journey.

[code-es]

Coding resource!

exercism.org

A free website where you get specific problems to methodically learn small concepts of a programming language. Do 10 minutes to 1 hour every day, and then you will keep practicing every day, and you will be able to use the skills you learn in your real projects. They walk you through the problem all the way, and it's a super good way to learn!

[jay0fspad3s]

I swear that half of programming is staring at your screen going "how do I do this" and the other half is figuring out why something doesn't work and being like, "oh duh I'm just fucking stupid"

[hayacode]

Software Development using C# (Bootcamp)

Week 6 done ✨ Almost halfway through the bootcamp 🥳

We started the backend project last week, this project is a teamwork and each team has 5 students. Honestly, I was scared of it because being the only one with a biology degree in a whole class of tech students made me overthink how will I do in teamwork and how I will definitely screw up everything and it’s true I made so many mistakes as expected (today lesson the hardest orz) but i am so glad my team members are so kind and they help me a lot 🥹

What i have learned from the bootcamp in the past 2 weeks 💻

- Database

- Data modeling 

- Relationship: 1-1, 1-M, M-M

- REST architecture

- HTTP methods & status codes

- Introduction to ASP.NET Core

- Webapi template & Swagger

- Create endpoints for CRUD operations

- Handle & return  error in webapi

- Using controller and service folder with dependency injection

- Authentication & Authorization (role base) 

- Introduction to ORMs

- Relations in EF Core

- Config database with Npgsql

(Yes, all of this in 2 weeks sobbbs)

Now let’s talk about C# again

- i am 50% done with codecademy course

- I Finished Bro Code C# videos (highly recommended and I plan to watch his React videos soon)

I am also almost done with my React first course ✨

Oh yeah Last but not least, this bootcamp gives us career advice classes related to developers' jobs, interviews, and how to have a good CV, LinkedIn, and github (if you are a friend on Discord, dm me so I can send you all the amazing stuff 💫)

[izicodes]

C# Study Links | Resources ✨

As I am starting to relearn C#, I thought why not share some links that have helped me in the past and what new ones I will be using this time to learn! I already made a similar resource post (post 1 | post 2) for C# in the past but why not a new one? 🤗

Microsoft Learn - LINK

C# Station - LINK

YouTube - LINK

SoloLearn - LINK

Codecademy - LINK

Learn C# - LINK

C# Yellow Book - LINK

C# Programming Guide - LINK

Tutorials Point - LINK

Roadmap to ASP.NET Core Developer (C#): LINK

C# Subreddit - LINK

Dot Net Perls - LINK

C# Coding Conventions - LINK

The Ultimate C# Guide For Beginners - LINK

That's all for now! If this does interests you, do check out the other posts (1 | 2) I made of other C# resources!

Happy coding/programming! 😎💻👍🏾

[nixcraft]

me_irl

[computer-nerd-girl]

[heart-ghost-studyblr]

Today I have an merge conflict plus a deploy error in my link in bio app which is deployed in Fly io. Not big deal, just came out that was auth error in deployment, but about the merge conflict was a little bit more than a few lines.

[rahisaurus]

The company I loved working for has run out of money to pay me, so I'm out.

I am a competent C++ developer with over 8 years of commercial experience in the computer graphics industry. I've lead multiple projects through the software pipeline from concept to distribution and maintenance.

I have excellent learning skills, I can pick up new techniques and frameworks and adapt myself to your team quickly.

Main skills: C++, C#, OpenGL, 3D Geometry Maths

Full CV: (OneDrive link)

If anybody knows of a remote working opportunity for a mid-senior developer where I can continue working from the UK, please contact me! Thanks for taking the time to read!

[code-es]

The women who laid the foundation of tech

EDIT: I noticed that this post ended up being reblogged by terfs. If you're transphobic this post is not for you to reblog. I want to celebrate everyone who is not a cis man in this industry, including trans women and nonbinary people in tech, and it was my mistake to only include cis women in this post when there are so many trans women and nonbinary people who have done great things in tech as well. Trans women are women and just as important.

Here you can read about trans ppl in tech, and please do:

https://www.thecodingspace.com/blog/2022-03-01-six-trans-programmers-who-shattered-the-lavender-ceiling/

https://abcnews.go.com/Business/transgender-tech-visibility-obstacles-remain/story?id=76374628

The morning of women's day i attended a super inspiring seminar about being a woman in tech at a large tech company in my city, and now I'm inspired to share what I learned with all of you!

I didn't have time to finish this post on women's day, but it's not too late to post now: every day is a day to celebrate women!

Women actually laid the foundation for a lot of the tech industry.

For example, the first computer, ENIAC, was programmed completely by women! While men were the behind the scenes engineers, it was women who did all the actual programming of ENIAC.

The women who made up the team responsible for programming it were called Jean Bartik, Kay McNulty, Betty Holberton, Marlyn Wescoff, Frances V. Spence and Ruth Teitelbaum.

I think one woman who is finally getting her overdue recognition is Ada Lovelace. She was a mathematician (also often referred to as the first programmer) who created the first algorithm in 1842, which wasn't recognized until 1953! However, since none of her machines were ever completed it was never tested in practice during her time.

She has since been celebrated by giants such as google, and she has given name to a programming language (Ada). She was also the first person to write about what is today known as AI. Back when she was practicing, computers were simply thought of as calculators. But she had an idea that if computers can understand numbers, then that can be translated to letters, and in turn that can lead to computers being able to handle words, and eventually even write, draw and create music.

Hedy Lamarr was a famous Hollywood actress in the 40's, but she was also an inventor who laid ground for what we use today for Wi-Fi, Bluetooth and GPS services.

During WW2 she wanted to contribute positviely to the military efforts against the Nazis, and she tried to figure out how to radio control torpedoes. In 1942 she patented her technology "Secret Communications System", also known as frequency hopping, which laid the foundation for the technology we use today for Wi-Fi, GPS and Bluetooth. It wasn't until 1962 that it was first used for its intended purpose, during the cuban missile crisis.

Grace Hopper invented the first compiler, called A-0, in 1955, and was also part of the Univac team, which was the company also responsible for building ENIAC. She also initiated work on the COBOL programming language.

She was also the one to coin the term "bug" in 1947. Computers back then had lights to visualize their working process (which was also a womans idea to implement btw) and bugs would be attracted to the lights, but usually that was no issue - until a bug made its way into a tube which caused the computer to stop working. Hopper taped the bug to a piece of paper and logged what caused the crash - a bug.

Dorothy Vaughan (left), alongside colleagues such as Katherine Johnson (middle) and Mary Jackson (right), was a mathematician at NASA (called NACA when she started) who worked on the orbit for the first ever manned spaceflight and later also on Apollo 11 that would take humanity to the moon!

When Vaughan started at what was then called NACA, segregation was still prevalent in the US and she was not allowed in the same areas in the office as her white colleagues. Another department was formed for the black staff, and when the director of said department unexpectedly died, she was appointed as the new director and thus became the first ever black woman at that position at NACA/NASA. In 1958 when NACA becomes NASA segregation is forbidden, and that is when Vaughan and her colleagues Johnson and Jackson started working on programming the orbit and later also Apollo 11.

Continuing on the same track of NASA and space, Margaret Hamilton was the Apollo project's first actual programmer. Hamilton became the director of software engineering at NASA in 1965, and she was also the person to first coin the term !

In the image above, she stands next to all the handwritten code that was used to send humanity to the moon. During the early stages of the project when she would speak of "sofware engineering", software development was not taken as seriously as other forms of engineering, and it wasn't regarded as a science, either. She wanted to legitimize software development as an engineering discipline, and overtime the term "software engineering" gained the same respect as any other technical discipline.

And lastly, if you're a woman in STEM, I want to highlight and celebrate you! Being a woman in a male dominated industry is not easy, we often suffer from sterotype threat and are not seen as our own individuals, but rather "the woman" in a room full of men. But just as these women, I'm sure you will achieve greatness!!

Here are some additional resources if you'd like to learn more:

https://www.history.com/news/coding-used-to-be-a-womans-job-so-it-was-paid-less-and-undervalued

https://digitalfuturesociety.com/programming-when-did-womens-work-become-a-mans-world/

And this was mainly my source for this post, but it's unfortunately only available in Swedish:

Thank you for reading ✨