Before using redis: pshhh Ive made it this far without it

After using redis DB, pubsubs, and message brokering: how in the fuck did i ever get by without this ?

javascript is just my favorite thing to work with but man i really need private properties and interfaces and I need them natively, not some subset typescript BS.

Functional or not, data transfer objects are a must.

1500 line factory

React native: Is a bare workflow better or Expo for my first time building with it? I've already gone with expo quite a bit of the ways and im finding that I have to use expo's libraries (location, permissions, ext) if i want my life to be made easy. Cause i cant use react-native cli to link libraries automatically or open them in xcode to link manually sense they're not technically xcode apps.

Is that the only answer with expo is to just use all the expo libraries in effort to stay compatible and not handle more overhead ?

Eslint throws a fit over null coalesce, wtf?!?

Im learning ALOT about C# these few months because i believe diving into more strict typed languages is a requirement to be a more well seasoned dev. With my journey I am leaving a nice trail of C# complaints. This sums up my frustration with the language and set of libraries. Above is a C# websocket handling some json sent over the line. Below is a node.js snippet setting up the entire connection and handling the return. The C# snippet is a compilation of 8 different 3rd part tutorials that I pulled together to make work for me. The node snippet is straight from the packages documentation. The native node.js implementations documentation is even better than the 3rd party packages docs. I highlighted the portions of the C# code that frustrate me to no ends. Without copying and pasting from different examples that implement it in numerous different ways, how am I to know how to instantiate a buffer ? I need a result and a getBytes method. I dont need to go read RFC6455 and implement it step by step myself to make a websocket handler. I would like to think we have evolved to the point of offering simple websockets.

Ok .nets websocket implementation alone is about to have me drop the whole framework. I have a switch over all possible URLs in a middleware that checks if it’s a websocket request and then call my websocket handlers..... either that or use signal R 🤢. And I can’t use signal R without their magic client package 🤮. .Net is pissing me off more and more by the day.

Got an interesting approach or question about how to approach an idea:
i need users on an IOS app, while on a certain map view to constantly update coordinates in redis everytime their location changes. I also need these users to get updates each time another users updated coordinates are updated a with lat/long within a defined proximity of theirs.

For a POC, would it make more sense to fiddle with SignalR (.net) or socket.io (node) to implement a websocket based approach or would it make more sense to build a poller for constantly retrievin new user coordinates ?
Updating coordinates is simple cause IOS has an event for when their coordinates change so I know when to update redis but as far as keeping the user updated with other users, im not sure the best approach.

Yes after months of writing this .NET core 3.1 API, I am still going back and rewriting the Auth flow.

I talk to a lifelong .Net Guru yesterday to get advise about JWT flow with .NET. His take in summary:

"Oh haha yeah all of these settings you kinda just copy over an forget about them over time. They change drastically between every version anyways. 2.0s approach is so different than 3.0-3.1s. "

We then proceed to spend hours trying to copy other peoples solutions and satisfy the type requirements for different services.

Guys look im trying really really hard to get into .NET. Harder then i should try. I come from .Node & php where you import a JWT library, you get the creds, check em and call on function to issue an Bearer token. You write a 5 line middleware function for getting teh claim and fetching the user into global scope and done.

This has been an ongoing nightmare and im about sick of it. I dont need a framework with an over-opinionated, ever changing way of handling auth.

OTHER FRAMEWORKS ARE SCAFFOLDING THIS SHIT FOR US ALREADY!!! ITS THE POINT OF A FRAMEWORK!! TO NOT HAVE TO REINVENT THE WHEEL!!

.NET needs to get its shit together. Most everything else about the framework is proving to be pretty rad though. Im about to get into SignalR though and im sure ill find equal frustration there.

yall really gonna bitch about javascript and then go write some ugly ass Haskell or Closure ??

Is there a dev out there that actually prefers angular over react ? When devs talk about react they talk about all the possibilities, combinations, different paradigms, different approaches. Their own unique processes and toolings combined for the best solution. With angular its angulars MVC paradigm, angulars http module that makes you use rxjs, angulars redux module. HOW BORING!!

How my days going. Why would anything ever have to come to this?

Merger!!!! More like absorbing competition but using the word merger 😁

I need someone to relate with me

This crazy ticket finally got put into integration testing after coming back from testing 6 different times with problems. Its an issue with lots of race conditions and machine dependent problems. Im so proud that its finally going to staging after all the hardship and then they find a problem in staging and have to revert it out. Im devastated. I look like a fool for failing this ticket yet again. I cant even find a fix for it quick enough cause its such a difficult process. I feel like an absolute failure today.

Only thing worse then 30 js frameworks is 30 js testing frameworks

Learning to write unit tests for angular 1.x 😄, why?... Cause I have to hahaha. Learning how to do something ridiculously complex for a framework I will never see again after this is replaced. Maybe I’ll be able to pull some concepts form it at least or be able to say “oh this testing suites nothing I use to work with angularjs stupid bullshit” or something

The quality of developer you hire to greenfield or implement feature sets dictates the amount of help you will hire in the future to handle customer support fixes both on the engineering side and CEM side

STOP WRITING CRAZY FUNCTIONS FULL OF INSTANTIATIONS THAT I NOR ANYONE WILL EVER BE ABLE TO WRITE UNIT TESTS FOR!!! STOP calling static factory methods that spawn up who knows what in mid function as if Im actually going to be able to mock such a dependency. Better yet, practice test driven development so we don't end up in this mess again

My first of "Stop doing" series of rants:

STOP WRITING WRAPPER FUNCTIONS AROUND NATIVE FUNCTIONS THAT DO NOTHING OTHER THEN PASS PARAMETERS THROUGH.

If its not significantly configuring values prior to using in the native function or combining several results, leave it be so NEW DEVS SUCH AS MYSELF aren't having to learn your shitty naming conventions wrapped around every native function to the language. Im a JS dev, not a Dave's witty web stack dev.

Need some advice on how to handle a unique problem. Im using Googles location services api with react natives geolocation service to fetch a clients location and gather more details on it. I essentially need users to be able to see other users on a map within the live time of their location. Im thinking about figuring what users are nearby to show by storing each users location in redis until the end of their session and fetching within a certain longitude/latitude range of the given user's location. Is this a solid way of looking up local users or is there a more solid approach to mapping users.

Im such a huge fan C# now after working on my own little api for the last month. With strict typing im not running api call after call after call with print_r or console.log everywhere trying to debug everything. 9 out of 10 times it just tells me before I even compile. Thats such a foreign idea to me and yet so beautiful. Now I still think working with websockets and the such is easier with node but man entity core is a breeze, .net core is as agnostic as I had always hoped .net would be. Im simply loving every moment of it. My rant is that ducktyped languages will now feel very burdening after working with C#.

Wow I finally got .net cores JWT middle ware working. Really nice to work with once it’s going.

Open the country back up or match businesses shut out on their income dollar for dollar. Period

My company now of three months has proven to be the most perfect environment for me to pursue what I would call a long road to senior level expertise in software development. They say you can only grow as large as the room your in will allow. Everyone around me has 30+ years of experience and is ridiculously intelligent. Theres not one feature that does not correctly use sufficient design patterns,. Code is actively refactored to the point that it reads like a book. New technologies are pursued, btw dont tell me mongo cant be proficient in a large environment, these guys have proven differently (it just takes the right abstractions to keep it safe). I encourage every dev to find that team that pushes you to be more.

Im starting to think fat client architectures a dumb idea. For any given application how many times is the api rebuilt? And how many times is the client rebuilt. You have a client for IOS, android, web, desktop, maybe smart watch. With that in mind why would i pass all of the heavy functionality off on the client ?

We heard you like being declarative. So we put declaratives within yo declaratives within yo declaratives

So front end engineer is a relatively new role if working with spas is a requisite for the title. It’s no wonder everyone on here’s like “ya f front end man I just write what’s needed to fix the issue” “f js” “f it’s not being reactive”. It’s so clear now. Today’s front end tooling just hasn’t sat long enough with everyone. I get it. The paradigms surrounding reactive components and the hierarchies and the state management resemble hardly anything on a server side application. Coming from a Traditional server side app with fresh eyes, it can be an absolute cluster fuck to wrangle in your mind. And with that I’m sorry for all you old fucks that have to learn it right in your glory years of development when you thought you were finally past all the “newness” . Guess your gonna have to ask the hipster JavaScript kid with checkered skinny jeans and stupid beard for help with Redux

Does anyone or has anyone struggled with Understanding get rebase ? I just can’t grasp everything it does in practice. I’m theory it makes sense but when someone tells me to debase off something to make something happen, I’m lost

I’ve been writing a node.js service that automates kubernete commands so users aren’t having to constantly call for newly generated pod names and then container names and so on so forth.

For instance it would ask you if you want to delete a pod, Exec into a container, fetch logs on a pod. It would list all namespace, pods and containers for those pods for you to pick from by just providing a corresponding number.

With this kind of service assist anybody who is constantly having to restart, delete, fetch logs and delete with Kubernetes?