circlejourney

artist, musician, writer (& more)

Art account: @circlejourneyart

posts from @circlejourney tagged #codeposting

also:

Read more about it
Life happens so fast. I feel like I blinked and suddenly the chicken game that began with "haha wouldn't this be funny" actually exists.

We'll be opening 50 slots on 15 September, hope to see some people there! It's still in beta so you get to see the site in not-quite-finished state.

(Planning 25 slots at 11am AEST and then another 25 slots at 11pm AEST)



I've been thinking about migrating my deeply fragmented online output to my website. From tweeted doodles to any Tumblr blog post worth remembering to whatever is on my Imgur that I can still salvage. I just...would really like to have it all in one place, you know?

I could not even begin to tell you how much there is, nor estimate the file space I'd need. But this would be a massive undertaking, possibly involving thousands if not tens of thousands of files, and it's one that I'd like to automate to whatever degree I can. I can probably scrape my own profiles for text, and autogenerate thumbnails with PHP. but the hard part is actually figuring out how I'm going to tag and display it.

I'd almost definitely do with Laravel, though this would necessitate setting this on a subdomain (possibly new.circlejourney) but that means I'd have to get back to updating it.

It'll happen eventually. I think. I'm just tired of hunting everywhere for my own works, lol.



circlejourney
@circlejourney

I'm losing my mind over how good it looks......Laravel my beloved I am marrying you


circlejourney
@circlejourney

So, I know the front-end styling has nothing to do with Laravel directly, but here's the thing:

I used to write everything for my site -- login authentication systems, database update forms, even the site's templating engine -- in vanilla PHP. Of all things. Every time I had a new project with a new use case, I'd spend a solid half of the time on setup - usually writing a framework, creating a database update tool, then filling said database.

And those were not especially robust; if I suddenly realised that one thing didn't work or was wrong, I'd have to go back through and update large swathes of my work.

But Laravel has like...everything I could ever need, and it just works out of the box, so I get to skip the drudgery of (to use my favourite phrase) reinventing the wheel and get to the actual fun bits -- at scale. I can fill my local tables with whatever junk links I want, and just know that I can quickly and safely transform every row of the table if I decided down the line that a different structure worked better.

SO...I can focus on front-end styling without worrying about whether I'll have to go through and rearrange 5 different webpages when I decide to change the page structure completely. :)