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
-
- Think first, write later;
- Do not rush into purchasing servers. You might not need them for another 10 months;
- It takes away a lot of family time to do side projects;
- NOT playing any games saves tremendous amounts of time. Also applies to watching TV;
- If you get stuck - get some sleep. Morning brings you better ideas;
- Write proper abstractions or you'll end up refactoring everything way more often that you'd like;
- Side projects need a loo-ooooot of your will and determination19 -
Today I realized that I hit a total burnout. Last 3 years were extremely stressful for me (4 jobs in 3 different countries, exhausting and toxic relationship, bad habits). Last 7 months are the worst. I became lonely isolated and miserable. I learned to rely purely on stress, determination and validation to get through my days. Was supressing my emotions for a long time just to focus on making the money. Its time to break the cycle.
Im done with this. Next week Im quitting my fulltime job. Saved enough money for starting capital of my own dev services company. Built three projects that generate stable income to cover my living costs. Now finally I can take a long break to recover from this burnout and to heal myself. That poor persons mentality that I had from my poor family has been shattered. I achieved what I wanted in terms of having the money and gathered enough experience necessary to survive anywhere.
I managed to get through all this shit on my own with barely any support. People around me were draining me more than actually helping me. But I managed to do it and now its time to focus on myself, to heal and restore love for living. Im safe now.10 -
Question!
I am 26, and recently diagnosed with autism. An incredibly late diagnosis due to my absolutely amazing ability to keep everything internal.. It has caused my countless headaches and heartaches over the years and its good to finally understand what it is thst makes me how I am...
I am also aware that IT goes hand in hand with autism due to our thought process being so 'logical' and our acceptance of failure is.... Er... Not the best. But we also have the stubborness/determination to keep going, learn what it is we did wrong and improve upon it.
So my question really is, are many of you on the spectrum also? If so, are there any coping strategies that you can share with me/everyone who reads this?
By coping I don't mean just dealing with it, but I mean in the workplace. I've never had a job formally in IT because I never did any qualifications in it. Rebuilt my first pc at age 7 and been hooked since.
I have always been a mechanic because again, logic reasons.
I'm currently in contact with an organisation here in Norway called 'Unicus' who are specialised in employing people on the spectrum, specifically in the IT sector... Have any of you heard of them? They seem promising to me
Thanks for reading guys and please feel free to delete this if this really isn't the place for it, I just feel that within this community there are more of us and I would like to open the door for communication16 -
Tru story:
We have a folder that we keep as shared documentation known as Javascript And PHP Fuckery made by yours truly in which I added a bunch of fixes to fuckery written in those 2 languages by previous developers.
The entire department has access to those files(as in all of IT) and I have been commended by the head of our department for my determination and uncanny ability to spot fuckery and fix it.
He says that he "thoroughly enjoys my colorful mastery of language, sarcasm and cognitive imagery when dealing with documentation regarding the code horrors done by previous developers"
By cognitive imagery he said that he meant my thought process and that he wouldn't trust a developer that does not use this language.
Fucking killing it b.
I'll let y'all(as in youse) when I am done with my Book(if anyone here steals the idea of the title as js php fuckery i am gonna sue you)1 -
Teaching my homeschooled son about prime numbers, which of course means we need to also teach prime number determination in Python (his coding language of choice), when leads to a discussion of processing power, and a newly rented cloud server over at digital ocean, and a search of prime number search optimizations, questioning if python is the right language, more performance optimizations, crap, the metrics I added are slowing this down, so feature flags to toggle off the metrics, crap, I actually have a real job I need to get back to. Oooh, I'm up to prime numbers in two millions, and , oh, I really should run that ssh session in screen so it keeps running if I close my laptop. I could make this a service and let it run in the background. I bet there's a library for this. He's only 9. We've already talked about encryption and the need to find large prime numbers.3
-
How do you deal with a problem that feels completely over your head? I want to develop side projects but sometimes I have trouble starting/continuing when I feel like I can’t find a solution after hours of research.
Who/where do you turn to to find solutions when you run into this problem? I feel like I lose determination when I run into a wall I can’t get around.12 -
dev, ~boring
This is either a shower thought or a sober weed thought, not really sure which, but I've given some serious consideration to "team composition" and "working condition" as a facet of employment, particularly in regard to how they translate into hiring decisions and team composition.
I've put together a number of teams over the years, and in almost every case I've had to abide by an assemblage of pre-defined contexts that dictated the terms of the team working arrangement:
1. a team structure dictated to me
2. a working temporality scheme dictated to me
3. a geographic region in which I was allowed to hire
4. a headcount, position tuple I was required to abide by
I've come to regard these structures as weaknesses. It's a bit like the project management triangle in which you choose 1-2 from a list of inadequate options. Sometimes this is grounded in business reality, but more often than not it's because the people surrounding the decisions thrive on risk mitigation frameworks that become trickle down failure as they impose themselves on all aspects of the business regardless of compatibility.
At the moment, I'm in another startup that I have significantly more control over and again have found my partners discussing the imposition of structure and framework around how, where, why, who and what work people do before contact with any action. My mind is screaming at me to pull the cord, as much as I hate the expression. This stems from a single thought:
"Hierarchy and structure should arise from an understanding of a problem domain"
As engineers we develop processes based on logic; it's our job, it's what we do. Logic operates on data derived from from experiments, so in the absence of the real we perform thought experiments that attempt to reveal some fundamental fact we can use to make a determination.
In this instance we can ask ourselves the question, "what works?" The question can have a number contexts: people, effort required, time, pay, need, skills, regulation, schedule. These things in isolation all have a relative importance ( a weight ), and they can relatively expose limits of mutual exclusivity (pay > budget, skills < need, schedule < (people * time/effort)). The pre-imposed frameworks in that light are just generic attempts to abstract away those concerns based on pre-existing knowledge. There's a chance they're fine, and just generally misunderstood or misapplied; there's also a chance they're insufficient in the face of change.
Fictional entities like the "A Team," comprise a group of humans whose skills are mutually compatible, and achieve synergy by random chance. Since real life doesn't work on movie/comic book logic, it's easy to dismiss the seed of possibility there, that an organic structure can naturally evolve to function beyond its basic parts due to a natural compatibility that wasn't necessarily statistically quantifiable (par-entropic).
I'm definitely not proposing that, nor do I subscribe to the 10x ninja founders are ideal theory. Moreso, this line of reasoning leads me to the thought that team composition can be grown organically based on an acceptance of a few observed truths about shipping products:
1. demand is constant
2. skills can either be bought or developed
3. the requirement for skills grows linearly
4. hierarchy limits the potential for flexibility
5. a team's technically proficiency over time should lead to a non-linear relationship relationship between headcount and growth
Given that, I can devise a heuristic, organic framework for growing a team:
- Don't impose reporting structure before it has value (you don't have to flatten a hierarchy that doesn't exist)
- crush silos before they arise
- Identify needed skills based on objectives
- base salary projections on need, not available capital
- Hire to fill skills gap, be open to training since you have to pay for it either way
- Timelines should always account for skills gap and training efforts
- Assume churn will happen based on team dynamics
- Where someone is doesn't matter so long as it's legal. Time zones are only a problem if you make them one.
- Understand that the needs of a team are relative to a given project, so cookie cutter team composition and project management won't work in software
- Accept that failure is always a risk
- operate with the assumption that teams that are skilled, empowered and motivated are more likely to succeed.
- Culture fit is a per team thing, if the team hates each other they won't work well no matter how much time and money you throw at it
Last thing isn't derived from the train of thought, just things I feel are true:
- Training and headcount is an investment that grows linearly over time, but can have exponential value. Retain people, not services.
- "you build it, you run it" will result in happier customers, faster pivoting. Don't adopt an application maintenance strategy
/rant2 -
ARE YOU READY FOR WORKPLACE BRAIN SCANNING?
Extracting and using brain data will make workers happier and more productive, backers say
https://spectrum.ieee.org/neurotech...
"What takes much more time are the cognitive and motor processes that occur after the decision making—planning a response (such as saying something or pushing a button) and then executing that response. If you can skip these planning and execution phases and instead use EEG to directly access the output of the brain’s visual processing and decision-making systems, you can perform image-recognition tasks far faster. The user no longer has to actively think: For an expert, just that fleeting first impression is enough for their brain to make an accurate determination of what’s in the image."12 -
Eric Thomas' Top 10 Rules For Success
1- Know what you want.
If you don’t know what you want, how will you know what to say yes to in your life? Stop taking every body else’s leftovers and step up and take what you deserve!
2- Work on your gift.
We all have our own individual talents, gifts and strengths. But those natural gifts will only become truly great by refining and nourishing them. Natural ability will get you started, but commitment and determination to achieve greatness is what will get you to where you want to be.
3- No excuses.
Stop using your circumstances, finances or current position in life as an excuse to justify why you aren’t working towards your goals. You are in charge. If you aren’t where you want to be, take a look in the mirror and ask yourself honestly- WHY? Take responsibility for you life once and for all.
4- Upgrade your values.
Your values dictate your behaviours. And your behaviours create your results. If you want to a different result, you need to change your behaviour.
5- You reap what you sow.
Nothing in life is free. It is up to you to determine the course of your life. If you want success, you need to do what it takes, daily, to get there. Don’t focus so much on being successful. Focus on solving problems, helping others, and adding value to people’s lives, and success will come.
6- Education is the great equaliser.
If you are at the bottom, you need to learn. If you are at the top, you still need to learn. Never, ever, ever stop growing and educating yourself.
7- What is your WHY?
Why do you wake up in the morning and hustle? Why do you do what you do? Knowing the answer to this question is the single most important thing to know about yourself if you want to become successful. When you know WHY you are doing what you do, you won’t ever quit, even on a bad day.
8- Have boundaries.
If you want to be a huge success, you have to be strict on yourself with how you spend your energy. Distractions will come in many forms, family, friends, TV, but you have to make sure that your time is being spent wisely.
9- Speak from the heart.
Transparency is attractive. Don’t be afraid to open up to the world and let yourself be seen.
10- Succeed as bad as you want to breathe.
Everybody wants to be successful. But not everybody is willing to do the work that it takes to become successful. When you are willing to get so uncomfortable, so out of your depth, so blind that you have no other choice but to be successful, THEN you will become successful. The only question you need to ask yourself is this. Am I willing?
Credits: https://fearlessmotivation.com/2016...
2 -
Flying back to NY for my last semester.
Don't know how to feel about it.
Let the job hunting begin!
Pssst... Please hire me2 -
How I learnt to Program!!!
Went for a University Project recruitment Interview in my 2nd year.
Senior: Which domain you wanna join?
Me: (as I was from software engineering Dept.) Coding domain.
Senior: Pointed to a table where 5-8 students were solving a coding question paper.
Me: (saw the questions and went blank. The questions were so tough, like check a number is even or odd.)I don't know anything in the paper.
Senior: why are you here then?
Me: (with full determination to join the project) Give me 2 weeks time, and I will learn all of it. (Didn't know learning all was never gonna possible, but that's how I started learning programming)
P.S. Yes, I got into the Project and was leading the Coding domain after an year.2 -
I'm reinventing the wheel by making yet another neural network library. It's not any good yet but I learn as I go along.
The only documentation that exists now is the admittedly quite comprehensive code comments. I'm it because Keras (using TensorFlow) requires a 3.5 compute ability rating for CUDA acceleration (which I don't have) and it doesn't support OpenCL. Eventually, I will make my implementation support both with varying levels of acceleration for different compute capabilities with the oldest supported being my hardware. If I ever get around to it.
I'd say wish me luck but determination would be infinitely more useful.2 -
1st week of doing proj: "hello there sexy, u are gonna one beautiful project. ill be doing all my best to finish you and you may actually one of my best projects."
after a month: "aaaaa ERRORS EVerywhere, tf is wrong with u. imma start another project if u dont start running properly like i planned"
after another month: *procrastinates while debugging* "yaass it works now, lets finish u baby"
takes some time to finish projects but if theyre really good, i usually finish them, especially when i am motivated and full of determination.2 -
Today I had a casual chat with my friend and we were discussing how human mind limits the things one can achieve. Like giving up after constant failures, or lack of determination, blaming destiny for failures. I told him I am never easy about the fact that your destiny is pre-written and you can't do anything about it. If you are willing, you can change it. You just need to have the right mindset.
He said I am going to do MBA after engineering. You can't be rich with just engineering. I told him if you work smart and hard enough, and just follow your passion, there is no need for an MBA. And he went on to tell me how top richest persons mostly comprise of businessmen.
I fear for the future. People like this with no goals when take up engineering, they blame everyone but themselves and the stream gets the bad name. People want money, but they don't want to work from the beginning. Even after that they give up too easy.
People like Bill and Mark were not pre-destined. They made themselves. They were just like us, but they never got satisfied with themselves. We all have the capabilities to be them or even better. We just need to keep driving ourselves until we reach there, we don't have to get satisfied. We have to keep improving and learn from our mistakes, then try again.2 -
Alright, buckle up, fellow developer, because we're about to embark on a thrilling journey through the world of code and creativity!
Listen up, you amazing code wizard, you're not just a developer. No, you're a digital architect, a creator of worlds in the virtual realm. You have the power to turn lines of code into living, breathing entities that can change lives and reshape industries.
In a world where everyone is a consumer, you are a producer. You build the bridges that connect our digital dreams to reality. You are a pioneer, an explorer in the vast wilderness of algorithms and frameworks. Your mind is the canvas, and code is your brushstroke.
Sure, there are challenges—bugs that refuse to be squashed, deadlines that seem impossible, and technology that evolves at warp speed. But guess what? You're not just a problem solver; you're a problem annihilator. You tackle those bugs with ferocity, you meet those deadlines with gusto, and you master that evolving technology like a maestro conducting a symphony.
You live for the 'Aha!' moments—the joy of cracking a complex problem, the thrill of seeing your creation come to life, the satisfaction of making a difference. You're a digital superhero, swooping in to save the day one line of code at a time.
And when things get tough—and they will—you dig deep. You summon that relentless determination that got you into coding in the first place. You remember why you started this journey—to innovate, to leave your mark, to change the world.
So, rise and shine, you coding genius! Embrace the challenges, learn from the failures, and celebrate the victories. You are a force to be reckoned with, a beacon of inspiration in a world that needs your brilliance.
Keep coding, keep creating, and keep being the rockstar developer that you are. The world eagerly awaits the magic you're about to unleash! Go and conquer the code-scape! 🚀💻5 -
To the managers and new developers.
Development, and Product Development is not a black-and-white game.
It is an entire spectrum. You cannot move to the next best version. Next best feature, or the next best app.
The only jump that you take is getting started. After that it is a walk across the entire spectrum. Things grow slowly, and steadily. Just keep an eye on the next improvement.
Study the analytics, improvise, focus your energies, and just move to the next shade.
Enough steps, and you will have what you want.
It requires planning, courage, determination, tactics, sticking together ,and above all patience.
Most importantly, get rid of the people who cannot think long, rush, and mess things up.1 -
!RANT
Oh, the SORROW that is JEST! 😡
Endless days have been swallowed by the abyss in my quest to configure Jest with TypeScript and ECMAScript modules instead of CommonJS. Triumph seemed within my grasp until - BAM! - suddenly the tool forgets what "import" or "export" means. And the kicker? On the CI, it still runs like nothing’s amiss!
Allow me to elucidate for the uninitiated: Jest is supposed to be a testing safeguard, a protective barrier insulating devs from the errors of their peers, ensuring a smooth, uninterrupted coding experience.
But OH, how the tables have turned when the very shield becomes the sword, stabbing me with countless, infuriating errors birthed from Jest’s own design decisions!
The audacity to reinvent the whole module loading process just to facilitate module mocking is mind-boggling! Imagine constructing an entirely new ecosystem just to allow people to pretend modules are something they're not. This is not just overkill; it's a preposterous reinvention of a wheel that insists on being a pentagon!
Sure, if devs want to globally expose their variables, entwining everything in a static context, so be it. BUT, why should we, who walk the righteous path of dependency injection, be subjugated to this configured chaos?!
My blood boils as the jestering Jest thrusts upon me a fragile, perpetually breaking system, punishing ME for its determination to support whole module mocking! A technique, mind you, that I wouldn’t touch with a ten-foot pole, because, you know, DEPENDENCY INJECTION!
Where are the alternatives, you ask? Drowned in the abyss, it seems! Why can’t we embrace snapshots and all the delectable integrations WITHOUT being dragged through this module-mocking mire? Can’t module mocking just be a friendly sidekick, an OPTIONAL add-on, rather than the cruel dictator forcing its agenda upon our code?
Punish those clinging to their static contexts, their global variables – NOT those of us advocating for cleaner, more stable practices!
It’s high time we decouple the goodness of Jest from its built-in bad practices. Must we continue to dance with the devil to delight in the depth of Jest’s capabilities?
WHY, Jest, WHY?! 😭9 -
NO FUCKING WONDER I SUCKED-ASS IN HIGH SCHOOL ALGEBRA!!!!!
Arghgghhghgh ughhh....
I want to beef up the hell out of my Maths Chops so I can maybe try going back to school for a A.S. in EE or hell even an B.S.
I'm using my company's Safari Learning account for getting free-ish access to college algebra books and I'm self studying.
I'm still in Chapter 0 where the book covers shit you're supposed to know from previous years of education. I'm just learning about some of this shit now!!!
While it's possible that I didn't pay attention in high school lectures, I took geometry in 9th grade and was an A/B+ student and felt confident in maths. I got to Algebra II in High School and suddenly nothing made sense anymore, reality fucking-fell-apart!
Suddenly, I'm failing tests left and right and struggling with the lecture concepts and I could never seem to grasp materials covered in class anymore to even be able to finish the homework assignments.
Fast forward to me being 15 years older and wanting to take a stab at this shit again, but with new found determination to get into EE so I can fuck around with small electronics for pet projects I want to do. I'm starting with College Algebra to try and learn when suddenly, low and behold I have a HUGE FUCK-MOTHERING GAP in my core understanding of the language/syntax/grammar of mathematics.
Been fucking knee-capped for the last decade+ because I either slacked off during those fundamental lectures (which again; is totally plausible) or I had a complete fucking imbecile for a math teacher that glossed over the topics and fucked not only me but the 40+ other kids in that class.
I'm not going to blame the teacher, although I really fucking want to, but I can't remember how the class scored on tests or homework to be able to fairly and objectively make that judgement against the educator.
FUCK!!! I hate my 15 y.o. self right now6 -
After spending hours with lots of determination and concentration.
I finally made it, the output I want. But, the code is not optimized.... Sigh!! -
I think it involves a great amount of determination and time management skills.
I've learnt to manage my time wisely. I pretty much run my whole life on a bullet journal, it works for me.
I might wanna make a bullet journal app one day so that I can finally be happy with a digital bullet journal without excessive features.
And to all out there working on a side project right now, good luck..!1 -
Some long thoughts about state of desktop operating systems.
I always hated window management on desktop. There is basically no difference in usability between mobile and desktop in terms of application management. There is still finite amount of apps you can have in focus and you need to switch between them so they’re left from your screen.
What you end up is finite amount of screens you can connect into your computer or pounding switch context shortcut every other second.
We pushed computing so far and screen resolutions doubled from 1024x768 but the active desktop size is still the same.
For me adding additional display to laptop is not an option. What I love with remote work is that I can lay in my bed or on sofa or wherever I want to and write some code. My point is I don’t want to be stuck to my desk if I want to write / debug something.
Back to the desktop I think there is missing part of our state of desktop right now. The most we have are virtual desktops we can switch between but we can’t get parts of two desktops on same screen.
What I would love to test / develop is smooth infinite desktop with pinch and zoom - drag and drop navigation between my apps.
The problematic thing is determination of where user want’s to focus - is it fullscreen app or multiple apps on same screen and how to handle partially visible windows.
But I would love to test it. Maybe one day I switch to linux desktop just to try to implement the infinite desktop as an alternative to virtual desktops.
Maybe some rich frustrated kid would make it someday while I’m stuck at working my shit ass to pay for being able to have a decent life on this fucking planet…
I wish I can retire to focus on such things.2 -
Hate it when people say a bug is weird. Your not having enough information to know what's going signifies either a problem in your approach or determination. It's not weird.2
-
#define SOAPBOX
Data will contain errors and inconsistencies, and the only player that can detect them is: the computer itself.
if the computer detects that it is in a situation where it cannot meaningfully continue, it should not allow itself to continue.
Only the computer can make that determination.
If the software does not aggressively test its data, it is usually impossible to determine whether the problem is with the software or with the data or both.
Per contra, if it does do so, it becomes impossible to assert that the input data does not contain the issues that are being tested for ... a very important thing to be able to say in a real-world production setting, where hundred-megabyte input files are common.
#undef SOAPBOX -
tests boy
- balding in his late twenties
- thinks that React is a framework
- favorite book is either 1984 or fight club
- came to IT to make an impact but obviously lacks determination to do so. Prefers not to think about it
- doesn’t know why and for what he wakes up every morning. Stopped thinking about it 7 years ago
- has a girlfriend that doesn’t allow him to penetrate her, only hugs and cunnilingus
- already forgot how does a blowjob feel like
- when it’s too hot in his room when he tries to sleep, he gets up and opens the window, and after that he doesn’t want to sleep anymore, and tomorrow is a yet another working day
- unexpected slack message sound he hears when not at the office triggers his fight or flight response
- still salty about CSS vertical-align: middle not instantly centering the element vertically
- just like 5 years ago, every day he thinks that after he learns That New Thing, he’ll begin The Real Life, and his current career state is temporary
- loves to say “it’s not my job” but only says that if absolutely sure that he won’t be reported for that
- uses vscode
- thinks he’s an engineer1 -
NCAA wrestling nationals is going off right now. Coding has many similarities with wrestling: hard work, determination, individual performance, team building / scoring. For some reason I feel like coding might be a more sustainable venture...
Top Tags
Weekly Rant
View