Skip to main content

ДО СВИДАНИЯ ЛЕТО

Doh Svedanyah Lyeto (Poet's note -- to be read aloud) Charge your glasses and toast the summer 'Fifteen
Gone much too quickly, as if never been.
Yet hints of it linger to buoy the keen
As Autumn approaches and changes the scene.

I have counted days passing, while sat at the shore
I have slept in the sunshine and woke wanting more
I pondered the Pleiades and wondered "What for?"
I will not leave summer, like the party's last boor.

I secure the lee line and make everything fast
The fisherman throwing the redemptive cast.
And though I deny it, the truth outs at last
Fewer days lie ahead than exist in my past

The dripping faucet gets the plumber
Behind the beat the lazy drummer
The silent rock grows ever dumber
A muted witness to the last of summer.

Our youth is betrayed by our bodies last treason
So put down your labor and come join with me son Time marches on without rhyme or reason
I mourn the passing of more than the season

Comments

Popular posts from this blog

Preventing accidental large deletes.

Instructions for Developers on Using the safe_delete Stored Procedure To enhance safety and auditability of delete operations within our databases, we have implemented a controlled deletion process using a stored procedure named safe_delete . This procedure relies on a temporary table ( temp_delete_table ) that lists complete records intended for deletion, not just their IDs. This approach helps prevent accidental deletions and provides a traceable audit log of delete actions. Why We Are Doing This Controlled Deletions : Centralizing delete operations through a stored procedure reduces the risk of erroneous or unauthorized deletions. Auditability : Using a temporary table to store complete records before deletion allows for an in-depth review and verification process, enhancing our ability to confirm and audit delete operations accurately. Security : Restricting direct delete permissions and channeling deletions through a specific proced...
 In software engineering, accumulating code behind a release wall is akin to gathering water behind a dam. Just as a dam must be built higher and stronger to contain an increasing volume of water, the more code we delay releasing, the more resources we must allocate to prevent a catastrophic flood—major bugs or system failures—while also managing the inevitable trickles—minor issues and defects. Frequent, smaller releases act like controlled spillways, effectively managing the flow of updates and reducing the risk of overwhelming both the system and the team. The ideal of ci/cd may not be achievable for all teams, but smaller and faster is always better.

October is Cyber Security Month

The President has declared October as Cybersecurity month.  It's not a bad idea -- just like you change the batteries in your smoke detectors once a year, maybe you should review your electronic vulbnerabilities? My top ten security tips: 1) Change your passwords.  You've had them too long, you use the same password in too many places.  Somewhere someone has hacked a site that has your username and password in plain text.  Now they are getting ready to try that username/password somewhere else.  Beat them to the punch. 2) Use a safe browser.  That means anything that's not Internet Explorer.   I prefer chrome. 3) Use 2 step verification for your email account.  If your email doesn't provide 2 step authentication consider switching. 4) Get a free credit report  and review it.  You are entitled to one free report a year.   BE VERY CAREFUL!  There are man scam sites that offer free credit reports.  Go through the s...