#Software engineering

[nixcraft]

[hyperoperationfractallisation]

[thewinastudyblog]

some advice i have for future computer science students

as soon as you learn data structures & complexity, run, don’t just walk, RUN to leetcode while the knowledge is still fresh in your mind. your entire career and whether you’ll get a well-paying job vs an average paying job depends on how good you are at leetcode.

build as many projects as you can, and i’m not talking tutorial projects that take a few hours, i’m talking big projects. working on a project for a month or two will get you really far.

if you don’t have an internship, do not waste your summers, learn new technologies, languages, concepts and build projects you can put in your cv.

try to participate in hackathons and coding competitions. it’s okay if you fail, but you’ll learn a lot.

learn how to read documentation. most tutorials don’t even cover a quarter of what a language, framework or software has to offer. the sooner you make reading documentation a habit, the better it is. and yes i know, documentation is long and hard to read. my advice is only read the sections that are relevant to you in the moment. something i also personally do is look at the code examples at the same time as i am reading the paragraphs, it really helps easily absorb the information.

try not to use chatgpt. and if you do, then at least use it for stuff you know you can do yourself and will be able to correct if the bot gets it wrong. using chatgpt is a very slippery slope and the more you use it the less you learn.

the math is important. math teaches you how to reason and how to develop better logical thinking. just because you don’t see yourself using the xyz theorem you’ve learnt anytime in the future doesn’t mean the math is useless.

be prepared to get comfortable with erros, issues, bugs and just problems in general. you’ll be coding 30% of the time and debugging 70% of the time (i’m exaggerating but sometimes it feels like this is the case lol), and that’s okay, it’s how we learn and the sooner you embrace it the better. if you’re someone who easily gets frustrated, then this is a heads up.

learn as you go. there is no such thing as waiting until you know everything before you start on a project. the only way and the best way to learn in this field is practice, so build, build, and build.

these are all the ones i could think of for now. feel free to comment your thoughts and questions <3

[scipunk]

The Matrix: Resurrections (2021)

[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”.

[oldguydoesstuff]

RIP Dr. Thomas Kurtz - inventor of the BASIC programming language that became widely used in the 1970s and 80s for programming minicomputer and home computer systems.

BASIC made computer programming accessible to a wide audience that included students, scientists and businesses due to its easy to understand syntax, immediately runnable code, and widespread availability. My earliest explorations of the software world involved writing BASIC programs, and I'm very grateful for Dr. Kurtz's contributions to the world of computing.

[punstars]

[mrbreaknfix]

Other people follow rules. I follow results

[zooplekochi]

They call it "Cost optimization to navigate crises"

[nixcraft]

[political-us]

[scipunk]

Devs (2020)

[omeletcat]

i got an old laptop from my grandpa and was googling about it, and the wikipedia page for the micro-soft acer aspire has an image of the acer aspire with the wikipedia page, containing the image of the acer aspire with the wikipedia page, containing the image of the acer aspire with the wikipedia page, containing the image of the acer aspire with the wikipedia page, containing the image of the acer aspire with the wikipedia page, containing the image of the acer aspire with the wikipedia page, containing the image of the acer aspire with the wikipedia page....

[nixcraft]

Vibe coding in a nutshell

[heart-ghost-studyblr]

I found myself surrounded by companions daring to tackle a real software architecture challenge. We shared a good wine and cheese to conquer it together! (Unfortunately, there’s always something waiting to be dealt with on Monday.)

The glow of my Neovim terminal in Monokai theme reflects my rhythm — a guy who doesn’t stop on weekends but knows that balance isn’t about being all-in, all day.

The setup screams character: a seamless fusion of productivity and comfort. Lazygit commands at my fingertips, a Ghibli-esque avatar paired with Neofetch adding a touch of Tumblr aesthetic, and a playlist of Korean indie OSTs playing in the background to add depth to every keystroke.

This is how I drive — in code, creativity, and moments that are unapologetically mine.