Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "climbing"
-
Mountain climbing. Increases social skills, teamwork and trust.
Building a house. Increases spatial visualization and planning skills.
Electronics. Increases mathematical and problem solving skills.
Chemistry. Increases precision and analytical reasoning skills.
Psychedelic drugs. Increases imagination, inspiration and abstraction skills.24 -
!programming
Anyone else gets peeved when you're insulted in a language your insulter thinks you don't speak?
I was at the indoor climbing gym, struggling halfway up a difficult route when a fat idiot attached to a 'Intro to Climbing' class howled to her friends "Look at that blind idiot, can't he see that big red piece beside his foot?" (I was climbing a green route) in Cantonese (a Chinese dialect).
😒9 -
I've optimised so many things in my time I can't remember most of them.
Most recently, something had to be the equivalent off `"literal" LIKE column` with a million rows to compare. It would take around a second average each literal to lookup for a service that needs to be high load and low latency. This isn't an easy case to optimise, many people would consider it impossible.
It took my a couple of hours to reverse engineer the data and implement a few hundred line implementation that would look it up in 1ms average with the worst possible case being very rare and not too distant from this.
In another case there was a lookup of arbitrary time spans that most people would not bother to cache because the input parameters are too short lived and variable to make a difference. I replaced the 50000+ line application acting as a middle man between the application and database with 500 lines of code that did the look up faster and was able to implement a reasonable caching strategy. This dropped resource consumption by a minimum of factor of ten at least. Misses were cheaper and it was able to cache most cases. It also involved modifying the client library in C to stop it unnecessarily wrapping primitives in objects to the high level language which was causing it to consume excessive amounts of memory when processing huge data streams.
Another system would download a huge data set for every point of sale constantly, then parse and apply it. It had to reflect changes quickly but would download the whole dataset each time containing hundreds of thousands of rows. I whipped up a system so that a single server (barring redundancy) would download it in a loop, parse it using C which was much faster than the traditional interpreted language, then use a custom data differential format, TCP data streaming protocol, binary serialisation and LZMA compression to pipe it down to points of sale. This protocol also used versioning for catchup and differential combination for additional reduction in size. It went from being 30 seconds to a few minutes behind to using able to keep up to with in a second of changes. It was also using so much bandwidth that it would reach the limit on ADSL connections then get throttled. I looked at the traffic stats after and it dropped from dozens of terabytes a month to around a gigabyte or so a month for several hundred machines. The drop in the graphs you'd think all the machines had been turned off as that's what it looked like. It could now happily run over GPRS or 56K.
I was working on a project with a lot of data and noticed these huge tables and horrible queries. The tables were all the results of queries. Someone wrote terrible SQL then to optimise it ran it in the background with all possible variable values then store the results of joins and aggregates into new tables. On top of those tables they wrote more SQL. I wrote some new queries and query generation that wiped out thousands of lines of code immediately and operated on the original tables taking things down from 30GB and rapidly climbing to a couple GB.
Another time a piece of mathematics had to generate all possible permutations and the existing solution was factorial. I worked out how to optimise it to run n*n which believe it or not made the world of difference. Went from hardly handling anything to handling anything thrown at it. It was nice trying to get people to "freeze the system now".
I build my own frontend systems (admittedly rushed) that do what angular/react/vue aim for but with higher (maximum) performance including an in memory data base to back the UI that had layered event driven indexes and could handle referential integrity (overlay on the database only revealing items with valid integrity) or reordering and reposition events very rapidly using a custom AVL tree. You could layer indexes over it (data inheritance) that could be partial and dynamic.
So many times have I optimised things on automatic just cleaning up code normally. Hundreds, thousands of optimisations. It's what makes my clock tick.4 -
It has been bugging the shit out of me lately... the sheer number of shit-tier "programmers" that have been climbing out of the woodwork the last few years.
I'm not trying to come across as elitist or "holier than thou", but it's getting ridiculous and annoying. Even on here, you have people who "only do frontend development" or some other lame ass shit-stain of an excuse.
When I first started learning programming (PHP was my first language), it wasn't because I wanted to be a programmer. I used to be a member (my account is still there, in fact) of "HackThisSite", back when I was about 12 years old. After hanging out long enough, I got the hint that the best hackers are, in essence, programmers.
Want to learn how to do SQL injection? Learn SQL - write a program that uses an SQL database, and ask yourself how you would exploit your own software.
Want to reverse engineer the network protocol of some proprietary software? Learn TCP/IP - write a TCP/IP packet filter.
Back then, a programmer and a hacker were very much one in the same. Nowadays, some kid can download Python, write a "hello, world" program and they're halfway to freelancing or whatever.
It's rare to find a programmer - a REAL programmer, one who knows how the systems he develops for better than the back of his hand.
These days, I find people want the instant gratification that these simpler languages provide. You don't need to understand how virtual memory works, hell many people don't even really understand C/C++ pointers - and that's BASIC SHIT right there.
Put another way, would you want to take your car to a brake mechanic that doesn't understand how brakes work? I sure as hell wouldn't.
Watching these "programmers" out there who don't have a fucking clue how the code they write does what it does, is like watching a grown man walk around with a kid's toolbox full or plastic toys calling himself a mechanic. (I like cars, ok?!)
*sigh*
Python, AngularJS, Bootstrap, etc. They're all tools and they have their merits. But god fucking dammit, they're not the ONLY damn tools that matter. Stop making excuses *not* to learn something, Mr."IOnlyDoFrontEnd".
Coding ain't Lego's, fuckers.36 -
Climb into bed, feel something wet under leg. Wtf? I check. Bloody slug...
There was freaking slug in my bed...
Clean it out, change sheets and all (at 4am, I got lost in the code) and then see another one climbing up the side of the bed27 -
I've noticed something odd lately.. every time I mention mains electricity in certain EE forums, people tend to go "you are a madman for wanting to use that 🤨".
To which I think in my head, sure it's a dangerous thing, after all the angry pixies that dance back and forth are kind of angry (120V) or actually insane (230V) depending on where you live.. but to mindlessly tell people to not use it at all, as an electronics engineer.. what's up with that?
I mean, it's a matter of respecting its power, right. So whenever I work with it, thick gloves, keeping my exposed lines as tiny as possible, keeping them around for as short as possible, properly insulating anything permanent, and even asking my landlord to install a defibrillator for when things still go horribly wrong (to which she agreed because it'd be useful to the other residents as well, yay 😁) are kinda mandatory.
And that's for the same reason essentially that precautions are taken when climbing a mountain by having climbing shoes, connecting yourself to pikes jammed into the mountain over a strong metal wire in case things go wrong, etc etc. And for the same reason that you don't climb a ladder in high heels and so on. Obvious, right.
Point is, inexperienced people indeed shouldn't be working with mains AC at all and that's the reason that I've avoided it in the first year or 2 of learning about electronics. But mindlessly telling people in EE forums that they're a redneck for working with the imminently lethal AC.. what's up with that?
Maybe I should just go find another electronics forum like the EEVblog forums over some random (kinda dead) electronics chat on Telegram though ¯\_(ツ)_/¯12 -
Exercise devs, exercise, exercise and then exercise a little bit more
I've been coding for a long time and tbh programming is a very fiscally stale labour/hobby and even if your mind is rushing looking for answers, jumping from one place to another you are not moving that much, yes adjustable desks for programming while standing up are good and having breaks also helps but nothing like running, jumping, climbing or any sport.
During my lifetime I've seen the long and short term negative effects of sedentary jobs, back problems, liver problems, hormonal imbalance, overweight, depression, and anxiety.
I've been fiscally active for a long while but when I stopped, the first symptoms I had were weight gain, anxiety and depression, one night I even broke a tooth from stress teeth grinding.
Ive seen that people here might be having this issues and think it's normal, but try it out, start with a walk or jog sprinkled on your weekend.11 -
In the before time (late 90s) I worked for a company that worked for a company that worked for a company that provided software engineering services for NRC regulatory compliance. Fallout radius simulation, security access and checks, operational reporting, that sort of thing. Given that, I spent a lot of time around/at/in nuclear reactors.
One day, we're working on this system that uses RFID (before it was cool) and various physical sensors to do a few things, one of which is to determine if people exist at the intersection of hazardous particles, gasses, etc.
This also happens to be a system which, at that moment, is reporting hazardous conditions and people at the top of the outer containment shell. We know this is probably a red herring or faulty sensor because no one is present in the system vs the access logs and cameras, but we have to check anyways. A few building engineers climb the ladders up there and find that nothing is really visibly wrong and we have an all clear. They did not however know how to check the sensor.
Enter me, the only person from our firm on site that day. So in the next few minutes I am also in a monkey suit (bc protocol), climbing a 150 foot ladder that leads to another 150 foot ladder, all 110lbs of me + a 30lb diag "laptop" slung over my shoulder by a strap. At the top, I walk about a quarter of the way out, open the casing on the sensor module and find that someone had hooked up the line feed, but not the activity connection wire so it was sending a false signal. I open the diag laptop, plug it into the unit, write a simple firmware extension to intermediate the condition, flash, reload. I verify the error has cleared and an appropriate message was sent to the diagnostic system over the radio, run through an error test cycle, radio again, close it up. Once I returned to the ground, sweating my ass off, I also send a not at all passive aggressive email letting the boss know that the next shift will need to push the update to the other 600 air-gapped, unidirectional sensors around the facility.11 -
How much exercise do you guys tend to do? There's definitely a stereotype that developers aren't particularly sporty, but I break that mould (gym, squash, rock climbing, skiing, etc)
Any other sporty developers out there?25 -
I see loads of students here.. and loads of freelancers and startup joiners.. all varieties...but one.. Anyone has a 'normal' 9-5 or sth (dev) work? Does that even exist?! Anyone stands up when the 8h are up and can leave the work behind?
I can't.. even when I leave the office I have algos & code stuck in my head..trying to solve the problem I worked on..
How do you handle non dev life? Is there anything left in a day?
I usually work monday-friday on avg 9h/day and have no idea how to manage not being fucked up at the end of the week. :\ I am trying to get back climbing, but usually I am just soooooo tiiiiireeeeeed after work.. I wanna sleep but when I close my eyes I see the code.. at least one core still left working..19 -
A little over a year into my job at my current company back in January, I have a yearly meeting with my manager to discuss the progress I’ve made and to talk about what’s next. This is the meeting where we are supposed to discuss a potential pay raise but it’s the last topic of a predefined agenda.
So we spend a couple hours talking about how work has been for me. I started there as a junior developer with very little experience in the field but was quickly able to jump into a project with a fairly large codebase to help out the only other developer working on the project. Before long they’re so happy with me that they actually put me in charge of the application, which means my responsibilities evolve toward a whole lot more communication with the client and everything else that comes along with being in charge, including a lot of stress. I also salvaged another application initially developed by another company but that was so bugged it should’ve just been sent to the pits and rewritten from scratch. I was also asked to develop a couple POCs that were satisfactorily delivered.
Anyway, after almost two hours of going over my accomplishments and getting praises from my manager, we finally get to the part where we’re supposed to discuss a pay raise. He immediately cuts me off by saying the subject is not on the table due to the current crisis and our company struggling to make ends meet. I tell him I understand how hard it must be for them but also explain that I know for a fact other companies in the field are still making financial efforts to reward employees they’re happy with. He responds by saying that he’s aware of that, but he also “knows” that those same companies are laying off people that don’t deserve to be laid off despite the fact that they’re receiving government aid to stay afloat.
In the weeks following that meeting, I find out our company is doing the exact same thing my manager was condemning (laying off good people, taking massive advantage of government aid) and all the while not giving anybody a raise.
In any case, I really felt like that meeting was huge waste of time. What’s the point of going over everything I’ve done, congratulating me for my great work and even promising to give me even more responsibility if you don’t want to reward me for any of it? Do you honestly think I’m working hard so I can get a pat on the back or brownie points from you? I’ve got a family to take care of and I am trying to make their lives a little better each day by putting in hard work. But if hard work and climbing the latter of responsibility does not help me achieve that, what’s the point??1 -
@Owenvii made a post over at (https://devrant.com/rants/2359774/...) and I want to write a proper response.
The biggest thing you have to look out for as a new dev is the jobs which you accept to begin with.
This isn't minimum wage no more, this is "big league", well, maybe not apple or google big league, but it's not $9.25 an hour either.
Basically you don't want to work anywhere where 1. your labor will be treated as a highly disposable commodity. 2. where the hiring manager doesn't know how to do the job themselves.
The best thing you can do is, if you're new, and just breaking through (and even if you're not), is ask them common questions and problems/solutions that crop up doing the work. If they can answer intelligently that tells you the company values competence (maybe), enough to put someone in place who will know ability from bullshit, merit from mediocrity, and who understands the process of progressing from junior dev to a more involved role.
It also means they are incentivized to hire people who know what they're doing because the training cost of new hires is lowered when they hire people who are actually competent or capable of learning.
Remember, an interview isn't just them learning about you, it's your opportunity to interview *them* and boy, you'll be making a BIG mistake if you don't.
Ideally you want them to ask you to pair program a problem. If your solution is better than theirs then they aren't sending their best to do interviews, and it tells you the company doesn't fire incompetents. The interviewers response can tell you a lot too, if they critique your work, or suggest improvements, and especially if they explain their thinking, that is an amazing response to look for, it says the company values mentorship and *actual* teamwork (not the corporate lingo-bingo 'teamwork' that we sometimes see idolized on posters like so much common dogma).
Most importantly, get them to talk about their work and their team. If they're a professional, it'll be really difficult to pry anything negative about their co-workers out of them, but if they're loose-lipped and gossipy thats a VERY bad sign, regardless of what they have to say.
Ask to take a tour and do a meet n' greet of who you will be working with. If they say no, then it's no thank you to a job offer. You want to take every opportunity to get to know everyone there, everyone you'll be working with, as much as possible--because you'll be spending a LOT of time with these people and you want to rule out any place that employs 'unfireable' toxic assholes, sociopath executives, manipulative ladder climbing narcissists, and vicious misery-loving psychopathic coworkers as quick as possible. This isn't just one warning flag to look out for, it's the essential one. You're looking for the proper *workplace culture*, not the cheesy startup phrase of "workplace culture", but the actual attitudes of the team and the interpersonal dynamics.
Life is really short, and a heart attack at 25 from dipshit coworkers and workplace grief can and will destroy your health, if not your sanity, the older you get.
Trust and believe me when I say no paycheck is too grand to deal with some useless, smarmy, manipulative, or borderline motherfuckers at work constantly. You'll regret it if you do. Don't do it. Do you fucking do it. Just don't.
Take my words to heart and be weary of easy job offers. I'm not saying don't take a good offer that lands in your lap, I AM saying do some investigating and due diligence or the consequences are on you.1 -
It's 6am and I could only sleep for 4 hours, if I don't get my morning coffee soon I'm going to cut a bitch
.
.
Also please save the usual "I didn't sleep for a year while climbing a mountain while breast feeding orphans while curing cancer" kind of comments4 -
In 2020 I want to achieve:
- develop a proper custom deployment tool (for job)
- get my boss to finally approve of me doing code reviews (we have 0 reviews 🙄, tiny company)
- never have to work on WordPress ever again
- develop or set up a company internal package repo (alt. to NPM)
- get a new contract
- get 3 open side projects done
(non-dev)
- buy some more furniture and make the appartment finally cozy and a happy place to live
- finally get over the negative thoughts of that antisocial ex
- go indoor climbing 3 days of the week, to get rid of those developer fat cushions... 😅6 -
My biggest regret was leaving school for the workforce. I had aspirations of climbing the corporate ladder and maybe even being a leader or CEO someday myself.
It unfortunately took me too many years to realize it’s all a complete scam. You end up wasting away working on the most soul crushing of stuff, all to support someone else’s dream, and the people on top are not those who deserve to be there, but those who schemed and manipulated their way to the top. They often have zero idea what they’re doing and you end up having to do their job for them, while they take the credit and the big bonuses.
I had (and still have) many brilliant ideas for creations, but not one of my employers has cared about anything other than their bottom line. You are nothing but livestock to them, and they will treat you as such.
I wish now I’d just stayed in school and worked on my ideas and theories in an academic environment. If you think for a second companies will give a shit about you, think again.1 -
I’m almost 49, which is now considered “old” by most tech companies if you’re just a lowly staffer. If I can manage to stay employed until I can afford to retire, my goal is to just push through in whatever job in the industry (or even out of it) I can manage to do. Learning and being proficient with zillions of languages and frameworks like all these job postings want is impossible for me. I’m trying to figure out a way to work in some aspect of the commercial spaceflight industry without having to go back to school for an engineering degree and clawing my way up again. If that means being a janitor at SpaceX or Blue Origin, I’m fine with it. I’m done with ladder climbing and ass kissing.7
-
Hmm... That's 2 yrs from now.. o.O
Mmm...ok... Keep the job, rewrite old crap (I mean code) I'm maintaining & rock at it..
Personal issues wise, get married get own flat/house & hopefully get back to climbing at least on weekly basis.. Ooh & maybe a doggo & kitteh.. xD
P.S. maybe find a phone that will outsurvive me.. or at least survive me for more than 3 months.. :/6 -
Start an organization dedicated to building technology that helps people suffering from mental illness.
I also want to be able to work remotely while travelling and rock climbing. -
Not a rant, not even dev related..
I'm just soooo super excited & happy for Janja Garnbret, she won first ever olympic gold in climbing.. woop wooop! -
Bouldering helps me get my mind free. Since I go climbing once a week I recognize how stressed I am when I miss it.4
-
Programming is like climbing a giant mountain covered with other smaller mountains. You conquer one small mountain (i.e. bugs, refactor, etc) just to realize there are many more mountains ahead before you get anywhere near the final summit.
-
FredBoat, largest open source discord bot.
Making all the things work + making it scale when demand kept climbing was a challenge where we had to learn simple stuff like postgres, working with 3rd party apis, generally good coding patterns and maintainable code, but also rather advanced stuff like making the garbage collector play nice, profiling memory leaks and optimizing the hot path, as well as high level topics like cutting the codebase into scalable domains and services. -
I'm a dev lead. I'm trying to consolidate a squad. There's a senior in it preaching the dream of career climbing and LinkedIn optimization.
Now all interns want to switch squads. I'm all for personal growth... but now everyone wants to be everything at once and productivity stalled. The job descriptions for our squad were perfectly clear, there's tons of different tech stacks... We can build a lot of cool things in this scope, and now no one can see them because Data Science or Data Engineering or Front-end is suddenly sparkling.
I'm tired.3 -
The worst kind of legacy code is the one in which a function body run miles climbing if-else ladders until nobody knows where the sky hits the floor, and returns when nobody is looking.
The best kind of legacy code is the one which is fully commented out! -
I've been climbing down the rabbit hole of free hosting shit on the internet. It starts at "You want a site? Pay us $15 per month!" And ends at "You've got a domain? Cool, we're a CDN, static hosting free!". The less user friendly, the cheaper...4
-
Guyz so I found this climbing gym with a sauna, it's all good and stuff but I wonder if i shouldnt supplement with a side of ashtanga what do u think? Long term i want to improve my surfing15
-
A fjord in the south of Greenland last summer. (Hiking rather than climbing, but it works for the purpose of the joke.) What was worse was coming back down again, it was raining.
-
I got our climbing club web page to maintain. It was written in PHP by our older member. So I learned programming and slowly added new features.2
-
Q) What's the bravest action ever?
a) Sky diving
b) Rock climbing
c) Underwater diving
d) Doing fixes in Production
Correct Answer: Option (d)2 -
(Spoilers about Ready Player one here)
FUCK YEAH!
I watched Ready Player One in 4DX AND IT COSTED AN UNHOLY FUCKING AMOUNT OF MONEY!
yet it was THE BEST MOVIE Ive ever watched, AND I MEAN IT! IT WAS SO FUCKING GREAT! THE CGI THE ACTORS!
STEVEN DID AN EXCELLENT JOB!
and as a Trekkie I LOVED the scene of Hallidays death I mean his coffin WAS A FUCKING PHOTON TORPEDO! and in the Last scene you could see a bat'leth HOW HOW COOL WAS THAT!
And dont get me started on all the other References like the Holy Handgranade, Rubiks Cube, FUCKING BATMAN HELPING SOMEONE CLIMBING, Minecraft OASIS edition, Halo... I CANT ITS TOO MUCH!1 -
Pick up and learn new tech like SignalR and Vue and many more while also focusing on design patterns and software architecture.
Get myself another promotion so I can afford more shit.
Learn rock climbing, get into boxing, and do a first aid course.
Yeah, I'm gonna be busy as hell this year. -
I used to love the hero treatment I got long ago in my previous company. Appreciations and what not for conducting events, contributing to open source. I think I burned out later. Later the hero treatment stopped there and I craved for it when I wasn't doing the stuff I used to do - basically I was previously keeping others happy I guess, instead of keeping myself happy. Contributing to open source or conducting events was not even part of the day job and was mostly considered outside the working hours and hence one had to stretch to do all that extra stuff. I over did stuff I guess and burned out
In my current company, I see heros and appreciations so much for contributing to open source though not all our roles are completely defined as open source roles and we instead have to work on closed source or yet to be open sourced stuff. My role is contributing a very tiiiiiny testing bit in an yet to be open sourced project, but a few other colleagues of mine work on closed source paid advanced version of the open source core project
Seeing all the hero treatment where I'm not the hero and seeing all the appreciation, I wonder how it doesn't seem right. Surely I'm jealous, lol. But I also felt the treatment also shows some sort of Special treatment for some people. It's "Special" and not exactly for all and only for open source contributors or people doing all the popularly so called as "cool" stuff. Fortunately for them their job role kinda mentions that I believe. And people working on closed source are now trying to contribute there. I'm stuck with some of my main day job work and dying in guilt for burning out, and not being able to contribute to open source and also kind of starting to hate open source for it's dark sides. Reminds me Batman dialogue "You either die a hero, or you live long enough to see yourself become the villain.". Open Source dark sides - of course the possibile dark sides of companies funding open source, the people behind the companies and also of course my company being one of them possibly, though if you ask anyone they say "Community comes first". That's full of lies is what I would say.
Inclusivity gets thrown out the window. Heroes get to talk. Heroes get worshipped. Others are not even noticed I think. I guess the only way to get noticed is to imitate the heroes
At some point I realized I'm envying or idolizing a crazy set of people, or like putting them on a pedestal. I'm trying to fix that in my head. But oh my, you should see all the treatment, the respect, etc. Surely some people just are there to do meh or grunt work or even good work or whatever without much appreciation, and then have to move on. No respect or consideration for opinions, thoughts usually. Some of them don't even have the time to care to check what people have to say. Top down hierarchy but they say it's flat hierarchy. They don't even wanna listen to some of us I think, that is during team meetings. Only very few care from what I have noticed
One good thing is I have to come to realize how much I'm like them in some behaviours and feeling damn guilty. I sometimes spend time thinking how to change myself for the long term. And how to avoid the toxic behaviors in the team and also control my anger and control my response to their behaviours. I'm also trying to understand where I'm climbing the ladder with my assumptions and also trying to see the "real" thing instead of assuming or being blind or imagining etc. But it has become so hard because idk if people are faking it, it's become very hard to always assume people are telling the truth 🙈 though it makes to assume or believe that by default. If people are okay with themselves lying, who am I question that huh1 -
They added Fail Mode to Super Mario Odyssey — a set of ridiculously hard maps where you’re expected to fall down, but your gameplay is recorded, and in-game NPCs laugh at you. But, if you jump really far using boosters from Mario Kart, you can end up in rock climbing mode. When you reach the end, you get to a half-oasis, half-purgatory where there is a poker table, and other NPCs greet you.
There are a lot of chips, but they mean nothing — you got to invent your own rules. Among those chips, I found a surf green-colored micro SD card. I put it into my Switch, and the whole new game opened: a hybrid of Mario and Subway Surfers where I’m being chased by half-Peach, half-Thomas the Tank Engine.
When we reached the end, we lost our furry friend. But he was hiding in a dresser drawer, with a sex doll. Not an inflatable one, mind you, and not a silicone one either: the material resembled that of Barbie dolls.
She was a human-size, pretty Caucasian girl. I talked to her. Yes, she could talk, and the voice wasn’t robotic — she was definitely alive. Despite being a completely empty shell, she was conscious, albeit very dumb.
Her name was Near. This is the joke she told me:
— Knock-knock.
— Who’s there?
— Andy.
— Andy who?
— Andy who was imprisoned for sexual assault five years ago, duh! -
I wrote my first proper promise today
I'm building a State-driven, ajax fed Order/Invoice creation UI which Sales Reps use to place purchases for customers over the phone. The backend is a mutated PHP OSCommerce catalog which I've been making strides in refactoring towards OOP/eliminating spahgetti code and the need for a massive bootstrapper file which includes a ton of nonsense (I started by isolating the session and several crucial classes dealing with currency, language and the cart)
I'm using raw JS and jquery with copious reorganization.
I like state driven design, so I write all my data objects as classes using a base class with a simple attribute setter, and then extend the class and define it's attributes as an array which is passed to the parent setter in the construct.
I have also populateFromJson method in the parent class which allows me to match the attribute names to database fields in the backend which returns via ajax.
I achieve the state tracking by placing these objects into an array which underscore.js Observe watches, and that triggers methods to update the DOM or other objects.
Sure, I could do this in react but
1) It's in an admin area where the sales reps using it have to use edge/chrome/Firefox
2) I'm still climbing the react learning curve, so I can rapid prototype in jquery faster instead of getting hung up on something I don't understand
3) said admin area already uses jquery anyway
4) I like a challenge
Implementing promises is quickly turning messy jquery ajax calls into neat organized promise based operations that fit into my state tracking paradigm, so all jquery is responsible for is user interaction events.
The big flaw I want to address is that I'm still making html elements as JS strings to generate inputs/fields into the pseudo-forms.
Can anyone point me in the direction of a library or practice that allows me to generate Dom elements in a template-style manner.4 -
Dragon’s Dogma 2 is Elden Ring lite and i fucking LOVE it! It’s Elden ring combined with that classic action rpg vibe I grew up with! And the climb the enemy feature is damn SICK (nothing screams being a fucking man like climbing the back of a huge beast and plunging a sword down its skull)
Here’s to sticking a sword up an ogre’s ass!4 -
Why is laravel so poorly documented? Take \Illuminate\Mail\Mailer::send() as example. The third parameter is a callback. Nothing more. No info in the docblock what that callback does, when it is called or what the signature looks like. You have to go into the code and hope to find it out without climbing through a dozen classes.
If they are so sparse with the information in the docblock, they can leave it away completely. -
I work with all sorts of sporty/adventurous people going hiking, climbing, running ironmans, travelling to the end of the world who won't eat the heel of the bread loaf.
-
Since I can't get my user stories today, I started on trying getting my angular frontend to communicate with my symfony backend. I now feel like I need a lot of climbing gear, because I get the feeling I went too deep into the rabbit hole.
getting quite confused with Observables and promises.1