I grew up poor. First time I saw a computer face to face was when I was 11 years old. Back then any other references to computers came through media. I genuinely believed that hacking was as seen on TV, didn't even question 2 idiots 1 keyboard and thought it was genius to unplug a computer during "an attack"

Fact is I arrived in this country when I was 11. By the time I had my first laptop I was around 13-14, as you can imagine it went really poorly for someone who was just awarded a machine of never-ending stories and entertainment with absolute fear that a single mistake can cause everything to crash and burn. Heck, I remember when I went to Vodafone and someone recommended Firefox, it was such a novelty back then, heh.

I didn't understand computers. My IT lessons were replaced to work on my dialect, but truth be told it was an awful waste of time. I've learned more from forums than I ever learned from any English teacher. I just sat there twidling my thumbs in agitation.

With no concept of what IT industry entitles (my idea of programming was cubicles and call centres), I never had a slightest clue programming could be for me. I always thought of myself closer to engineering or physics type, but that never really drew my interests. So I dwelled in depression thinking I'm broken. Useless. That there was no calling for me.

I'm 22. For the past year I dipped in and out of programming, it still felt like such black magic.vLast month or so the spell dispelled and I finally feel like my eyes have been opened. I've spent the past 3 days sitting in front of my computer learning or actively programming, with occasional dips into DevRant reading your stories, frustrations and victories and I truly feel at home.

In retrospect I feel like I made the right decision for not chasing any mathematical/physics/engineering degrees, while certainly a goal of mine, I feel like I'd be miserable in those communities. They're closer to hobbies, really.

I guess what I wanted to say is thank you. Thank you DevRant for being the spark in my null future and giving me a sense of purpose and belonging. For the first time I feel like I can make it, like there was hope somewhere over the horizon.

That moment you leave the office for the last time in 2018.

FAWK YEAH!

What a year it’s been, from learning new platforms, to developing never ending changes, to breaking production at Christmas time, and finishing the year at the peak of purchasing period on a couple of websites with no reason to care what happens for several weeks all while absorbing extra projects from resigning co-workers.

*Turns on autopilot and walks the fuck out*

From one exhausted dev to the rest of you, enjoy the holiday break!

I've never learned how to program : I'm still learning.

Even if it's said 5 years of experience on my resume, I feel like I'll be a never-ending student.

Question to all you web developers out there: how do you survive long term in this job without going nuts? I have been working in this industry for almost 7 years and feelings of frustration have accumulated, to the point where I honestly feel like laying g bricks as a job would be more rewarding. Here are the main reasons why:

1) The fact that your job is never "finished" and it looks like and endless stream of tasks. Either the project has money being rolled in or is pretty much dead. Ever changing requirements ensure that most of what you do will be rewritten in 6 months or so. This is ok for the most part, but overtime it does give you the feeling that most of your effort was wasted, and you have the same website/app to show for it, slightly different...

2) The never ending churn of tech, particularly in the Javascript/node ecosystem. Sure, there is a good side of learning new approaches of doing things and it brings variety, but there is the dark side that you never feel you are getting better at doing your job, as every new project does not look anything like the previous. Even if all the stack pieces are the same (never happens), everyone sets it up and organises the project differently enough that you have to spend loads of time solving things you have done before. This makes it difficult to get a sense that you are mastering something...

So, if autonomy, purpose, and mastery are the keys to fulfilling work, I find this career lacking in mastery and purpose...does anyone feels/felt the same? How did you counter it?

Me coding and researching to fix new things everyday and people come to me saying:
"You are working too much"

And I'm thinking: actually, its a never ending learning job, I dedicate so much because almost everyday I learn at least one thing.

But knowing that non-tech people have a hard time around it I just answer: yeah.

QA personal voice assistant that runs locally without cloud, it’s like never ending project. I look at it from time to time and time pass by. Chat bots arrived, some decent voice algorithms appeared. There is less and less stuff to code since people progress in that area a lot.

I want to save notes using voice, search trough them, hear them, find some stuff in public data sources like wikipedia and also hear that stuff without using hands, read news articles and stuff like that.

I want to spend, more time for math and core algorithms related to machine learning and deep learning.

Problem is once I remember how basic network layers, error correction algorithms work or how particular deep learning algorithm is constructed and why is that, it’s already a week passed and I don’t remember where I started.

I did it couple of times already and every time I remember more then before but understanding core requires me sitting down with pen and paper and math problems and I don’t have time for that.

Now when I’m thinking about it - maybe I should write it somewhere in organized way. Get back to blogging and write articles about what I learned. This would require two times the time but maybe it would help to not forget.

I’m mostly interested in nlp, tts, stt. Wavenet, tacotron, bert, roberta, sentiment analysis, graphs and qa stuff. And now crystallography cause crystals are just organized graphs in 3d.

Well maybe if I’m lucky I retire in the next decade or at least take a year or two years off to have plenty of time to finish this project.

many many times in the past I had this impostor syndrome in various situations but I never lost faith in my dev skills!

you have to be humble to realise that this situations are fine and that you will learn something from it (not necessarily tech things, but also how life works). Also you have to realise that development as everything else in life is just never ending learning endeavour! When you accept all of that, impostor syndrome goes away forever.

It's been around 3 years since I felt like impostor for the last time because I accepted who I am as a person.

It crawled up on me last week in a different way - I was thinking of myself - what if I am just really good at googling things and understanding how those things work but I am also very capable problem solver so I can understand the principle and apply it to my code.

Then I realised - ok, that's what programmers do! So that's the story of how the impostor syndrome actually become confirmation syndrome!

Folks, believe in yourself, be forgiving to yourself as we all were there, give yourself some time as people don't become good developers overnight - and this is OK.

It's was the forth year of my college, in the corner of the world in south India, I wanted to something to combine both medicine and the coding that I learnt, I started learning about heart murmurs, it's basically a skill based diagnosis that only 1 in 20 heart specialists can make by hearing the heart beat and listening to a small murmur that happens during the systolic cycle or the diastolic cycle. I wrote a program to learn a lot of sample murmurs and try to find (very bad hand made logic) the similarities between two wave patterns, the problem started with noise so I went out and built a new stethoscope with a carbon mic inside a normal stethoscope head and try filtering the sound at source (worked well enough at that time) I then tried to find people to test it on, but alas I was not able to find patients as doctors are not supposed to reveal them etc. I wanted to show them visually how a murmur pattern would look like and I stole some code and made a plotter for the wav file and presented everything. By that time I got a lot of close amazing friends involved and they helped me solidify the project and we won the best project award and I got my first gold medal of my life at the end of my academic life :) it was one of the best moments of my life. Second only to the joy of getting married to wife. May be third if I put getting a job in Microsoft India Development Center.

I still wish I could dig that code up and write it properly with what I have learnt today but work is never ending and I find great problems to solve everyday which I know I can make a difference, may be when I get retired I will dust out that CD with the decades old c++ code and write one last program...

So good to see flash finally be put to pastor. Am I sad no flash sucked from a developer standpoint but even more from a business standpoint! Why? Here’s why!

....Yes it was fast in the sense of quickly getting content out and functioning BUT this ment you are at the mercy of Adobe / Macromedia (depending on the timeframe) for support AND mercy of the company whom create the browsers for support.

Meaning your product is fully reliant on others for existence and can easily not exist if one of two other beings choose.

For developers shame on you for accepting this you should never have supported this.. if you did it was just for a job you are suppose to be experts in your field and when management came to you for guidence you allowed this technology to be used rather than saying no this isn’t good! It’s too risky...

Fuck... how many people choose a career path that made them flash only developers.. well guess what becuase you niched yourself now your out of a job... rethinking now?

CAN ANY OF YOU TELL ME WHAT OTHER WIDLY USED TECHNOLOGY IS RELIANT ON A SEPARATE ENTITY?!

geee it would be a shame if one day that technology was phased out or no longer supported and then a date was picked and boom shutdown... geee that would suck...

I remember for years before it was announced it would be ending ... I said development around flash should be avoided at all costs because of it’s reliance on someone else for your product to function and exist...

Let this be a foreshadowing/ warning... learning experience/ AMAGE.. to those who use similarly situated technologies...

Developers you were warned.

Businesses you were warned.

HELP ME I used to conduct Java interviews for junior dev candidates, but since changing jobs three years ago, I've barely had to look at Java at all, and now I've forgotten everything.

Am I stuck in a never-ending loop of learning and relearning everything over and over again for eternity???

i found playing with arduino is never-ending fun. and then i tried Raspi and feeling the same. now i buy a bunch of raspi and trying to cluster them up, just for another random project.

yeah this is clearly nonsense. this is myself when my boredom gets high enough. No, vacation is not helping, trust me i've been camping in a jungle for 5 days and the next week i go to the beach. this is bad.

making things worse, My way of life is like any ordinary people (or maybe a developers) but turned upside down for example I program, learning for fun, and going vacation is just another medical need that i need to follow.

I am an university student, studying IT. I've been programming since 6, and geeking anything around technology and astronomy till now. this is my third semester and i don't get challanged enough for this kind of curricullum. i need some kind of project that even i don't think about any number of money anymore, but just enough to challange me up. just need to get rid my boredom.

sorry for ranting from a to z, this is just buzzing around my mind.

I've been programming for 15 years now or more if I count my years I programmed as a hobby. I'm mostly self learned. I'm working in an environment of a few developers and at least the same amount of other people (managers, sales, etc). We are creating Magento stores for middle sized businesses. The dev team is pretty good, I think.

But I'm struggling with management a lot. They are deciding on issues without asking us or even if I was asked about something and the answer was not what they expect, they ask the next developer below me. They do this all the way to Junior. A small example would be "lets create a testing site outside of deployment process on the server". Now if I do this, that site will never be updated and pose a security risk on the server for eternity because they would forget about it in a week. Adding it to our deployment process would take the same time and the testing site would benefit from security patches, quick deployment without logging in to the server, etc. Then the manager just disappears after hearing this from me. On slack, I get a question in 30 minutes from a remote developer about how to create an SSH user for a new site outside of deployment. I tell him the same. Then the junior gets called upstairs and ending up doing the job: no deployment, just plain SSH (SFTP) and manually creating the database. I end up doing it but He is "learning" how to do it.

An other example would be a day I was asked what is my opinion about Wordpress. We don't have any experience with Wordpress, I worked with Drupal before and when I look at a Wordpress codebase, I'm getting brain damage. They said Ok. The next day, comes the announcement that the boss decided to use Wordpress for our new agency website. For his own health and safety, I took the day off. At the end, the manager ended up hiring an indian developer who did a moderately fair job. No HiDPI sprites, no fancy SASS, just plain old CSS and a simple template. Lightyears worse than the site it was about to replace. But it did replace the old site, so now I have to look at it and identify myself part of the team. Best thing? We are now offering Wordpress development.

An other example is "lets do a quick order grid". This meant to be a table where the customer can enter SKU and quantity and they can theoretically order faster if they know the SKU already. It's a B2B solution. No one uses it. We have it for 2 sites now and in analytics, we have 5 page hits within 3 years on a site that's receiving 1000 users daily... Mostly our testing and the client looked at it. And no orders. I mean none, 0. I presented a well formatted study with screenshots from Analytics when I saw a proposal to a client to do this again. Guess what happened? Someone else from the team got the job to implement it. Happy client? No. They are questioning why no one is using it.

What would you do as a senior developer?

- Just serve notice and quit
- Try to talk to the boss (I don't see how it would work)
- Just don't give a shit

Finish a client project, with Laravel 5. Got a hang with the features and for once felt like I am "there" . nothing can beat me. then client request for the network to have no single point of failure.

I am like "whuttttt" how do I even replicate database and have fail over on it.

Im always trying to learn new things. Im passionate about learning new things, especially development. So much i started a small collaboration group of developers and slack group to collaborate new projects/ideas,get to know new people, and just to learn new things from each other. The group is not language specific developers only, but mostly consists of PHP/Laravel developers at the moment, so im always trying to grow that network as much as possible, so if you would like to join my network to collaborate new ideas or to just even talk to some cool cats, ill send you an invite any day. Anyways, back to my original reason for this post. Im mid level developer who considers himself pretty knowledgeable in PHP and Laravel. Im curious to what other developers use to learn new things. Im constantly questioning my skillset and compare myself to senior developers who always blow me away with their knowledge which often makes me feel like i dont know enough. Currently I use resources such as:

-laracasts.com
-serversforhackers.com
-digital ocean articles or any textbook that wont cost me an arm and a leg lol

I mean i just want to learn about tech related stuff always but currently interested in learning specifically about development topics such as:

- Server administration because i would consider this my weakest skill set (things like provisioning,nginx/security, deployment)
- Continous Integration (as ive never been at a job that practices it)
- RESTful APIs(as ive never developed one)

and so much more but i wont waste your time with my never ending list. What resources/tools do you guys use for your learning?

Once a React aficionado, twice the frustration we endure,
In the realm of libraries, React's problems seem impure.
With Svelte's elegance and grace in our sight,
Let's vent about React, as day turns into night.

Boilerplate Overload, a monotonous affair,
Classes, constructors, lifecycle steps we declare.
In Svelte's simplicity, we find a breath of fresh air,
Just markup and magic – a coder's love affair.

Complex State Management, React's Achilles' heel,
Redux, Mobx, and their massive code appeal.
Svelte's state handling is a cinch, for real,
No more tangled webs of logic to conceal.

Unnecessary Re-Renders, React's performance woe,
Countless updates, like a never-ending show.
Svelte updates what's needed, like a pro,
Efficiency and speed, in its radiant glow.

Verbose Syntax, JSX's verbosity on display,
HTML in JavaScript, causing dismay.
Svelte's concise template syntax lights our way,
No more endless tags, just code that's here to stay.

Lack of Truly Reactive Behavior, React's hurdle high,
Hooks to wrangle, state to satisfy.
Svelte's reactivity, no need to question why,
It just works, oh my, oh my.

Ecosystem Complexity, React's sprawling sprawl,
Choices galore, making us bawl.
In Svelte's world, simplicity is the call,
A coherent ecosystem, it has it all.

Learning Curve, React's mountain to climb,
Classes, hooks, context, a hill of time.
Svelte's gentle curve feels sublime,
A smoother path to code, so fine.

Tooling Overkill, React's complex array,
Build tools, linters, configs in disarray.
Svelte's streamlined setup leads the way,
No more intergalactic code buffet.

Debugging Headaches, React's mysterious realm,
Complex state, intricate components overwhelm.
Svelte's predictable model, a soothing helm,
Debugging becomes a peaceful realm.

In the end, React, a complex labyrinth we explore,
Svelte's elegance and simplicity we adore.
If only React could learn, its problems to deplore,
A brighter future, for React we'd implore.

so i've been working with a ux/graphic designer on a pretty large project that will likely have many services attached to it, it's been in "active" development for about a year now. something that concerns me however is how uncertain i feel about what i'm doing, constant questions like "am i doing this right", "is this secure", and many like them plague my mind while i'm coding and it's really discouraging. when i was just learning i didn't really take any heed from these questions, intact i never even really thought about them so why am i now? i feel kid if i'm able to just work and have fun i will be so much more productive and happy. my partner has been learning front end and has been doing great me i'm working on front and back end. i have been making most of the decision in regards to our stack but i feel like i'm making them arbitrarily and to attribute to this fact, i have switched things up several times, we went from react to an mvc framework and now i'm considering going back to react. i just can't seem to keep on track with my decisions, if any of you have experienced this before i would really like some advice on how i can be productive and again and not fall into this never-ending abyss of doubt.