I've never had a great experience working with designers, but this one might be the laziest! Props if it's for a friend and unpaid though.

Its Friday, you all know what that means! ... Its results day for practiseSafeHex's most incompetent co-worker!!!

*audience: wwwwwwooooooooo!!!!*

We've had a bewildering array of candidates, lets remind ourselves:

- a psychopath that genuinely scared me a little
- a CEO I would take pleasure seeing in pain
- a pothead who mistook me for his drug dealer
- an unbelievable idiot
- an arrogant idiot obsessed with strings

Tough competition, but there can be only one ... *drum roll* ... the winner is ... none of them!

*audience: GASP!*
*audience member: what?*
*audience member: no way!*
*audience member: your fucking kidding me!*

Sir calm down! this is a day time show, no need for that ... let me explain, there is a winner ... but we've kept him till last and for a good reason

*audience: ooooohhhhh*

You see our final contestant and ultimate winner of this series is our good old friend "C", taking the letters of each of our previous contestants, that spells TRAGIC which is the only word to explain C.

*audience: laughs*

Oh I assure you its no laughing matter. C was with us for 6 whole months ... 6 excruciatingly painful months.

Backstory:

We needed someone with frontend, backend and experience with IoT devices, or raspberry PI's. We didn't think we'd get it all, but in walked an interviewee with web development experience, a tiny bit of Angular and his masters project was building a robot device that would change LED's depending on your facial expressions. PERFECT!!!

... oh to have a time machine

Working with C:

- He never actually did the tutorials I first set him on for Node.js and Angular 2+ because they were "too boring". I didn't find this out until some time later.

- The first project I had him work on was a small dashboard and backend, but he decided to use Angular 1 and a different database than what we were using because "for me, these are easier".

- He called that project done without testing / deploying it in the cloud, despite that being part of the ticket, because he didn't know how. Rather than tell or ask anyone ... he just didn't do it and moved on.

- As part of his first tech review I had to explain to him why he should be using if / else, rather than just if's.

- Despite his past experience building server applications and dashboards (4 years!), he never heard of a websocket, and it took a considerable amount of time to explain.

- When he used a node module to open a server socket, he sat staring at me like a deer caught in headlights completely unaware of how to use / test it was working. I again had to explain it and ultimately test it for him with a command line client.

- He didn't understand the need to leave logging inside an application to report errors. Because he used to ... I shit you not ... drive to his customers, plug into their server and debug their application using a debugger.

... props for using a debugger, but fuck me.

- Once, after an entire 2 days of tapping me on the shoulder every 15 mins for questions / issues, I had to stop and ask:

Me: "Have you googled it?"
C: "... eh, no"
Me: "can I ask why?"
C: "well, for me, I only google for something I don't know"
Me: "... well do you know what this error message means?"
C: "ah good point, i'll try this time"

... maybe he was A's stoner buddy?

- He burned through our free cloud usage allowance for a month, after 1 day, meaning he couldn't test anything else under his account. He left an application running, broadcasting a lot of data. Turns out the on / off button on the dashboard only worked for "on". He had been killing his terminal locally and didn't know how to "ctrl + c a cloud app" ... so left it running. His intention was to restart the app every time you are done using it ... but forgot.

- His issue with the previous one ... not any of his countless mistakes, not the lack of even trying to make the button work, no, no, not for C. C's issue is the cloud is "shit" for giving us such little allowances. (for the record in a month I had never used more than 5%).

- I had to explain environment variables and why they are necessary for passwords and tokens etc. He didn't know it wasn't ok to commit these into GitHub.

- At his project meetups with partners I had to repeatedly ask him to stop googling gifs and pay attention to the talks.

- He complained that we don't have 3 hour lunch breaks like his last place.

- He once copied and pasted the same function 450 times into a file as a load test ... are loops too mainstream nowadays?

You see C is our winner, because after 6 painful months (companies internal process / requirements) he actually achieved nothing. I really mean that, nothing. Every thing was so broken, so insecure / wide open, built without any kind of common sense or standards I had to delete it all and start again ... it took me 2 weeks.

I hope you've all enjoyed this series and will join me in praying for the return of my sanity ... I do miss it a lot.

Yours truly,
practiseSafeHex

I got bored so I made this WIP Page

(Props to Mario Duarte for the Floating CSS he made)

This is like the hundredth time that I fucking forgot the motherfucking "s" for "props" 😠😠😠

It is fucking props, props, props

First time I've seen an app which willingly, intelligently, and sensibly turns off its own daily notifications after I never used their app for many many weeks.

Props to the devs for taking into account people like me,who are just too lazy to disable an app's notifications. Also Enki is absolutely incredible for devs so go check it out :D

I almost did rm -rf / as root on my computer, but Ubuntu actually stopped me from doing it, even as root, saying it was too dangerous. Props, Ubuntu. You saved my hard drive.

Just wanted to say cheers to all those coders among you who make sure their login is encrypted, their passwords are hashed and salted, their codes are tested and their forms are code injection safe.

No client will understand what you did, so take my props for it! After all, its our responsibility to make sure software is secure. That's all :)

!rant

props to @dfox and @trogus for uploading their devRant podcast to 5 different plattforms, as well as providing 3 mp3 download links in different bitrates! you can tell this was created by devs, for devs :)

Just saw this in a store window. Props for using a raspberry instead of a pc.. but..

Finally got my duck.
Props to devrant for the one day delivery.

One of the things that make devRant special is it's multicultural nature. Every time I see a photo, it is from another country and even with such different people, we all relate to the same things and that is, my friends, fucking dope. No other social network is like this. Props to devRant!

This was sort of strange to see... but props to Adobe for Order 66'ing their shit.

Props to the devs who made this app, literally does nothing but still have 1 million dowloads and tons of 5 stars.

!Dev but still a work related wtf moment.

A company has lunchtime sessions where people could present their hobbies or interests. All went well until one guy presented about his and his wife's interest in BDSM, complete with props and photos. The sessions were quietly abandoned after that.

My phone is my most reliable computer. It made it to 2000 hours of uptime before I restarted it to update.

Props to Android.

The coolest project I was ever involved on, was when we signed a client in Namibia (we were a South African based company). So I was flown to Namibia for 2 weeks to train the clients etc. I spent about 4 days training the client and I had no more work to do. So the client took me out around town and we drank so much on his tab! He even gave me a bottle of Johnnie Walker Blue, because he doesnt drink Whiskey! The best part of it, apart from exploring their awesome country and pubs, was Mad Max 4 was being filmed in my town, and my client took me to see the yard where all the vehicles and props were situated, because he owned that property! So all in all, it was more of a paid holiday than anything else!

In my first annual review as a developer, I took a copy of the job description I'd applied for and a summary of the work I'd done that year and asked my manager to spot the difference.

I was doing a totally different job, said I was bored out of my mind as a result and expected to leave within 6 months.

Props to him, my job completely changed and I was there 4 years.

Complete and total rant:

You know what fucking confuses the holy fucking shit out of me? DESIGN

I have MAD respect for motherfuckers that spend their days tailoring shit away in CSS, writing custom animations and toggles in JS and ensuring that their HTML is pristine as fuck. I really do and in my opinion they should b getting mad props from everyone, because if they so decide to learn GOOD server side scripting then they are most definitely on their way to create some awesome functional and beautiful shit.

But...

I am not a designer by any means of it. And I know that shit is supposed to look good and work across a multitude of devices. Doing something like that takes me a couple of lines of code (granted, after hours of work that is) that may take a designer way less.

But why oh why do I see THOUSANDS of lines of CSS code for shit that does not take me half the amount of work that it takes other people?
Like seriously. I am trying to emulate the menu that university of Chicago uses(as an example for a lil design practice cuz i suck at it) and looking into their CSS I see thooooousands of lines of code to do something that I did in about two hundred.

So wtf man, do I suck so hard that I am missing some serious shit? wtf is happening? This confuses me, because in my mind it should take me just about as much work as it takes them right?

AGAIN MAD RESPECT FOR DESIGNERS -- If you are a designer reading this please tell me wtf is happening

Props to those who watch tutorial videos by Indian guys at normal speed. Patience is a virtue.

New country, new company, new team, new projects.
I'm supposed to be the TL of a team working on a React project.

A guy in his late 40s celebrates himself as "the senior", he basically just finished watching a youtube thing, React 101 crash course or similar. The other two juniors who did only Wordpress so far venerate him like a god.

The code, of course, is one on the finest pieces of crap I ever had the pleasure to deal with in my life: naturally a bunch of JQuery plugins for everything, no tests, no state management, side effects everywhere, shared state and globals like hell, everything written in ES3/ES5 style, no types, no docs, build and deploy totally manual, deep props drilling at every level... and not to mention the console.log() shipped in prod.

First day, already headache.
Full rewrite start tomorrow.
Hiring real devs as well.

Wrote myself a flight stability controller for a drone I built - used an ultrasonic sensor for altitude so it should've maintained a constant altitude, but I had the throttle increments too high...
Hooked up the battery - off it fucked, hit the ceiling, bounced off a wall, and broke 2 props before I could grab it and yank the battery off.

Protip - if you're building a drone, tie it to a heavy fucking rock for your first flight test!

Happy (late) Halloween, bitches 😈🎃👻

Props to anyone who knows what this is 😝

I gotta share my favorite ever SO question that I flagged... here's a screenshot. Props to the person for having the balls to post it.

I just love how liferay keeps finding ways to surprise me...

Customer: need to fix this security issue
me: ok
me: fixed. Testing locally. Works 100%.
Me: testing on dev server. Works 100%
qa: testing on dev server. Works 100%
me: all good. Deploying to preprod
customer: it doesn't work
me: testing preprod - it doesn't work.
Me: scp whole app to local machine. App works 100%.
Me: preview loaded liferay properties in preprod via liferay adm panel. All props loaded ok.
Me: attach jdb to preprod's liferay to see what props are loaded. Only defaults are used [custom props not loaded according to jdb]

me: is there some quantum mechanics involved..? Liferay managed to both load and not to load props at the same time and the state only changes as it's observed...

So when our campus expo happened, I immediately went to the apps I critiqued last time when I was a a panel judge in the IT dep’s oral defence. Fair enough, this happened:

- The app I failed (the tilting avoid boxes shit app) actually got optimized and got the first time user tutorial I was looking for. I was short of relieved of them listening and kept going despite me failing them (props to the girl btw)

- Second app was the same as before but added my recommendations, nonetheless still a good app

I am nothing short of amazed they actually listened to me so I think that’s a win for my part

If you are one of all those awesome developers and hackers and I only understand 20% of your rants then props to you and keep scrolling :-D

But if you are a young developer, fresh grad or just learning programming I have an idea, how about a mentor?

This literally just pop in my head right now while cleaning my kitchen!

I'd be learning along your side and also having lots of fun! I don't have any formal experience providing mentoring but have some education credits and patience.

I'm gonna stop the sales pitch because it's annoying even me! but Idk, i just thought that maybe there's someone else out there interested in mentoring services :P

So yesterday ended with me becoming a first responder in front of my house. Talk about a crazy day.

Guy sped up down my very short dead-end road and flipped a school van down the embankment. Thankfully there were no kids in the van and the driver was okay.

I've never had to run into the scene of an accident before, and what the brain does in a time of crisis like that is absolutely amazing.

Feeling everything but the immediate need drain away. It was like time was slowed. I took in all the information of the scene and somehow worked fast while also double-checking every action I did.

I remember hesitating for a moment, worried about what I'd see. School students on the back. Would I see injured or dead children? Body parts? I remember saying "Fuck it" and running down the embankment and that was about it.

So serious props to any of you who read this that also volunteer as EMT or fire/rescue. I've long considered doing that myself and I may very well step up now that I've had first-hand experience.

And now for the requisite joke: Usually I only have to help out when Windows crashes. :)

Why do people feel so compelled to create their own custom components when the component library you're already using HAS ONE ALREADY?!

You can change the styling and animations using CSS and props. Stop building buggy shit from scratch.

!rant

This morning, I thought I'd give devRantron a try, and man, I'm not disappointed.
Since I'm always at my computer, I rarely check my phone and now that we have a proper desktop client, I can finally shitpost while sitting at my desk. :v
No seriously though, this app is awesome.

Props to Tahnik and the other guys who worked on it.

I can't use Javascript object destrucuring in react components because a colleague doesn't like / understand it for some reason.

So instead of:
({ something }) => {
return (
<div>{something}</div>
)
}

If have to use
(props) => {
return (
<div>{props.something}</div>
)
}

Its no big issue, but I hate it.

Q: What did the proud React component say to its child?

A: I've got to give you props

I really have to say, huge props to the shutdown speed of Mint. This thing shuts down in less than five seconds.

Why I try to ALWAYS use semicolons in JS:

In short, weird shit happens sometimes

An example:

So I'm doing a small project for freeCodeCamp, working with the Twitch API. I decided to make an array on the fly to append a few elements to a documentFrag in order after setting all my props. Forgot a semicolon. Apparently, Babel transpiles this:

info.innerHTML = (``)
[span, caret, info].forEach(elm => frag.appendChild(elm));

to this if you omit the semicolon:
info.innerHTML = ' '[(span, caret, info)]

this is why you should avoid relying on ASI, you're going to have to remember them in other languages out there, so for your own sanity, might as well get used to them. Just thought I'd share--who knows, might help a JS newb out there somewhere.

Lets remind someone that weekends are NOT for not coding

(props if you recon whose rantfeed that is)

wow... the regular react community sucks...

where with react-native 3rd party libraries/components have very clear and detailed docs, the normal react libs out there are like:

20K starred component
"here is a .txt file with some props, TS? yea we use it, but everything is just set to ?: any"

quite the shame :/

Me: What if I use navigation props in EF Core, what might go wrong?

*tests API call*
*120 seconds later finally got result*

Me: I better undo my changes and stick with 2 seconds response time O_O

Context: New to typescript. Writing a thing, doing it for work, good opportunity to stretch my dev legs. Using a propriety lib, alternatives not an option.

Rant begin:
SOOOO, who the fuck thought THIS was a good idea:
1. Lib has minified react in dev (because closed source) meaning no downstream errors AND the entire premise of the lib is that a widget is a react component, so I'm writing typescript react the entire time without downstream errors
2. SHIT docs. By that, I mean there's an API reference page that's so sparse there's literally a set of CRUCIAL interfaces that only say the word 'Interface' on them. That's it. that's what i get. It's an interface. NO FUCKING SHIT SHERLOCK, what the fuck is it though? What's its purpose? Is it an interface for a dog? A dog that has a 'shit' property? or a cat? or a cat eating dog shit? Nobody fucking knows - the docs sure as fuck don't care.
3. No syntax highlighting - editors, IDEs (i've tried a few) can't even find the lib inside this environment, so Code and everything else thinks I'm importing shit that doesn't even exist - so no error prediction, code completion based on syntax of the library, none of that.
4. There are some EXTREMELY basic samples - these samples exclusively use React classes - no function components, no hooks, nada - just classes and even perfect replicas of the sample code display erratic behavior like errors about missing props, so that's mostly FUCKING USELESS
5. And this... this is where the straw breaks the fucking camel's back... there's no... there's no hot reloading... Do you know what that (in conjunction with the previous 4 fuckups) means?

When I write anything or I fuck up (which of course I'm doing every time I write half a line because how the fuck?) I have to restart the client and server EVERY FUCKING TIME and manually test to see if the error (THAT ONLY GETS REPORTED IN THE LOCAL UI) is gone or different.
Then, once I see the error, it isn't an error: it's the minified React error-decoder link and guess what? It isn't really clickable a link OR copyable, meaning that every FUCKING time I get a new error, I have to MANUALLY TYPE A FUCKING 50 CHAR URL TO FIND OUT A GENERIC REACT ERROR MESSAGE WITHOUT A LINE NUMBER OR ANY FUCKING CONTEXT. I HAVE TO DO THIS CONSTANTLY TO SEE IF ANYTHING I'M DOING EVEN WORKS.

6. There's no github to complain to the maintainers or search for issues because it's NOT FUCKING OPEN SOURCE so there is literally nothing to be fucking done about it.

This is due in a week and a half, found out about it last Friday. How's your day going?

PS: good to be back after a long respite from dev ranting.

Props to slack for this. This is awesome!

Next to a large pond / lake, trying to connect to & debug & rescue a robotic boat that had gone haywire, flipped upside down and was somehow just spinning in circles.

Eventually realised it was spinning in circles because its props were stuck at full power in alternate directions and acting as fans, so eventually decided to just use them as fans to blow it upside down back to shore.

Suggestion please!

I work basically on native android applications. From last week I started exploring cross platform and chose React native. I have zero knowledge on JS. And now it seems very hard to grab. I started a project and learning whatever I'm needing on that purpose. Some props I'm shooting blindly and components I don't even understand clearly how they are working.

Please suggest me a convenient way or guide me with some resources to alleviate my frustration! Pretty please!

Is it just me or has the usefulness of Google search been SEO'd to death? At this point only Bing and even freaking Brave Search are providing results that are related to what I'm looking for. Even Gigablast does a better job than Google sometimes (props for open sourcing the backend, Gigablast maintainer guy)

Spent sometime looking for questions to answer on StackOverflow for the first time in around 2 years... Mother of God the questions have gotten even worse - and there's even more of them.

Quickly decided to leave it for another time, with the level of stupidity out there I kinda get why almost all the regulars have become assholes.

white house props up "memory safe" languages

cloudflare releases all in one network connections library pingora as open source (for rust, a memory safe language)

cloudflare is sus. they were hosting that Ukranian kill-list that was routed through Langley/FBI. when contacted by multiple people, they ignored the violations and complaints to take down the website

SEE IT WAS SUS

so I guess if you can put spyware on the low level and convince everyone to move to it it'll give you an Intel advantage

cloudflare being a CDN sure would give the American gov a lot of metadata to work with

and ofc businesses just want something that works, so on we go

v0.0005a (alpha)
- class support added to lua thanks to yonaba.
- rkUIs class created
- new panel class
- added drawing code for panel
- fixed bug where some sides of the UI's border were failing to drawing (line rendering quark)

v0.0014a (alpha) 11.30.2023 (~2 hours)
- successfully retrieving basic data from save folder, load text into lua from files
- added 'props' property to Entity class
- added a props table to control what gets serialized and what doesn't
- added a save() base method for instances (has to be overridden to be useful beyond the basics)
- moved the lume.serialize() call into the :save() method on the base entity class itself
- serialized and successfully saved an entities property table.
- fixed deserializion bugs involving wrong indexes (savedata[1] not savedata[2])
- moved deserialization from temp code, into line loading loop itself (assuming each item is on one line)
- deser'd test data, and init()'d new player Entity using the freshly-loaded data, and displayed the entity sprite

All in all not a bad session. Understanding filing handling and how to interact with the directory system was the biggest hurdle I was worried about for building my tools.

Next steps will be defining some basic UI elements (with overridable draw code), and then loading and initializing the UI from lua or json.

New projects can be set as subfolders folders in appdata, using 'Setidentity("appname/projectname") to keep things clean.

I'm not even dreading writing basic syntax highlighting!

Idea is to dogfood the whole process. UI is in-engine rendered just like you might see with godot, unity, or gamemaker, that way I have maximum flexibility to style it the way I want. I'm familiar enough with constructing from polygons, on top of stenciling, on top of nine-slicing, on top of existing tweening and special effects, that I can achieve exactly what I want.

Idea is to build a really well managed asset pipeline. Stencyl, as 'crappy' as it appeared, and 'for education' was a master class in how to do things the correct way, it was just horribly bloated while doing it.

Logical tilesets that you import, can rearrange through drag-n-drop, assign custom tile shapes to, physics materials, collisions groups, name, add tag data to, all in one editor? Yes please.
Every other 2D editor is basic-bitch, has you importing images, and at most generates different scales and does the slicing for you.

Code editor? Everything behavior was in a component, with custom fields. All your code goes into a list of events, which you can toggle on and off with a proper toggle button, so you can explicitly experiment, instead of commenting shit out (yes git is better, but we're talking solo amateurs here, they're not gonna be using git out the gate unless they already know what they're doing).

Components all have an image assignable to identify them, along with a description field, and they're arranged in a 2d grid for easy browsing, copying, modifying.

The physics shape editor, the animation editor, the map editor, all of it was so bare bones and yet had things others didn't.

I want that, except without the historic ties to flash, without the overhead of java, and with sexier fucking in-engine rendering of the UI and support for modding and in-engine custom tools.

Not really doing it for anyone except myself, and doubt I'll get very far, but since I dropped looking for easy solutions, I've just been powering through all the areas I don't understand and doing the work.

I rediscovered my love of programming after 3-4 years of learning to hate it, and things are looking up.

so my friend and I are canvassing NLEs for our guys at the Post Production squad in our project (we were in charge in infrastructure). We looked at Premiere since it's kinda ok until we found Black Magic Design's Da Vinci Resolve.

First of all, I was suprised with the price. 299 for the Studio Version? Holy fuck, that's cheap as hell! Then there's a free as in free software version which has the core editing features with 1080p rendering. So we grabbed that and kinda suprised it requires postgres but as seeing Resolve having collab and render queues, it makes sense.

Installed them on the PCs the postprods gonna use, they were amazed. We literally saved 500 bucks for an NLE. When they asked how much is it. Our reply was:

"That's free".

and there was silence...

"And it's also 299 bucks for the cooler version".

And silence still ensued.

Guess our guys wasted alot of money on a pipeline that is cheap as hell but more jam-packed than any other NLE found in the market.

Props to you BlackMagic Design.

Outside for the first time after about 48 hours of straight coding in React.
Why can't I change the property of people by supplying props to them?!

It's always amazing to fire up a PS2 game and go "Wow... this PS3 game looks great!" an hour later before realizing it's still a PS2. Take Final Fantasy 12, for example: the environments are massive and gorgeous, all the textures look nice, and it's a MASSIVE GAME. Sure, in some areas the environment flavor stuff has really noticeable draw-in and there's no AA and some of the area textures (buildings, floors, the like) are noticeably low-res on close inspection and it's only running at 480i, but when playing, lack of AA and resolution are basically invisible and in most areas the env flavor draw-in is still really far off. It *feels* like a mid-life PS3 game, which the creators deserve mad props for. (I have yet to try upscaling via homebrew, when I get a hackable PS2 i'll see if it looks any better at 720p or 1080i.)

This isn't the only game like this, I have at least 4 that look like PS3 games on-disc, and like 12 more waiting for a hacked PS2, this isn't uncommon. They crammed so much flavor and life into 40MB of total VRAM and it's absolutely fucking nuts.

Even if he's a younger guy than most other examples, my mention is:

Jordan Walke

He's the inventor of React, which probably changed the way to write (web-)apps for a lot of people and was based on a prototype written in StandardML.

He's also created ReasonML which is not only in many ways a more fitting language to write React, but also a good systems language (props to OCaml and it's unbreakable type system). Many React concepts/patterns have their origins in functional language concepts, including reducers and hooks.

How do you feel about using TypeScript with React? I appreciate the benefits, but, as every snippet of React code everywhere on the web is vanilla JS,I just don't want the cognitive overhead.

Yes, I know TS is JS, but, if I'm not going to use the features, why bother? I'd want to strongly type props, state, etc.

What's the status of TypeScript support in the React ecosystem (eg Router, MUI, etc.)?

I'm kinda hoping Reason will get some traction as the type inference is much better, but, will that happen? Or is that going to fizzle so it's a choice between TS and JS?

Appreciate any thoughts on this---including those from anyone who's in the same boat.

Looking for views on TS in React ecosystem---no need to sell me on TS in general.

I'm trying to get into react for side projects but my java and backend background in general really make things tough. Let's say I have a few data manipulation functions that I want to extract to a separate service and inject it using react hooks (since that's what everyone is using nowadays apparently). I can see it being much more elegant than props, but all the examples I can find resolve around passing state here and there, not passing actual dependencies like a stateless service. Any ideas how I should solve this?

When Game Developer is out of Idea of Props.
Just put the Code instead whatever.
Game: Burger

I really feel lost in the world of freelancing, I mean I literally have three jobs on the go so barely any pressure and yet I'm cocking up my time estimations and mixing up code for each site, and giving incorrect predictions for completion, so basically I keep ending up working for free. Freelancers of the depths of devRant, please help! How do you manage to maintain a work life balance? Is accurate predictions and time management just something that comes with experience?

Also huge props to you for being able to keep your mentality!

"Hey guys I need help I struggle with asynchronous stuff and I need to pass props loaded via Ajax, I can't manage to apply this solution (link to another SO question with complete and structured answer), can you guys help ?"

*30 seconds later, question is marked as duplicate, the answer has been given here (link to same question I was refering)*

I love the React and Sails docs. The contents are human-readable. Perfect for idiots like me since most docs are $h!+5%&* (hint: Git).

Created redux store, wrote two reducers with multiple actions, thunks, couple of react components to dispatch some actions, bound state to props, bound actions to props, worked 4th time!

Result!

My brain hurts from trying to figure out this unit testing crap. Is it just me or is it really a struggle to test your front-end code? I'm using jest and enzyme to test our React app but complicated parts of code with multiple state changes or calling props is making my life a living hell. I mean I usually just debug by console logging everything and it works lol...but my fucking boss has forced me into writing this unit testing crap. FML.

Doing someone else's Code Review in my project: "You must retain the holiness and piety of the code you write by following PascalCase naming for files and kebab-case naming for CSS variables. Avoid using duplicate strings by declaring enums in a constants.ts file and using that all throughout the app"

During my own Code Review in someone else's project: "WHAT THE FUCK DO YOU MEAN I CANNOT PASS FUNCTION REFERENCES AS PROPS TO A REACT COMPONENT AND ALWAYS NEED TO INVOKE IT INSIDE AN INLINE FUNCTION FOR THE PROP."
"WHAT KINDA FKIN DRUGS ARE YOU ON TO USE snake_case IN TYPESCRIPT DID YOUR MOM DROP YOU ON YOUR HEAD WHEN YOU WERE BORN YOU SACRILEGIOUS PIECE OF SHIT"
"WHAT DO YOU MEAN I SHOULD USE BOTH SINGLE AND DOUBLE QUOTES FOR IMPORTS AS PER LOCAL OR GLOBAL; I'LL SHOVE THE SINGLE QUOTE UP YOU WHERE THE SUN DOESN'T SHINE YOU FKIN DEGENERATE MORON"

As much as I do believe in self righteousness of my own coding conventions over others (I might be slightly better than others but I really can't claim good authority because I've had my lapses in conventions too; and being one of the newer members of the team certainly doesn't help, despite my boss supporting my initiative), I guess it is high time we bring in some already established code conventions in the team that is finally big enough to warrant them. Maybe AirBnB.

Props to Apple for having a craptacular purchase system. There are unknown purchases on a person's account I'm looking at. Doesn't say what device it was purchased on, can't even find history of the apps purchased, but a subscription to a service is charged to the account. All of which supposedly isn't supposed to be there.

So this "senior" programmer tells me that redux should only connect to the upmost react component and then IT should pass props down..... Like why even use redux then? WTF

As I started learning React, I found the allure of declarative style of programming appealing. I try to avoid maintaining multiple state variables for data that can be derived from the base state itself that's stored in the redux store. It works wonders when I have to change something; as I just need to make changes to one function in the utils folder and that change is implemented across the whole app, rather than change the instances everywhere as was the case when I initially started working on this project after the previous dev left.

But I see myself redefining a lot of computed values everywhere, and if I just try to define them in the root component, I'll end up with a huge list of props being passed to a couple of components. Shifting it to the utils folder helps a bit, but then I find myself defining even the simplest of array filtering methods to the utils folder.

Is this need to define computed values everywhere a trade-off that you need to accept when you write declarative code, or is there a workaround/solution I am missing? As of now, the code-base is much better than how it used to be when they had a literal Java dev work on React with their knowledge of Java patterns being used in a framework that is the polar opposite of OOP, but I still feel like there's room for improvement in this duplication of computed values.

Say what you will but React JS development is utterly exhausting. Every React project is a totally new stack and there is no consensus in the ecosystem.That is how I feel after having worked on 5 big SPA React JS projects over the course of 5 years.

The structure of these projects was all but similar: most used HOC's, some render props, functions-as-a-child, hooks or rather component lifecycles, some used container-components, some Redux, others sprinkled business logic & state all over, and yet others use a mix of server-side rendering and "hydration"...

I dangerouslySetInnerHTML on LazyExoticComponents, and dared not useEffect on the DO_NOT_TOUCH_OR_YOU_WILL_BE_FIRED root property. Hooks embrace functions, but without sacrificing the practical spirit of React, you see.

I didn't make this up. It's verbatim from the code and the docs.
This is not web development, this is at best a tedious fantasy multiplayer game or at worst, a costly joke.

Been working frontend on a very large ASP.Net Core project with React. The company is a multi national oil company. I asked for some documentation on their React components, like where is the props, why is this component showing this side-effect and is there a component for X and Y so that you won't have to pay me in order to dig around in the codebase? They told me they will document the frontend when the project is finished (whenever that may be?)

So basically, there won't ever be any documentation then.

To ship a package of two USB cables from one US city to another. What could be easier for a large company? Well, hold on a little.

I ordered two fucking cables from fucking Nomad at 15TH OF FUCKING JULY, and they are still not shipped. Here's how their customer support works: you send them an email, they reply in like a day or two, and that's it, that email thread is abandoned. They won't visit it again. You should write a whole new message where you say "hey, the previous time you said me X, so I want you to do Y then", and the message title should be different, otherwise they'll ignore it.

My roof is under construction now. When it was raining and there was a rain both inside and outside my apartment, I filmed it and an article about the situation was in my local newspaper in like 20 minutes. Russian government organizations are notorious for ignoring people's requests, shutting down their telephones and doing other shit like that, but in one day I managed to collect the foundation of overhaul, my utilities provider, the foreman of the organization responsible for roof repair, his supervisor and the actual guy that did that job. That same day, they all was at my doorstep, collecting the evidence, signing papers, apologizing, threatening to sue each other and collectively signing a document that states that they owe me either a full financial compensation or an overhaul. I managed to do it in the country where you throw an empty plastic cup at a cop and go to jail for it for five years.

Nomad, tell me, what exactly is stopping me from going full Jackson Pollock with a .45 on your company all over the social media (props to @SortOfTested)? You think I can't handle a mediocre iPhone case manufacturer?

Think again.

Why the fuck do consultants / noob types LOVE using fucking props in react components. This app is complex, just make a fucking redux slice and use that. I'm not passing 23904 props to a component to get it to render. God

In most businesses, self-proclaimed full-stack teams are usually more back-end leaning as historically the need to use JS more extensively has imposed itself on back-end-only teams (that used to handle some basic HTML/CSS/JS/bootstrap on the side). This is something I witnessed over the years in 4 projects.

Back-end developers looking for a good JS framework will inevitably land on the triad of Vue, React and Angular, elegant solutions for SPA's. These frameworks are way more permissive than traditional back-end MVC frameworks (Dotnet core, Symfony, Spring boot), meaning it is easy to get something that looks like it's working even when it is not "right" (=idiomatic, unit-testable, maintainable).

They then use components as if they were simple HTML elements injecting the initial state via attributes (props), skip event handling and immediately add state store libraries (Vuex, Redux). They aren't aware that updating a single prop in an object with 1000 keys passed as prop will be nefarious for rendering performance. They also read something about SSR and immediately add Next.js or Nuxt.js, a custom Node express.js proxy and npm install a ton of "ecosystem" modules like webpack loaders that will become abandonware in a year.

After 6 months you get: 3 basic forms with a few fields, regressions, 2MB of JS, missing basic a11y, unmaintainable translation files & business logic scattered across components, an "outdated" stack that logs 20 deprecation notices on npm install, a component library that is hard to unit-test, validate and update, completely vendor-& version locked in and hundreds of thousands of wasted dollars.

I empathize with the back-end devs: JS frameworks should not brand themselves as "simple" or "one-size-fits-all" solutions. They should not treat their audience as if it were fully aware and able to use concepts of composition, immutability, and custom "hooks" paired with the quirks of JS, and especially WHEN they are a good fit.

An old post from medium. I found it really funny. BTW my text field component has more than 20 optional props 😎

The spring framework, it took a pain in the arse language {java} and turned into something reasonably good again! Props to Rod Johnson on that one

So been doing a freelance project for the past week, small backend API with a front-end, thought I'll give react.js a shot and actually learn it (know a bit of the basics) so using MERN including tailwindcss.

Built the API in a few days, quick and easy. Down to react, not going to lie. Once you dive into it, it's really nice to use. Just tackled a contact form and a few dynamic pages using props, state etc today. Now onto the rest of the site including the the Dashboard to CRUD records.

Still have a lot to learn. But given what I've learned so far. Don't see it taking too much longer.

Famous last words though 😅

First dev job was not really a job but rather an internship... I was completely new to Spring and Jersey Java and i was given a 5 points story "which turned out to be 8 later on" to consume a RESTfrl webservice... Manipulate the response and create an Excel sheet at the end... But the Excel columns n rows had some complicated logic to determine colour, font, borders, alignment and a lot of other props..
Got it done "code was a bit ugly" and dev lead was satisfied and told me I actually knocked out an 8 points story on my own... Team velocity was 5 points story per Dev.
Now im a full time Developer therr

Making good money, started to think more logically in day to day situations.
Also realising how stupid people can be (read that in someone else's rant, props to the op)

Last week I conducted a FE React-JS tech interview (high-level, no coding challenge) with a potential new hire. He knew his stuff in React 16.8+ but I was baffled npm install was the only npm command he could name, he'd never heard about semver, never used SASS, and didn't have any Nodejs exp. I asked him to name a tough situation he encountered and solved in React, and he said "too many re-renders, so we used useMemo and useCallback" but that's kind of basic and it was evident he didn't understand this meant passing props by reference under the hood. So I wrote a very mixed report, but this is only the 3rd interview conducted. Was I too harsh? To me this signaled a lack of curiosity (especially for a self-taught programmer which he was). My manager was kind of disappointed about the guy following my report.

Finally im starting to get hang of how nextjs works. Still no idea how query params work, routing api calls, the proper structure, useEffect vs useState, SSR vs static props, etc but i wrote the messiest spaghetti code youve ever seen, and it works! I built a frankenstein. And its alive. Cleaning this shit up is the least difficult part

WOW -__- they left me to code the SPO Teams website when im coding a Text rpg engine while Over clocked is fixing his tablet while Solario is helping his other friends code his java + lua = andlua mod menus for android Screw ya )=<
@overclockedgd
@Solario360
im not even good at website designs LOL its gonna be a website that wants to commit DDoS iill post the final product and if you survive through the whole website without getting your computer molested props to you =)

How do you guys like to name things, do you prefer being specific/verbose or generic? Say, we have a vue component to which we need to pass props. Would you prefer:

<todo-list todo-model="TodoModel" />

or rather:

<todo-list model="TodoModel" />

For me, the first is easier to search for, the other is more elegant and decouples what is happening from why is it happening.

Vue <router-link> cant parse props data when parsed using path="" rather than name=""

WHAAAAAAAATTTT??????

Is it a good practice to turn props into state inside a components in react?

Trying to build something that makes me rich by learning. Started ReactJS Going through events, state and props again. Really beginning to make progress. Will continue with tutorial tomorrow, and see how it goes. Still a bit unsure about the multiple levels of props, but getting there :) Also please suggest me more to learn today so it would be helpful tomorrow.

1) make a ordered list
2) prepare the props
3) specify a talking order
4) fuck everything because everyone does everything they want anyway
5) get a brutal amount of coffee*

funfact: my longest recent meeting was supposed to go for 30 minutes but we ended up talking about the position of a fucking infobox for 4 1/2 hours

What was your longest recent meeting?

*replace coffee with your favourite "fuck you, I am pretending to be awake" drink

Excuse my question I might be the one to blame, but on Typescript 3.7 JSON.stringify parses numbers as strings, while on 3.4 it was working without issues.

I'm no pro in web dev but I did use JSON.stringify lots of times and that's something strange here, not sure what the cause is, but when I parse number props again using parseInt(value.toString()) it works .-.