#LegacyCode

[asadmukhtarr]

"Working Effectively with Legacy Code" by Michael C. Feathers is a must-read for developers and software engineers who deal with legacy systems. Legacy code, often characterized by its complexity, lack of documentation, and resistance to change, can be daunting to work with. This book provides practical strategies and techniques to understand, refactor, and improve legacy codebases. Below is a user-friendly, step-by-step breakdown of the key outcomes and takeaways from the book.

[jonfazzaro]

"Simply hoping for AI is not a solution. The major cause of all our headaches is the method by which we ask and answer questions about our systems."

[softlifesofttech]

Inheritance Tax: Legacy Code

After a few tumultuous weeks of hacking away at legacy code in the hopes of bringing it to a viable and secure state, there has been a clear cause for reflection. Maintaining software is an integral part of software development. The moment a codebase is deployed, it joins the ranks of entities clamouring for attention and care. It is an inevitable fact of life. In some instances, it's not so much the security updates that bring the most hassle, as that is to be expected; but sometimes it is the sheer breadth and depth of the application. From all ends you hear of the horrors of people's encounters with legacy code, often with the original owner long gone, leaving the current team to grapple with maintenance. This becomes increasingly pertinent when the legacy application is vital to business functioning, creating a dilemma of letting go versus managing a behemoth. You find fear rooted in the challenges associated with migration, and while warranted, there's a hope that fear can be replaced with a desire for ease and efficiency over a pompous technicality. In the contemporary landscape, out-of-the-box or low-code solutions have gained popularity, and the primary reason one might opt for a custom application is to fulfil a specific niche. But you find that most organisations are not offering substantially different services. There's usually a business that has either done it before you or done it after you and has done it better. It's about finding the appropriate service platform and outsourcing. An example I recently came across is Kraken Technology, which provides an out-of-the-box system for energy providers ready to be plugged in.

With a custom-built service, there's a cost associated with not only the gradual accumulation of technical debt but also the responsibility of training end-users and documenting processes. Hence, the appeal lies in ongoing support and the ease associated with low-code solutions. While people desire innovation and automation, it doesn't come without a burden. Each step associated with custom-built code, which is readily offered, incurs a massive cost that may not necessarily offset what would simply be a yearly fee. Even then, there's no consideration for the cost associated with opportunities—what else could you be doing with that time, effort, and resources to strengthen the business. OOB and low-code applications are easily integratable and often require only a few plugins or a handshake. This contrasts favourably to building a fully custom security component. Service providers have made it a point to make their services simple to integrate, baring in mind today's security challenges. There's an apprehension that lies in the fact that, although an OOB service may address high-level needs, it might not fully consider its specificity to an organisation and its unique requirements. Many software applications start as a buildable shell, allowing configuration according to an organisation's needs. However, organisations can adapt, discovering more efficient processes that challenge preconceived notions. This adaptability filters out outdated business models while lightening the workload for developers. Efforts can be focused on more innovative, smart, and slim solutions. I think it's imperative to emphasise the slimness of solutions, as that is how we find ourselves wrestling with the present conundrum of dealing with legacy code. There's a certain glory that comes with having a role people may associate with intelligence. However, in an effort to maintain this facade, people may forsake the simplest and easiest solutions, neglecting the overarching goals of cost-effectiveness, adaptation, and easy integration within a company. There is value in asking if this is relevant to the end user. When we consider IT in a holistic sense, we give more consideration to practicality over vain recognition. The real marker of a great application or system is the ease associated with it.

[jet-bradley]

decided to bite the bullet and remake

new blog: @lambda-core

follows from: @wheres-all-the-data (effectively a continuation of my current main, @legacycode)

This has been in the making since at least last october.

If you guys followed me on a different sideblog (like my space blog, @x-15), it's probably been transferred over to the new account. This is the one I'm leaving behind. I won't be deleting it because I don't want to erase what's effectively a log of my personality, interests, etc. through the end of high school, college, and university.

As for @tron20emails, I deliberately left it on this account to cut ties with the Tron fandom, but it's not getting deleted or anything. Whenever I want to return to the fandom, I'll probably transfer ownership of it to the new account to maintain it. I could be convinced to share ownership with someone who's been in the 2.0 fandom for a while, if anybody has an interest in maintaining it. But I won't be handing it to just anyone, only people I know have an interest in maintaining an asset for that community. Message me on my new blog if you're interested.

I have a lot to say about this decision, and yet, nothing at all. I just need a fresh start. It feels weird to cut off an old part of myself like this, but it's just how it is. I need to get out of here, and changing my url and icon isn't gonna cut it this time. I need out.

Thanks for a good... seven !? (2017?) years everyone. I had a lot of fun on this account. If you wanna keep contact, don't be a stranger, hmu over there.

[wheres-all-the-data]

Fandoms, old computers, other interests: @lambda-core

Blog where I pretend to be my gamerbro Paragon Shepard: @n7-jet-shepard

Amusement rides: @xcelerator

Space: @x-15

E-stop buttons: @estops

Other aesthetic blog: @shearflow

p.s. I used to he @legacycode, but I remade :>

[codigonautas]

¿Qué es el Código Heredado (Legacy Code)? - https://codigonautas.com/codigo-heredado-legacy-code/?feed_id=257&_unique_id=6746e13786ab4 #CódigoHeredado #DesarrolloSoftware #LegacyCode #MantenimientoSoftware

[insanepoll]

Early doomguy propaganda!

He rips and tears and then goes back to his gamer cave where he eats fruit candy and pizza and takoyaki chips. While gaming

He has this cooking magazine

Also the most insane doomguy is in the N64 game and I feel like that adds batshit points. Bro just jumped into hell forever the moment he had a console exclusive. Like

the whiplash i received i–

[gusgrissom]

[coffee emoji] american aerospace engineering peaked with the xf-85 goblin bcuz its cute

Oh that is just A Little Guy…

[samrat747]

#legacycode https://www.instagram.com/p/CV0hkJNh2qZ/?utm_medium=tumblr

[jonfazzaro]

"The ability to traverse the codebase at such a level of granularity is particularly important as it reduces noise (i.e. unnecessary code) from the context provided to LLMs, especially relevant for files that do not contain highly cohesive code."

[captain-deepi31-naresh]

Learn a basic process to develop a solution to a problem. There is nothing unique in this drive to use a computer to solve a problem, this process can be used to solve a wide variety of problems that have nothing to do with the computer.

[scriptsouffle]

Further integration with Laravel

A few weeks ago I wrote a short blog post outlining some of the early success and challenges I had had integrating Laravel with a large legacy application. It is not possible to start again from scratch, so I am using Laravel to provide the application development process with a modern platform while continuing to allow the legacy code to run unhindered.

Since then i have continued to integrate the code and have come upon and successfully solved several integration issues.

Laravel must be loaded in a function.

Laravel Takes over all Error Processing

Sometimes you think Laravel is causing a bug but its not.

Sometimes you can use both

Integration

At the begining I was unsure exactly how integrated I would make the Laravel Code and the Legacy Non Laravel Code. I began by only loading the Laravel Codebase when I needed it, but quickly realise that having laravel functions available provided a huge advantage to the legacy codebase, so now I just load laravel in the config load file for the legacy codebase, ensuring I have access to all functions at all times.

Together but seperate.

One obvious area for seperation is in views. My legacy code base uses smarty, which I have always liked, and have been using since V1. If laravel had an option to use Smarty I would have continued with it, but thats not possible, so I use Blade with my new Laravel code.

This was a simple decision. Old code would continue to use Smarty, new code would use Blade.

Then...

Then I decided to provide information about a new feature (Subscriptions) to an old feature (Booking) so I pulled in the new Subscription Eloquent model into my view_booking page and passed it to a new Smarty template to use as a partial in the main Smarty Template? But why write a new template in Smarty, if I'm slowly going to be moving to Blade? So instead I called

$SubscriptionsHTML = View::make('bcs.booking.tab_subscriptions',['Subscriptions' => $Subscriptions]);

This runs my new Blade Partial through the blade engine and returns my HTML which I can pass to Smarty as part of its content.

This may seem like I'm mixing up lots of things and heading for making myself very confused, however I see it differntly. i have decided to embrace (Laravel)[https://laravel.com/] and use it moving forward. The more I integrate it with the old codebase the more I will be willing to write ALL new code in any part of the codebase using the Laravel Framework.

I have been amazed at how well I have been able to integrate an existing project with Laravel.

[kalki-maitreya]

"The Grid Calls." #LegacyCode https://www.instagram.com/p/CCv5bsenDgi/?igshid=1h70d2h9468ci

[amuseablesun]

🎁

[tron20emails]

Welcome to TRON 2.0 Emails!

The purpose of this blog is to provide a means for TRON 2.0 fans to locate TRON 2.0 emails more easily. This blog hosts all 75 emails in TRON 2.0. You may browse them by:

"Date" (actually month)

Character (separated by whether they're mentioned or involved in the email chain)

Email thread

Level

A list of all emails

I have also provided transcripts of any corrupted emails, free of corruption, so that users who struggle with random characters interspersed in the middle of text can read them without the corruption.

To-do list for this blog:

A means of browsing emails in chronological order

Combining "in-thread" tags for characters with multiple canon emails

Desktop theme

Disclaimer: TRON 2.0 is the property of Disney and Monolith Studios. I claim ownership of nothing on this blog and do not make profit from anything on this blog. This blog is NOT intended as a "replacement" for playing TRON 2.0, which is available on GOG.com and Steam. Support the original developers!

This blog is provided courtesy of @jet-bradley. My main blog is @legacycode. Please contact me if you find any errors or have any questions.

[jet-bradley]

one of my favorite blogs that i follow for @legacycode posted crypto and i had to unfollow :(