overview for vraylle

Primitive Technology: Wet Season Destroys Thatched Workshop by vraylle in c/humanities@beehaw.org

[-] vraylle@beehaw.org 4 points 7 months ago

He mentions (in the comments of the video) the catch-22 of needing the thatch to last long enough to make enough bricks to make a brick and tile workshop that doesn't need thatch.

Feral by vraylle in c/humor@beehaw.org

[-] vraylle@beehaw.org 3 points 9 months ago

Guess you haven't met my neighbors.

Your next Windows PC may need at least 16GB of RAM by vraylle in c/technology@beehaw.org

[-] vraylle@beehaw.org 4 points 10 months ago

I'm still running 16GB. I built my PC in 2015 and it's been my gaming/work/dev machine ever since. Have only upgraded GPU and storage.

It is definitely showing its age, but I don't need to worry about the Windows requirements. My CPU isn't supported for Windows 11 so I'm sticking with what I've got until Windows 10 hits EoL. Then I'll probably buy a 64GB AMD system and switch to Mint at that point.

Microsoft moving fully to the cloud, does this mean something to us? by vraylle in c/technology@beehaw.org

[-] vraylle@beehaw.org 1 points 1 year ago

Bingo! Rural in particular is slow and unreliable. Something like this isn't a practical option even if I was OK with it. I'm already planning to switch to Linux when I get a new PC or when Windows 10 hits EoL. This would make the switch a necessity.

3

I hate time zones, especially when I'm stupid (beehaw.org)

submitted 1 year ago by vraylle@beehaw.org to c/programming@beehaw.org

0 comments fedilink

The primary application at my job was...not well written. Originally .NET Framework 3.5 with a strange collection of approaches to MVC. SQL Server for data. I claimed it look like something written by CS students fresh out of college on their first job. Turned out I was close...it was written by 3rd-year CS interns. We've fixed and improved a ton (including migrating to .NET 6 earlier this year).

One of the ongoing issues was the use of SMALLDATETIME and DATE fields for everything. We've been gradually migrating these to DATETIME2 or DATETIMEOFFSET (we don't have future dates) as UTC. Because 95% of our usage had been CST/EST, we've typically set the time component to 17 hours to get a reasonable noonish time in those zones when we don't have a better time of day.

Had another round of these today and thought it was going well. Finally got it running and everything was +1 day from where it should be. Spent an hour trying to figure out the issue.

Converting for display incorrectly? No. Serializer not doing what was expected? No. Configured time zone got messed up? No. Brought in our DBA to help me figure it out.

I had added 17 days twice.

Side note: I wish everybody was on UTC time and time zones would forever disappear into the ether.

TLDR; Migrated time wrong because I'm stupid.