"Engineers don't memorize documentation. They know how to use it."

Programming felt insurmountable to me before I started with it. This phrase blew my mind and changed my approach entirely.

Worst meeting I've been in?

The one where I was told by my lead and the senior that my new colleagues were having trouble speaking to me because I'm a "strong, independent woman" and that I need to make sure I don't scare them when I approach them.

-_-

Why the Fuck anyone who knows programming is assumed to be nerdy ?
Also, this guy's "multilingual" approach backfired strong

other dev at work: "why cant i switch branch of my SVN repo like Git"
Me: "Cuz it uses different approach, different branches are at different locations......."
Him: "but how can i use it like Git"
Me: "you cant"
Him: "but why"
Me: "Get away from me before i throw something heavy at you"

A piece of software i use received a major redesign today and this is the outcome...

I REALLY LOVE THE MINIMALISTIC APPROACH YOU HAVE TAKEN HERE!

Just throwing ideas out here but you know...testing your product before launching it to your customers might be an idea, just saying...

Wannabe entrepreneurs approach for building their app.

Them: So you're familiar with Android?

Me: Yes but it's been a while, will take some time though.

Them: Not a problem.

Me: So shall we talk about the payment?

Them: Yeah, about that.. Listen, we don't have any funding now but we're sure this idea will be a hit and take off, then later we can pay you.

Me: Ok

*Gets up and leaves*

To all the C++ programmers who haven't read "Modern C++ Design" by Andrei Alexandrescu yet, READ IT! Its great. To me, it opened up an entirely new approach to designing classes with a whole new dimension of possibilities. And it reads really well! Sometimes I got shivers because the code was so sexy 😅😂😂

Wish Adobe would take a similar approach like Microsoft and release their Applications for Linux.. so I could use Photoshop and Lightroom there and ditch OS X completely...

That moment when you find yourself seriously arguing with your rubber duck about which approach to implement...

Now that I have time to approach my ultimate dream ( being the pro penrester ) , asked a hacker for a road map and he gave me (U'll rarely see such open hackers that share knowledge :) )
Surprisingly I've been familiar with all the topics but being the most pro , requires u to be pro in every single topic .

Guess what ? I'm starting from basic linux commands all over again 😂
echo 'hello world :/'

I had a professor, in college that believed "sometimes we have to fire customers. There are bad customers and it serves no purpose to spend time and effort in serving them when they burn you out and are simply bad customers" and I share that vision.

Reached out to Apple to report a bug where my screen gets pushed down 50% and leaves an odd blank area. Turns out the bug is literally a feature 😂

I like the modern entertainment industry's approach to tackling piracy.

Make shows/movies so horrible nobody wants to even pirate it.

!rant
Something that has probably stuck with me the most and has changed how I think about things:

"If you can't think of at least 3 different ways to approach an issue, you do not fully understand it yet."

Got the best compliment on an interview :3

Submitted a coding take home assignment. Was told by the tech lead that the code looked like they wrote it themselves! There was nothing they would change in terms of style or approach :3

I think I figured out why so many companies jumped on board the Agile approach. Companies heard Productivity Bonus and Put Stuff into a List Of Things to Do, and left out all the rest of their responsibilities. One of my past companies was like "We're going to take an Agile approach to everything! Except, we're not going to shield developers from everyone who has stuff in the backlog, and we're going to have other meetings during the day on top of the scrum meetings to check on your progress, and we're going to measure points in time instead of complexity".

I feel like the creators of the Agile Manifesto would be really upset at all of the poorly implemented processes. Because all of us developers are pretty upset.

DevRant is the best. I just gave Imgur another try. It still makes me depressed and loose faith in humanity. All those stupid people. DevRant is much better. Here we have smart people that know how to approach problems and understand jokes.

One day at a meeting I proposed a solution and explained it to everyone and everyone agreed to it. And then comes in this motherfucking Mr. shithole who starts talking about a piece of shit approach which had apparent drawbacks and everyone could see it but no one mentions. Why, becuase that bigger asshole is the boss of these smaller assholes. When I mention the drawbacks, all I get in return is, you are right but we think you should go this way. No fucking explanation why should I or any son of bitch should go that way. And every single one of those fuckers in the meeting suddenly became ok with his approach without any question or doubt. I mean WTF! What kind of developer you are if cant fucking express your views.

I almost gave up. I allready wrote an email to may boss, to admit my approach doesn't work, that he was right from the beginning, that i can't do it with a brunch of bash scripts, but special software has to be bought. I almost gave up. But then i just googled around a little more and found another approach to solve my problem. And it fucking worked!

Don't be afraid to approach companies that aren't actively hiring. No-one will look negatively at a positive attitude

Anyone else approach coding with the mindset of - "make it work, then make it right".

It really helped me up my productivity

Yesterday I started programming a telegram bot. First approach. Just curious.

Pretty impressed.
It's well documented and funny.

Follow up to yesterday’s “hybrid/cross-platform is shit” rant about Electron apps being blocked from the Apple App Store.

See the below image of the github issues template on the Electron repo, to file an issue for this problem.

Yes, this is such a common issue with their product, they’ve made it easier to file a github issue. Let’s not address the fact that there is a fundamental flaw in the approach they are using, let’s just make it easier to open a ticket while everyone waits to see if we are allowed to ship our app.

I’ve also heard talk that under some circumstances it’s possible for them to patch out the libraries causing issues. Apple provides tools to identify these libraries ... therefore Electron is doing fuck all to adresss this issue, and adopting a “wait until someone complains” style of approach.

A+

Programming lesson #5
When logic becomes too complex to solve mentally while coding, writing the requirements and inputs on paper and coming up with pseudocode is a good approach.

So I would really like to see a devrant like app where devs can share design ideas for problems that are greater than a function call, or topical questions found on stack overflow.

As I have gotten older, I have realized that actual implementation is typically easy, the design approach is typically harder to get right from the first go, so open critique can be very useful.

As a consultant, you get tasked with a variety of stuff. Last few weeks been struggling to maintain an old C++ application that was written by a complete tool of an a$$hole with zero knowledge on how to write maintainable and production quality code. It would hardly run without a crash. First it was a challenge I had to accept, but as I stabilized the code and just fell over even more traps, I had to admit defeat and review my approach.

Rewrite is something I would choose last, but this one ticked all the marks worthy of a rewrite. So, the customer is a very friendly researcher and gladly spent 15 hours with me explaining all the math and concepts - just a delight for a programmer to have such a customer. Two days in, with a DDD approach - a functional, more precise, faster and stable application.

Sometimes there is no rant to share, it's rare to have that perfect communication with a customer that is so dedicated that he spends so much time teaching you his speciality and actually understand your approach. DDD was really a lifesaver here, by using it's key concepts and ubiquitous language. The program is essentially 8000 lines of math, but wrapping it up with value objects and strong domain models made me understand his domain and him mine. It also allowed me to parallelize the computations, giving me a huge performance boost. Textbook approach, there will not be many like this!

My boss keeps trying new tech with important new projects instead of trying the fucking new things with anything other than important shit.

I support this let's try better options approach but cmon, be rational about it.

first approach to new software

My development process seems to go:

1. Write code
2. Believe that said code is amazing
3. Write more code
4. Revisit earlier code and start to doubt it's amazing-ness
5. Get frustrated that it could be done better
6. Redo 1 and repeat cycle

Seems a massive waste of time but I tend to like taking a different approach as soon as I find I'm getting stuck with the previous one.

I then get encouraged to take the quick/easy approach which seems like a backwards step and not worthwhile because I know it won't be as fast/efficient.

20 minutes trying to convince my boss (lead dev) that dynamically create tables on DB based on file name to store uploaded json content isn't a good design approach and he is still convinced that 500 lines will really impact performance that much on one table and that this is the best design...

Based on this approach, he wants to create another table with the user who last modified and the "fk" (not sure if he even knows what this is cause none of the fks here point to anything...) would be the table name... now I know where those hideous tables we have here come from...

Don't know if I laugh or cry...

I got a "Revise and Resubmit" response from the journal. Reviewer #1 wanted me to implement some baselines to compare against my method and he cited 6 papers. 5 of them did not have open-source code, and it's not like you can re-implement, train models and fine-tune someone else's approach in 2 weeks. The last one had code, for Ubuntu 14 (may its soul rest in peace), OpenCV version from the time America and Europa were connected and CUDA toolkit that was carved in stone in a cave.
I was bawling my eyes out, thinking about how many days it would take trying to Docker it to work. But then I realized the approach he cited was for RGB-D data, while I only use RGB camera. That's like letting a sniper with an M82 compete in archery....

In my view, there is exactly 1, very specific occasion, when hybrid / app wrappers / webviews etc. are the right approach for a mobile app.

1. Never

How I should approach a new project:

- think about data design
- draw some tables
- configure relations
- create data structures
....

How reality proves I'm a donkey:

- builds random table
- works on models, with random querys
- realizes things get to complicated and relations are broken or tables need duplicate logic
- starts thinking about 'good' design
- draw some tables
- configure relations
- create data structures
....

Quite an approach on NPS, something like: “We know we’re great, tell us how great”

The Subtle Art of Not Giving a Fuck: A Counterintuitive Approach to Living a Good Life

I am not into motivation books but I was intrigued by a title.

Nice fucking book.
Found some improvements I can make in my life.

Author literally wrote he don’t give a fuck if you’re reading it or not.

Well, that's a diffrent approach to gdpr.

!dev && avaition.stuff()

What a stupid idea to approach like that....

I was planning a crosswind landing, but I was too high, forgot how to extend the flaps, and for some reason the left landing gear wan't extended.

--> Crash

(FSX - ICAO: RKSW, IATA: SWU)

!rant

My colleague saw this code of mine and said it is annoying conditions are not on the same line, since it is a shared project I can't go "that's my style!"

What do you think should I convince him why we need to follow this approach (at least it can be easily read rather than reading a screen wide line)

This business philosophy is relevant no matter which industry, culture or century you're in. In software development a user- or customer-centered design approach is particularly important👌

Via Instagram @alphaimplement 🚀

I'm really sick of the "six-figure" advertisement that the industry uses to encourage more people to go into programming. The amount of people who hate coding with a passion but are in it because they want money is staggering. A lot of them end up dropping out. Sometimes I feel like I'm the only one who dearly loves this field. Truthfully, this approach won't resolve our retention problems.

Me as a sysadmin, and the devs approach with this:
hey "Linux", they network is stupid, the firewall is blocking the trafic from server1 to server2, pls fix.

The servers are on the same subnet with no firewall, so I log in to the servers and find out that their programs is not running.

This is something I deal with every day

"This is the Unix philosophy: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface." -Doug McIlroy

In today's context we can draw parallels with the microservice approach towards building software.

just hate it when exams approach and the whole month I neither code nor study , well derp

I only wish that my agile team comes up with the task breakup and documents the implementation approach to our project, as good as this kid did, while panning for a party!

img source: reddit

2020 apple news: New Iphones and macbooks have no screen anymore.

I feel like apple is taking the minimalistic approach a little too far huh..

!rant
Disregarding completely the anonimity factor...!

Guys vuejs conf in Amsterdam is happening tomorrow! If you are attending and see three guys with green t shirt with pulilab written on it just approach us!

We can't wait to meet some fellow ranters

What is your approach as a developer?

Copy & Paste

Have you ever argue with a developer who:
+ have the same level as you
+ on the same position in the company
+ in the same team
+ OLDER than you
+ thinks their code is the best

A few years back, a coworker and I argue about how to implement a feature. I proposed an approach. He proposed a different one. I immediately saw some problems and told him. But hell no, he defended his idea so strongly that I just gave up since I will leave the company soon.

2 weeks later, when the sprint was about to end, the whole team had to work overtime to fix the mess because of his terrible approach.

I'm starting to think that "Machine Learning" is the most unfortunate term that the industry has ever seen.

How people approach a problem here where I work: "I have a problem, I don't know how to solve it, I don't have any data. Let's implement a Machine Learning algorithm that will solve the problem for me."

Don't you just hate when a junior has been assigned a task in the domain you have experience, and instead of asking you for context and approach, the person asks for the EXACT LINE CHANGES INCLUDING THE LINE NUMBERS TO BE MODIFIED? Might as well assign the task to me.

Using Linux way back at school on a personal laptop.

Another student approach me and says:

- I like that skin what kind of skin (theme) has your windows machine?.

I replied:

- is Linux not windows is another operating system is my world

I was doing code reviews for some of the new Devs recently joined... One guy wrote his entire life history in the check in description... Like Why he took this approach, why interfaces are necessary in coding, when did he lost his virginity (I doubt he ever did), what's his pet name? - sadly no information related to his online banking... Shame really...

When it comes to nervewrecking situations, what I've encountered so far is a pull request for which the 2 reviewers had opposite opinions.
Something like this:
* opens pull request *
reviewer 1: "update using approach A"
* updates code *
reviewer 2: "this is wrong, change to approach B"
* updates code again *
reviewer 1: "this isn't what i asked for, i'm rejecting your PR"
Oh, also, each of them had their own set of coding standards.

What was your most challenging situation when writing code?

Life sucks when you get an error which you have seen this error like plenty of times and when you start debugging it and run out of all the ways you have always followed to fix it and all those didn't fixed the problem.
With nothing left now to approach, wondering what may have gone wrong.
The fundamentals are shattered
...

How awesome would it be to be able to migrate to a cattle-approach from a pets-approach when it comes to the human body, just kill your old body and start using a new one

Sickness? Create a new instance of your base image. Death? Just spin up a new instance and you're ready to move on. Broken arm? Kill body and get a new one.

Ofcourse, since we're stateful this method is kinda harder, unless you consider your conciousness an external database/soul

Don't be specific on any programming languages, focus more on OOP approach, and say you know about OOD/A rather than, you know Java, C# and this and that.

Installed my telecom service provider's app for checking new packs. Didn't remember the password. Hit forgot password! I get my password in plain text in sms!

Fuck, it's one of the leading service provider in the country!

Till now i had only read about it, but never encountered it! Any ideas as to how to approach them?

Overthinking and premature optimization. God damn them both! My mind completely freezes trying to come up with the best approach without actually trying or typing anything, only thinking.

No, Steam support, I don't wanna see your copy-paste shit, I just want you to fix your broken SSL on one of your server...

I hate writing to support so much (doesn't have to be Steam). I just want to see a human approach for once, but all I get is copypasta bullshit.

I learned how to program during my MSc at UC Santa Barbara in 1988. But the real thing happened during my first job as software engineer at Chorus Systems, in Paris, with the guidance of some of the world's best mentors, Russian engineers who taught me how to approach code design as if it was playing chess. These guys were brilliant!

The development principle behind this project was the infinite time/monkey/IDE approach.

Simplifying a problem
Is not the same
As as taking a simplistic approach.

debug hell

senior: i'm going to read the code changes of the PR that caused this bug, many files , lots of lines of code to see if i can suss out this issue

me: skimmed the PR, i give up, unga bunga time, time to compare the variables in the debugger between the different implementations, found the difference

due credit, the unga bunga approach worked this time, might nto always work

What are your thoughts about competitive coding and hackathons in general?

I sometimes feel that practices which are important for maintaining and structuring the code gets lost in the spirit of competition. Also, more hacks are kind of used to finish the assigned tasks rather than a proper approach.

Since learning how to program, I have started to see the world in a different way. The algorithmic and Mathematical way of approaching computing problems I have adapted to approach all of my problems. Everything is just a problem that can be solved by taking a logical approach!

Coding taught me how to think logically and how to approach problems with a fresh clear mind if your ever stuck like walking away for a bit and returning after a break.

It also allowed me to give my old teachers the middle finger who said I'd never do anything in life... 6 years later and I've owned my own media business and now work for a web agency!

Telecon about new requirements. I brought up concerns that while the customer's new approach would fix some problems, it would also fuck up something else.

Customer panicked because he didn't have an answer. I calmed him down that this telecon wasn't about finding answers, only for ensuring that we were on the same page with the questions. Customer relieved.

I actually explained the purpose of the telecon to the customer who had scheduled it. WTF.

I haven't touched algorithms for many months but needed to create a matching algorithm today.

It has to match using variations of the original key and output the keys that can't be matched.

The feeling in my head felt like I was turning rusty gears n sort of just stumbling through...

I used an N^2 approach but afterwards it just felt wrong... And it took me like an hour of hacking to do it....

Actually I just realized it's an N approach! because all possible matches would be hit by iterating from one of the lists of possible names!

I suddenly feel so proud of my subsconcious...

But still something doesn't feel right...

Introduce Git - Promote Collaboration
In the real world they won't work alone. Instead of giving individual projects give them a module to work for.

Example project: Library System
Student 1: Sign-up module
Student 2: Log-in module
Student 3: Book sorting module
Student n: x module

Output: A working system

With this approach, students will learn to work with a team and communicate properly about the project they're working for.

That guy at the office who gets really irritated and worried about newly introduced technology. He would spend 2-3 days talking trash about it, saying how much he prefers the older and less efficient approach just because he knows it.

That fucking guy.

I think my company used to work with an innovative developer centric approach to software development where you make commits based on the state of the developer rather than the code. 😂

Translation : "My DD is going to fail hence I commit" and "I'm tired".

I always had this mentality that I shouldn’t rely on a certain library or framework for my entire project because what if one day they stop supporting it. (Yeah I’m talking to u vuetify) That’s why I came up with this code structure that for everything that I wanna do I have a ‘driver’ library all coded by myself that interacts with that third party framework or library so if they stop supporting it I could just change a couple of lines of code in my driver file and my codebase should be working again. But I feel like this ‘driver’ approach is not the most efficient way of going in terms of memory usage. Do you guys think I should keep it simple and directly use those libraries or this is actually not a bad approach.

*every time we're pulled into a meeting to discuss a problem. 20 mins into discussion.*

"But that approach overlooks s-"

"THANKS GUYS. JUST KEEPING IN MIND TIME, LETS MOVE ON"

---

Move on to what? You asked to meet to discuss this problem - but I guess we should stop because `time > problem`.

Because when you built the UI and you watch how the end user interact with it, it’s like watching your kid approach their first love, or like watching moon rover landing except you designed and built the whole program by yourself.

It’s just magical.

When you convince your PM to follow your approach to solve a critical-ranked issue..

A new system developed at CSAIL was shown to have stronger security guarantees than Intel's existing approach for preventing so-called "timing attacks" like Meltdown and Spectre, made possible by hardware vulnerabilities.

Image courtesy of Graz University of Technology

My favorite famous dev/tech person + why?

Scott Hanselman.

He always takes the human approach to technology. Its easy to forget we're supposed to write software for people.

ML Dude: “Hey see what I did with this python code. It is so clean and dope”
Business Boss: “Well Done.”
ML Dude: “It is a nice approach don’t you think.”
Business Boss: “How does this put a money in my business account?”
ML Dude: “Ehmmmm”

Atari XE System, my first approach to a computer system.

[day 1] my team lead insisted that we work "together" on a story. told me to code my approach while he code his then evaluate both once done.
[day 3] we presented our codes to the team but in the end his code got deployed.
[day 4- 7]we got a lot of defects. we did a lot of fixing
[day 8] undeployed his code then deployed mine.
all problems got solved.

What would be the better approach for loading very big in size or in quantity files in java?
1) Loading data parallel through multiple threads
2) Loading data in series in a single thread
3) any other methodology?

Just asking because loading time is varying both cases.

Dell et al should start selling pre-stickered laptops so execs could buy that "dev cred" look.

There's probably a science to producing a look that doesn't make you look like someone's mum at a cool party.

What sticker placement approach do people use?

When an interviewer asks, what are the steps that you take usually when given a task to do something, what do you guys say?

I said, I devote 10-20% of the time to understand the given problem - sit and explore all possible scenarios to handle, then develop a brute Force approach, improve the approach to make it more efficient, see if it handles all edge and corner cases, then write test cases for it.

( I'm thinking, the process doesn't vary a lot for most of the people?, Except in TDD - one'll write the test cases first)

How would you answer this question?

I have this feeling that I messed up something 🤔

Re-reading old code I wrote some time ago and trying to improve it. It sounds and it definitely is scary to do at first, but it truly helps me approach things from a different perspective and question what I did.

So I have to build a frikkin site builder at work. It's supposed to run in the browser. Anyone has any good advice on how I should approach this? Should I use an already present library like GRAPESJS, or should I build it from scratch?

By trying to do my best. Doing a good job makes me feel good and gives me even more motivation.

Also by trying something new every time. Either by using new library, new approach do to things or whatever. Just to keep stuff exciting.

Just got told by our designer that I was wrong about the "mobile first" approach when designing web applications. She insisted that creating unique pages for each platform was the best way.

I must have missed that memo.

Love writing comments, hate writing documentation.

Ugh, I know it is needed but just don't care about it as much as the code/comments which is a more direct 'here is what this does' approach. Writing idiot proof documentation sucks. Any little change? Have to remember to update the docs. Yeah, not happy.

I was wondering how many years will I get for killing muggles who approach me with ideas about the "Next Facebook Idea" after hearing I am a programmer?!

Would be possible to be freed of all charges?

Being a programmer is more like being a football player, as you approach mid 30s your game dips really low.

If your problem has not yet been answered on StackOverflow, your probably doing something horribly wrong.
Consider a new approach.

Code reviewer tried as hard as possible to find issues in my commits.

After timereportimg 3 hours extra in a small ticket, he concluded we needed to try a different approach, even if code was OK? Why?

Simply because it was his idea and his idea is better. The reviewer needs to feel his superiority by any means.

I read this rant on Quora. Is this true ?

“The IT industry has devolved into a gigantic ponzi scam built on exploitation and BS. Quality of solution and quality of work was replaced with a ‘Does it work now?’ approach with zero contingency.
And the fact that geeks and nerds are naive only helps the white collar crooks to exploit them as code monkeys.”

I implemented the equivalent of “?.” In typescript with a function callled safeRetrieve(descend into the field only if the object is not null).

We could not update typescript, so I just created this function and it made me used to use ‘keyof T’ as a parameter type… I still feel very satisfied after I use this approach with anything because it really feels like using typescript correctly!

Idk why but it feels like lately i've such a pessimist approach to any new-tech (barring languages)
Any new framework or wrapper or CI/CD handler and without even seeing beyond description my instinct goes "fuccccccccck this, I hate it, it'll break things"

I wonder if theres a way to fix this mindset T__T or am I just getting old idkkk

First time used the TDD approach. I knew I needed to use it but never quite used it cause I thought it would slow me down. I was so wrong!
Mocha and chai js rock 🤘

Hate grows inside my soul when you are talking about a new feature and it's implications in the code base. Then you suggest a first approach, everyone agrees but one, someone whos rotten soul is craving for bloodshed, someone who says something like "Hell now, that's too much work" and then after hours of arguing he/she/it proposes the exact same approach... saying it's a better way.

I'm a strong believer in the triple-A unit-test pattern: Arrange, Act and Assert

Anyone else that uses this for their tests? Do you see any cons to using this approach to writing tests? Are you using an alternative?

I’m rarely at the initiative of a meeting, but when I am, my approach is: what questions need to to be answered? Time spent in the meeting is answering those questions without beating around the bush. I request precise answers, no "we shoulds" or vague responses. Meeting usually ends with clear answers/resolutions written down and shared so there aren’t any "that’s not what we agreed upon"

How do you guy (think of) prototype UI?

I have used the pen and paper approach but when you add the interactions such as clicks and animation on the paper,it become messy.

I feel that coding up a full blown front end for prototyping is overkill. Because when you want to prototype the list , you also need to insert the dummy data in order for you see probably clicks and drag animation.

My boss from a job I recently quit, there was a slight problem and I wasn't sure how to approach it as I didn't want to bother the customers and she just went out there like "I want to bother them 😈"

I and my team mate are assigned a task and if we find 2 or more probable approaches to it we naturally ask our supervisor how would he like us to proceed, with which design and approach.
He downright answers, "I don't care how you do it, just do it and finish it by xyz date".
I mean WTF? What are you our supervisor for?!?! This is also a part of your job dude!!

Ekhem.... da money? Sure I can go on about how it changed my approach to real life problems or how it keeps my mind flexible and always learning more BUT the truth is - those are just nice things on top of being able to buy food and pay rent

React hooks are so good that now I don't want to throw my laptop while developing web apps.
Nice approach.

Just "finished" a side project (I know right, unprecedented) to be graced immediately afterward with another approach to vastly improve one of its features. Well shit, now I HAVE to implement it otherwise it'll just bug the shit out of me for the rest of time!

WHY DO YOU DO THIS TO ME BRAIN! JUST LET ME FINISH MY SHITTY SIDE PROJECTS WITH PEACE AND QUIET!

Trying to review the architecture of an internal boilerplate... After having explained Atomic design principles, and the "component approach" to my colleague, he still managed to come back to me with:

- plugin/
- module/
- components/ ....

in his architecture... I don't know what to do. I'm depressed. FML. I'm quitting.

The only electronic device called Alexa that is allowed near me is a professional camera made by Arri. Approach me with some other Alexa device and my bodyguard will tase you.

In a long queue of people always want to apply LIFO approach but ended up using FIFO approach 😔

man... fuck java's approach to lambda expressions and like passing functions as arguments and the lot.
it's honestly just so terribly bad. it's sucks so much.

How I approach the project: got an idea run at super speed thinks something important on my way there and return with the same speed. 🤔🤔🤔😐

Sometimes developers forget how to take a pragmatic approach to solve issues. Just because it is shiny does not mean it is right for the job.

How to approach job applications for EU and US market?

I have applied at multiple places and have never made it even to the first stage. The jobs I apply for, pretty much match my experience level and stack.

Does this have something to do with visa issues since I am from the Middle East?

Or is there something else I am possible missing out on.

When it comes to a new project. I think what I dislike the least is building the mobile navigation. Especially when there's multiple

What approach do you guys take?

This may be obvious, but debugging is all about input / algorithm / output. If there's something wrong, it's one of the three. Work with the method of elimination. Sometimes it's easy, sometimes it's not.

I'll give you an example from my situation:

I wanted to play an old DOS game on my modern PC and so I used DosBox. I made an iso from the original CD, mounted it, referred to it in the game's mount settings and launched the game.

Then, after I had saved the game and I tried to load it again, the game would say: "Could not read/write savegame". And so I thought something was amuck with my mount settings and I started fiddling with those, but it only made it worse and it gave me more (cryptic) errors.
The next approach was to save a new game and load that one. Nope, same problem.
Finally I decided to follow a DosBox tutorial for the game and load the game again.. same problem. So I think hmm.. my algorithm is correct.. my output is wrong.. so then my input must be wrong. So I decided to save the game again with these new and correct settings and low and behold, it finally loaded.

One thing to note was that when it failed to load the savegame, it was because it had done a partial save because due to incorrect mount settings it couldn't figure out all the right config folders/files/paths and my savegame ended up being corrupt with 80% of the files having 0 Bytes, which was suspicious. That usually means a file became corrupt.

And then it hit me.. if the game says: "Could not read/write", that doesn't mean the same as "Could not access the file/folder". It could access it, it just couldn't parse it. And of course.. the 'write' part of the message indicates that it messed up in writing, causing it to misread. Sometimes you really have to think about it..

Anyway, input, algorithm, output. :)

I hate the word "Proactive"

What does that even mean? You add the prefix pro- to the word "active" and you get the same thing! Why not just say active?!

We're talking an active approach

We're taking a proactive approach

See, they mean the same thing and the first version doesn't make you sound like a douche.

How I approach pointer arithmetic:

Code something that seems ok, compile, and just keep fucking with it until gcc doesn't give any more errors.

Our mascot for the commercial approach to a teight deadlined project. I even got a framed copy when I left 😃.

You explain something exactly. Write extra documentation and even do tutorials and videos for the approach.
And then others come along and think they want to do it completely different. And only because the colleague before them has already done so.

Oh shit... My XPS 13 seems to slowly approach it's EOL :(

It has lost power 3 times already since yesterday. The last time it shut down while I was browsing BIOS (UEFI) settings, on a charger...

shit :(

Yes, I am drooling at the new XPS 7390 with advertised battery lifetime of 21 hour. But I'm so used to my lappy.

Shit :(

When your team is at war with the other site's team because their archi approach is "screw architecture and quality"

Whether it's a good idea to host my very primitive web-app on Heroku or setting up my own VPS on DigitalOcean etc.?

Heroku will save me some time, but I'm not sure about the scalability and cost.
VPS approach means I'll have to take care of all the DevOps myself, even though I know a bit Linux to kick things off, this is still quite daunting to me.

Any suggestions? Insights? Rants?

"Today’s designers and illustrators are synthesizing the best elements from past eras of graphic design to create a new visual language with a reduced and rational approach." - R. Klanten, H. Hellige

Spend several months designing an alternative approach to string matching/parsing not based on parser combination or Regex. Benchmark and profile the ever living hell out of it. Find out the performance is highly competitive with FParsec and far easier on memory than either approach. Discover FParsec responds very badly when failing. Document all of this, do a presentation on the design. Upload video of presentation with links to it on a few sites. Presentation gets downvoted, and receive hatemail. Yay.

Soooo lately my boss just introduced the AGILE methodology using Epics, UserStories, Tasks, etc. I enjoyed the approach so much. Scrums, Sprint meetings and the like. And also questioning him why ONLY NOW.

Typical insurance company BS approach.

Listening to xmas music, Spotify ad kicks in about 'just being "hacked"':

Buy our cyber security insurance product to quickly recover and retain liquidity in case of a cyber security beach.

Not a single word about preventing the incidents in the first place...

Lucky to work in a place that doesn't skimp on IT.

I'm new here and I don't know if this is a thing -
But I wanted to know if anyone would be interested in coding with me (+_+)

I didn't know of a better approach...

Stack Overflow's great when people choose to demonstrate their intelligence by insulting your approach rather than answering the question or providing substantive guidance.

I recently took on a protege who is a complete newbie to the world of CS. I recommend that everyone should try to lend a hand to someone who is just starting out - it helps you communicate complicated concepts more effectively, understand how less technically inclined people approach programs and it's also great practise for your personal skills.

does recursion have any practical use outside of being a cute/elegant solution under constraints where stack overflow isn't a concern due to small input size, and leetcode?

im having trouble thinking of anywhere you could justify using recursion in industry outside of leetcoding people

i assume the iterative approach would be preferred in scenarios where scaling matters

Monday morning
Get to work
Open email
Ci went crazy
Slack is on fire
Some npm modules deprecated approach
Rewrite docker files
Some other npm modules disappeared.

I hate you web technologies, I hate you developers who make releases Friday night.

I hate everything.

Ffs on the weekend just build Ikea fornitures instead of fiddling with my stack!

Sigh.

It's sort of two separate projects although they are very tightly related.

The first is a pattern combination library and parsing engine. It takes a superficially similar approach to Regex or parser combinators, but with some important underlying differences.

The second is a specialized (not turing complete) language for rapidly defining full language grammars and parsers/lexers for those languages.

Waterfall.

I string dislike the waterfall methodology and much prefer agile or scrum. And it's incredibly difficult that upper management only understands waterfall while claiming to know agile.

Meanwhile they want things completed by deadlines that are only possible with an agile approach. So you have a mishmash of upper management running waterfall with impossible deadlines and developers trying to meet those deadlines running in agile.

Anyone else have this problem?

Eureka! I have done it! I have written a program that will replace 80% of programmers with an AI!

The approach is to use grammar identification with language heuristics to recognize solution patterns using multilayered neural networks. The code source uses trusted pattern samples that are scored by human programmers. The code is programmed using text duplication and placement from the trusted sources.

TLDR: Uses pattern matching to copy and paste from Stack Overflow.

I think it was very useful for developing soft skills like time management, teamwork, dealing with failures, the willingness to learn and how to approach a problem, etc.

It's not about learning a technology or programming language super good and be the C++ or Web expert after finishing your degree. It's about self organization and problem solving IMO.

My approach to writing C++:

1. Write a test
2. If I don't understand the compiler errors, give up.
3. Run the test.
4. If it segfaults and I can't work out why in gdb, give up.
5. Make the test pass.
6. If the result is ugly and it breaks when I refactor, write a different test
7. Anything that makes it this far can be shipped.

I'm not a data scientist but lately I've learned NumPy, Pandas and now I'm learning Matplotlib and Seaborn and after years of Excel the improvement is astounding.

Excel is far easier to approach (I casually use it since I was 6) but once you need to do more advanced stuff it requires a lot of tricks and workarounds which needs to be memorized and are hard to find just by reasoning or are straight impossible without the use of macros which introduces many compatibility issues.

Pandas on the other hand is harder to approach but once you learn the concepts between its basic data structures you can do a lot with little "Google-Fu".

One of my biggest pet peeves with C++ are the number of ways to do things that, I personally, don't think their should be. Is that int* really an int pointer? Or is it an int array? Int vector? I am really regretting the refactoring approach I took.

Competing on different subjects while in school have taught me how to work efficiently under pressure. My teachers have given me a systemmatic approach to problem solving, from divide and conquer (math), careful reading and analysis of the problem, as well as good documentation (physics).

And last, but not least, I learned to type fast, which is really helpful in speedy expression of thoughts. And for that, I gotta thank IRC.

I've been familiar with C Programming and to sn intermediate level with web design, and currently I'm taking an introductory java Course, And The instructor kinda started with some simple gui apps using swing components on netbeans environment , his claim is that console apps are not that relative in the real word anymore , and gui apps are more interesting for newcomers , and I personally don't think it's a very effective approach , what's your opinion ?

Just got this coding task from a recruiter trying to determine what they want.

This for a front end job but we talked about api/network calls.

Are they just looking for the UI or do they want me to make the agency names dynamic through the different databases?

The recruiter is kind of clueless.

How would you approach this.

Hopefully get out to the public the two projects I have been working on currently. A local focused startup help website and a local focused fillable forms platform.

And hopefully get my first large scale software project kickstarted - A retail management system on a full Feedback Driven Development approach perhaps with the ability to integrate AI and ML later on.

Everyone excited discussing a new data access API to provide to the clients when, le boss:
"Just so you guys think out of the box a bit. What if you deployed the API on Swagger instead of AWS? It seems a nice and fresh approach, huh?"

Everyone on the room remained in silence and internally questioning why do we work here...

No matter what I do and try: Scala always look so damn ugly.

And yes, I do use scalafmt. Yes, I try to follow the scala approach, yet still -- my poor eyes.

It's also not helping that the bracket mess and the lack IDE-help in regards to finding where I missed them reminds me of time wasted in lisp.

Lets take onlyfans system for example. They have fans and creators. How is database models supposed to be structured? Whats the correct way.

1) a User model that contains all users of all roles, but differentiates them by Role ENUM

2) a separate Fan and Creator model, each having their own unique attributes, while each extending an abstract base User model class that has all the common attributes that both models should use

The 1st approach is simple but gets very large and difficult to maintain and view all the attributes cluttered in 1 class. Not to mention how some attributes will never be used for a user who registered as a Fan.

2nd approach is more modular and easier to understand and maintain by knowing exactly what attributes to put for each model. However problems occurs when you try to join tables and stuff start to become overengineered

Help. We're starting to feel the effects of unnecessary micromanagement.

We're a small startup. The kind with less than 10 devs spread across different domains. We've been fine with a Kanban approach as the velocity/flow of deliverables don't necessarily warrant a Scrum approach yet.

Our boss has been wanting to adopt Scrum-style sprints, even shoved and assumed that were doing these sprints and demanding Scrum-style reports (and meetings!!!) when they are, in reality,
1) unnecessary
2) a waste of time

Absolutely none of the team members want this. But our boss insists on having it. We like our boss, but lately things are getting out of control

What can we do to mitigate and prevent this?

Six months ago, I architected a solution that I thought was pretty darn good. Of course my boss didn't agree and basically twisted my arm until I agreed to go along with his approach. Today, he's walking back on it.. and telling us we can refactor the solution if it doesn't make sense anymore.. so back to my original solution?
If only he listened in the first place..

I am new to devrant and it seems like a neat platform to connect with exclusively developers and programmers. I am newly enrolled in Full Sail University's Web Design and Development Online Bachelor's degree program and learning early HTML and CSS currently on my own while finishing my general classes. Any tips/tutorials/courses on code, inspiration, best way to approach learning languages, etc. are all appreciated. Also open to connecting as well.

I've found a better job offer; shorter distance, but salery is low, not that is a big issue tbh.

What is the right approach to quit your job?

Or to say, nicest way to avoid burning any bridges.

Why don't most products follow a minimalist approach right till the end? Most start ups start like that. But when things begin to fall apart or become better they tend to deviate. While the earlier reason is understandable (because no one likes to fail so they'll do anything to not fail), the second reason seems to me more of an organisational creation than what the users want.

From my understanding as the product becomes popular positions (managerial or product) created need to justify their presence. What do they do? So the breath of fresh air brings in a lot of garbage that may not be required and would be in deviance from the main product idea.

It is debatable that audiences would not accept such ideas that are being brought in, because hey audiences are smart. And they are. But the organisation in order to justify the original wrong decision tends to push their new features (through offers or marketing campaigns). This makes the organisation invested into a wrong direction and security of jobs of the new managers/product people. Win win situation, but lose lose for the organisation and the original product.

I was told to write a program without being given any spec, and now get comments that I should have done more of top-down approach. Yay.

It taught me to always approach problems logically and rationally.

What's the best way to ask my IT manager for a first year review? What's the best way to approach it from a junior position where I feel I'm being underpaid and overworked?

Its taken for granted in most projects but for me its definitely git, I especially like Gitlab's approach.

Also a rubber duck.

!rant (I got down voted for this on Stack Overflow, so I try to discuss the issue with a more professional crowd.)

In a Software Engineering class, we had an assignment to read Parnas' seminal paper on modularization [0]. In this paper, two approaches of dividing a software into modules are discussed:

Traditional Approach: A flow chart is drawn to work out the single processing steps and the program's high-level flow. Then every processing step is turned into a module. This approach doesn't yield very good results.
New Approach: Every design decision will be turned into a module by the means of information hiding. This approach leads to much better results.

My personal interpretation of the term design decision is that the modules are identified as data structures rather than as processing steps of an algorithm. This makes sense, because data structures are much more suitable for information hiding then processing steps of an algorithm. (The information inside a data structure is hidden behind functions, whereas a function only hides more detailed processing steps and no information; the information is actually passed in as arguments.)

Why does the second approach work so much better than the first approach? Here comes my second interpretation: The single processing steps of an algorithm are not replaceable (and thus not reusable), whereas it's possible to convert data structures into other data structures.

And here's my question: Could that be the reason why software development using workflow engines (based on BPMN, for example) never really took off?

My personal experience is that the activities created in such workflows are hardly ever reused, but there often are big data structures passed around all the involved activities, even if most of the activities use only one or two of them.

My question exaggerated: Could we get rid of all those clumsy workflow engines by giving managers Parnas' paper to read?

[0]: On the criteria to be used in decomposing systems into modules (Parnas 1972)

I had this idea
convert my application icons into base64 and save everything in one big js object

one month after this bizarre moment now I'm here trying to develop a even worst approach.

any suggestions?

I'm a Newbie to networking, and currently trying to understand this Network and Identifying the IPs for which interfaces.

I'd love to know which IP address is for the captured Router interface, etc. Which IP is the address of the captured interface n2.

How do I approach to solve this Problem?

Question to all those who have worked with software architecture: What is your approach when implementing architecture and design into actual software?

I find it very hard to translate UML diagrams and architectural requirements into working code and I feel like there is quite a big "gap" between the two. How to you breach that gap and manage to maintain a clean and comprehensive architecture in your project folders?

"If you look at any designer you admire, whose work inspires you, and whose approach somehow resonates with you, I promise you’ll find a person who does not think of what they do as just their job." - Alexander Isley

Question: which is better approach?

1. Use push notifications to tell react website that new data is available

OR

2. Use SignalR (similar to socket.io) and push data in real time?

The down side of SignalR is server needs to map connections --> use more memory while push notifications doesn't require that

It's getting on my nerve to constantly change from one programming language to another in one semester. We are learning web development (html css js), functional programming (haskell), speech analysis (matlab) and logical programming (prolog). It's driving me kinda mad having to change the approach for each assignment every few days.

Guys, about Continuous Integration with SVN, what is the best approach? Thank you

isARant()==idk;
I'm a linux fan (not fanboy) and I just discovered I can have a Microsoft Imagine account from my school and I don't fucking know if I want to use windows to learn Azure and .NET
I quite hate Microsoft for their privacy policies and their recent approach to windows
But it would be a shame not to learn that stuff
Any advice?
Fuck (to make it more ranty)

Can anyone freaking tell me that Agile is still relevant and yet one of the most hated approach??

I'm freaking confused.

post != rant #sorry

Just curious. How would one go about programming something like this? Do you guys think this machine just displays a fullscreen web app made in html/css or is there another approach with an actual programming language, not markup language that one can take? I heard it uses RFID technology to show cartridge levels, and records the time dispensed, alerts store owner when low, and brand dispensed alongside just dispensing drinks.

Does this ever happen to you, where you see your company/client spending too much money on a problem needlessly. Then you come in and tell them a way cheaper and better approach and they agree on doing it your way.

Then you think of the money you saved them knowing that there is no reward for you doing that, and then take a big sigh?

🤔 Google is transforming from a free service company to a paid service company with gsuite, youtube tv, google drive premium , YouTube patreon approach, g cloud, selling hardware ... and more

I am a little afraid 😱
Is google transforming to apple like

Reverse number(logic)
------
First Approach :=
void reverseMethod(int n)
{
String str="";
int temp=0;
while(n>0)
{
temp=n%10;
n=n/10;
str=str+""+temp;
}
System.out.println(str);
}
-----
Second Approach :=
void reverseMethod(int n)
{
int temp=0;
int rev=0;
while(n>0)
{
temp=n%10;
n=n/10;
rev=rev*10+temp;
}
System.out.println(rev);
}
-----

why the fuck second one is recommended??
In first, at least we do not required to remember that formula.

I don't know... I'm very sceptic about JPA. I worked on a project using this technology and having much trouble and now I'm working on the second one, but sincerely I prefer the standard SQL approach. What do you think guys about this framework?

Can somebody give me examples of questions I might get asked in a final technical interview where I'm NOT doing any coding...

The guy said they want to get a sense of how I would approach a technical problem and that they can teach me how to code but I need to show I can problem solve - just not sure how prepare for this...

People do not know the value of simplicity... They want a system that does EVERYTHING ANYBODY EVER wanted, forgetting that this approach will always cause problems in future

Email today:

"Forgive me for this direct approach. I'm from (business) and wanted to give you the opportunity to opt out of our future weekly emails."

Did anyone here use sapper and svelte to build a production application? How was the experience overall?

I've been reading about it and watched Rich Harris present svelte and sapper, I like his approach but I'm not too sure about how it work in a production workflow

How do you plan before small software changes?

I have some extremely iterative approach where I change one function or one variable at a time, like a headless chicken. I am not planning beforehand which modules or functions I need to change but start from somewhere and like a linked list, I am moving on until the end.

But I feel like it is wasting my time. What is your approach when you want to have let's say -50 line of code changes?

Having to approach your manager and bringing you that you haven't been meeting your deadlines due to being distracted dealing with depression is by far one of the hardest things I've ever had to do.. If you need help reach out someone is always willing to help!

Hi everyone, long time no see! I have a question for you all.

Where does your company keep its clients’ code on GitHub? Is it everything in the company’s GitHub Org or does each client have a dedicated GitHub Org?

Any issues you guys have encountered with either approach?

I think promoting 'a quick lookup on Google' every single time you need to add something useful into your codebase is a bad mentality. It's the same problem with populating your code with Stackoverflow snippets.

I think this is not a good approach because your code will eventually rot and you won't have full control over your codebase in that you didn't write those parts and you don't fully know what's going on underneath. Then, you will forget about that code. A new feature request will come up and oh no, you will be wrestling with your old code because you just quickly inserted it in there, not fully knowing it under the hood. Hours will be lost on debugging.

I advocate much more the approach of really knowing the language and the solutions you're using, instead of just constantly hacking it with the excuse of "Oh, there's no time to learn everything", "You don't need to know the details" and "This is the real world".

No, this is not a good attitude. With the former approach, you will be much more able to safeguard your code and improve on it, rather than wrestling for hours with it. I think it's important to have as much ownership of your code as possible and depend as little on outside libraries as possible.

Fundamentals first, practicality second.

Please i have a question

I'm building an API with expressJs

Do i need to create a single database connection for all my query

Or should i rather open and close a connection for every query.

Which one is more efficient?

I'm currently using the first approach but the heroku clearDB addons is keep crashing Everytime saying connexion closed!

Please help
Thanks

hello folks, any help would appreciated :). serious question about designing/developing a rest backend.

here is a little insight: I want to reduce the endpoints for many CRUD operations as I can. So for that approach I defined a set of "dynamic" routes like /:moduleName/list, /:moduleName/update and so on.

Now I want to also reduce hardcoding as much stuff as I can for the front end. like I want forms/view/components to know which fields can be sent in the "/:moduleName/xxx" endpoints from above. So I'm thinking to make some /:moduleName/list/map, /:moduleName/update/map endpoints that tells the frontend which fields/keys can be sent for X or Y operation.

regarding design/security concerns Is that a good approach? do you know any other approach that's like to what I want to achieve?

Linux package management is dumb for one simple reason: it is too complicated for its own good. There are too many different approaches and even within one approach there might be multiple repositories.

Is bad.

I don’t like commented code in a project, I always remove commented code whenever I see. But sometimes these removed commented codes need again to add by uncommenting.

I can get the code by seeing the git history but if only I can remember I removed that portion of code. So is there is any best approach to manage commented code, which may require in real future?

Fixing bugs is like scratching balls , if you're at it for too long and it hurts ....
It's probably time to try a different approach ....

I have skipped a job follow up after a nice interview at a seemingly great software development firm two months ago, and it was because they used slightly different technologies. Now, I wanna do ANYTHING to switch my current job to another one.

How should I approach the company I didn't follow up with now? Especially when they still have the job posting on their website.

Break my phone...

Tho I can't say I've used this approach yet, but I'm certain it'll work if I ever get that courage

would you separate Domain Classes with Models and ViewModels in an asp mvc EFCF approach?

Everything can be fixed, it just requires a methodical and calm approach.

That's what I keep repeating in my head, as I desperately try to fix my mums washing machine before she gets back from holiday.