Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Search - "i like the transitions"
I hate time.
Yes, that dimension which unidirectionally rushes by and makes us miss deadlines.
Also yes, that object in most programming languages which chokes to death on formatting conversions, timezones, DST transitions and leap seconds.
But above all, I hate doing chronological things from the point of view of code, because it always involves scheduling and polling of some kind, through cron jobs and queues with workers.
When the web of actions dependent on predicted future and passed past events becomes complicated, the queries become heavy... and with slow queries, queues might lock or get delayed just a little bit...
So you start caching things in faster places, figure out ways to predict worker/thread priorities and improve scheduling algorithms.
But then you start worrying about cache warming and cascading, about hashing results and flushing data, about keeping all those truths in sync...
I had a nightmare last night.
I was a watchmaker, and I had to fix a giant ticking watch, forced to run like a mouse while poking at gears.
I fucking need a break. But time ticks on...2
I never liked when rappers do the bridge on emotional songs.
the song starts like "ooohh, baby I love you, you know we're for each other, bla bla",
then the rapper comes up with some raw shit like
"baby you know that this cum is only for you,
we're meant for each other, you suck me so good,
you know that you moan when I raw in your ass"
bro, wtf... it was a gentle romantic song...
or when the singer is depressed, has dilemmas about life
and the rapper's like "im rolling on my mercedes bitch"
it actually sounds like rapper is intentionally making the singer look like a pussy.
now, before some troll comments that I'm an idiot dinosaur that can't understand hip hop, let me say:
I like hip hop, I'm not gonna make a fool of myself by name dropping rappers from the past or today, as if you needed credentials to emit any option about the genre. I will only say that I've been listening on and off since I was 15.
And I like emotional songs as well, any genre.
The problem is that I feel a sort of disconnect between the singer and rapper of a song.
You can't have one performer be like "I feel sad, life is hard" and then the other like "I GOT HELLA MAD DICK NIGGA, CHOKE ON MY CUM", in the SAME fucking song.
They are completely opposite emotions,
That works in movies, eg: a romantic slasher film, but that shit works because it's feature length.
There's enough time to make transitions and to let the mood slowly change.
Meanwhile, these guys are trying to stitch these things together in 3 fucking minute songs.
But this shit dominates the charts, so ¯\_(ツ)_/¯2
(long post is long)
This one is for the .net folks. After evaluating the technology top to bottom and even reimplementing several examples I commonly use for smoke testing new technology, I'm just going to call it:
Blazor is the next Silverlight.
It's just beyond the pale in terms of being architecturally flawed, and yet they're rushing it out as hard as possible to coincide with the .Net 5 rebranding silo extravaganza. We are officially entering round 3 of "sacrifice .Net on the altar of enterprise comfort." Get excited.
Since we've arrived here, I can only assume the Asp.net Ajax fiasco is far enough in the past that a new generation of devs doesn't recall its inherent catastrophic weaknesses. The architecture was this:
1. Create a component as a "WebUserControl"
2. Any time a bound DOM operation occurs from user interaction, send a payload back to the server
3. The server runs the code to process the event; it spits back more HTML
Some client-side js then dutifully updates the UI by unceremoniously stuffing the markup into an element's innerHTML property like so much sausage.
If you understand that, you've adequately understood how Blazor works. There's some optimization like signalR WebSockets for update streaming (the first and only time most blazor devs will ever use WebSockets, I even see developers claiming that they're "using SignalR, Idserver4, gRPC, etc." because the template seeds it for them. The hubris.), but that's the gist. The astute viewer will have noticed a few things here, including the disconnect between repaints, inability to blend update operations and transitions, and the potential for absolutely obliterative, connection-volatile, abusive transactional logic flying back and forth to the server. It's the bring out your dead approach to seeing how much of your IT budget is dedicated to paying for bandwidth and CPU time.
Blazor goes a step further in the server-side render scenario and sends every DOM event it binds to the server for processing. These include millisecond-scale events like scroll, which, at least according to GitHub issues, devs are quickly realizing requires debouncing, though they aren't quite sure how to accomplish that. Since this immediately becomes an issue with tickets saying things like, "scroll event crater server, Ugg need help! You said Blazorclub good. Ugg believe, Ugg wants reparations!" the team chooses a great answer to many problems for the wrong reasons:
For those who aren't familiar, gRPC has a substantial amount of compression primarily courtesy of a rather excellent binary format developed by Google. Who needs the Quickie Mart, or indeed a sound markup delivery and view strategy when you can compress the shit out of the payload and ignore the problem. (Shhh, I hear you back there, no spoilers. What will happen when even that compression ceases to cut it, indeed). One might look at all this inductive-reasoning-as-development and ask themselves, "butwai?!" The reason is that the server-side story is just a way to buy time to flesh out the even more fundamentally broken browser-side story. To explain that, we need a little perspective.
The relationship between Microsoft and it's enterprise customers is your typical mutually abusive co-dependent relationship. Microsoft goes through phases of tacit disinterest, where it virtually ignores them. And rightly so, the enterprise customers tend to be weaksauce, mono-platform, mono-language types who come to work, collect a paycheck, and go home. They want to suckle on the teat of the vendor that enables them to get a plug and play experience for delivering their internal systems.
And that's fine. But it's also dull; it's the spouse that lets themselves go, it's the girlfriend in the distracted boyfriend meme. Those aren't the people who keep your platform relevant and competitive. For Microsoft, that crowd has always been the exploratory end of the developer community: alt.net, and more recently, the dotnet core community (StackOverflow 2020's most loved platform, for the haters). Alt.net seeded every competitive advantage the dotnet ecosystem has, and dotnet core capitalized on. Like DI? You're welcome. Are you enjoying MVC? Your gratitude is understood. Cool serializers, gRPC/protobuff, 1st class APIs, metadata-driven clients, code generation, micro ORMs, etc., etc., et al. Dear enterpriseur, you are fucking welcome.
Anyways, b2blazor. So, the front end (Blazor WebAssembly) story begins with the average enterprise FOMO. When enterprises get FOMO, they start to Karen/Kevin super hard, slinging around money, privilege, premiere support tickets, etc. until Microsoft, the distracted boyfriend, eventually turns back and says, "sorry babe, wut was that?" You know, shit like managers unironically looking at cloud reps and demanding to know if "you can handle our load!" Meanwhile, any actual engineer hides under the table facepalming and trying not to die from embarrassment.38
I gotta say, I actually admire the work that content creators must go thru to make quality content.
So as I stated before I’m working on YouTube channel, under the name “TheSoftwareSage” ... to create tutorials and a way of me teaching software the way I believe it should be taught, not how the mainstream methods of today are.
Bottom up approach rather than top down
(Must start with a firm understanding of the foundation.. and build upon the knowledge as we go thru the layers of abstraction but the key concepts must be understood first)
Anyway, I’m working on this in my spare time and I was not aware of how much effort I would actually need todo this right haha. At first I figured I’d just screencast a monitor and have a ppt or text editor or terminal open and that stuff and just do it.
As In person with my interns I never have “planned” lessons or content is all impromptu based on the need at the time and I just go with it, with their computers and a whiteboard lol.
I was wrong for video recording lol... maybe it’s OCD... or perfectionism, I’ll make a video, review it like 5times and then be like shit I forgot to mention this or that or I didn’t like how I explained this or that
I keep worrying too much about colors, and sound levels and quality and transitions and video angles and all this other shit.
And then post editing fuck.... I’m about ready to say fuck it and “do it live .. one shot” and just upload the end result.
I guess this would be in the content world similar to our “paralysis analysis” notion.10
I'd like to talk about my first impression of the new product of Microsoft :
"New Edge Browser"
I just wanted to take a shallow glance at this browser, and it was horribly awesome in contrary with my expectations.
The design and animations and smooth transitions, ease of migration from chrome and enhanced UI were the things that aroused my interest at the first 5 minutes of usage, as a frontend developer, I'm so much eager to dig up more in it. Share your experience and opinions with me 😉22
What I'm doing now, writing a JS library for a simple kitchen timer (like, something that can be wound up, is ticking, can be paused, etc). Here's a list of neat stuff I've learned:
Polyfilling as a lib author (I decided against it).
Packaging the lib (using Rollup, ES6 modules are totes cool).
Using flow to add static typing in strategic places (started appreciating types in JS since reading up on functional programming).
Modelling state and transitions using an explicit state machine. (Fucking finally. There's usually an implicit state machine somewhere, only spread out all over the app...)
Using mostly side-effect free methods, being very explicit about when and why things are mutated).
Test-first/TDD (ish) using Jest and the awesome Wallabyjs.
Freeing up mental capacity by letting Prettier format my code for me (it was hard to let go but totally worth it).
Started using git.
Did all work on Ubuntu after pretty much a lifetime of Windows (initially to separate work from gaming) and finally swapped MS Visual Studio for Atom.
When it's finished I'm going to publish it on GitHub, which will also be a first for me. Might try out some CI platform while I'm at it.
tl;dr: wrote some js, felt good2
about six months ago i posted that i was accepted into and starting at a coding bootcamp. next week is the last week of curriculum for me before i can choose to be a teachers assistant or finish my capstone project and graduate!
some basic info about the course i took:
- 6 months (3 months web dev 2 months CS 1 month capstone project )
- starts by learning the MERN stack
- includes noSQL and SQL dbs
- transitions into C and then python for computer science
- includes basic security info
- lots and lots of algorithm practice
- lots of job readiness stuff (resume writing, linkedin, etc, but i havent done that yet)
- lots of portfolio-able projects throughout the schooling experience
- previous cohorts have something like 40% (after 1month) and 70% (after two) job placement rates (rough estimate)
let me know if anyone is curious about anything related and id be happy to answer what questions i can! :)6
Client is a group of designers and asks for a website reskin, we made the previous one.
They spend like 4 months fixing up their design and after they're done, we developer look at it and decide what can be done and what can't be done and we go on like this for a few days.
At the end, I begin the development of the website, the data structure is already done, it's there and it's working.
The design is there, we all asked to not modify ANYTHING about it.
After I finish making the website, which is kinda unusable bc of the UI, they decide to completely redo the about page (which took like 3 days to get done)
After all it's done they just say "ok, now we gotta just add animations and transitions between all of the pages"
It took like 3 months to finish...
Is it too hard for clients to actually have a specific idea on what they want to do?
more like a combination with browser incompatibility. i designed a neat webapp with transitions and stuff only to find it didn't work in the desired browser.3
I graduated from my High School last Spring, and since then as a part of a huge overhaul of the education systems, they decided to put the school into the 21st century. The problem? They're doing it all wrong. Every school in the district is acting on its own, making transitions from one grade to another painful. The middle school purchased a cart of iPads despite the fact that Elementary schools use Surface, and the High School uses 2-in-1s. But what makes it worse is the services. The High School used Office365 and OneNote, while the Middle School uses Google Classroom and cloud storage. If the school board wants to make education simpler, modern life, and efficient, the least you could do is have everyone on the same page. Right now, costs are higher, grades are confusing, and efficiency is lower. Each teacher pretty much fends for themselves. I volunteered to help them sort this out by being on the educational committee in charge of the decisions, but I graduated and they felt like they were doing fine. Seriously?1