Agency: " Sir, we found 3 candidates as per your requirements, now how do you want their placements sir?"

M.D: "Put about 100 bricks in a closed room. Then send the candidates into the room & close the door, leave them alone & come back after a few hours and analyse the situation:-

1) If they are counting the bricks, Put them in Accounts deptt.

2) If they are re-counting the bricks, Put them in Auditing.

3) If they have messed up the whole room with the bricks, Put them in Engineering.

4) If they are arranging the bricks in some strange order, Put them in Planning.

5) If they are throwing the bricks at each other, Put them in Operations.

6) If they are sleeping, Put them in Security.

7) If they have broken the bricks into pieces, Put them in Information Technology.

8) If they are sitting idle, Put them in Human Resources.

9) If they say they have tried different combinations yet not a single brick has been moved, Put them in Sales.

10) If they have already left for the day, Put them in Marketing.

11) If they are staring out of the window, Put them in Strategic Planning.

And.......

12) If they are talking to each other and not a single brick has been touched, Congratulate them and put them in Top Management.

😂🤣😃😁😅😜

Your profession changes how you think.
Coding did the same for me. Some good, some bad.

The good:

I know which problems in life are worth trying to solve.

And I'm very good at solving those problems.

I can analyse a situation accurately. I don't get emotional and panic.

I can immediately identify logical flaws in people's thinking.

I can identify biases in others and myself.

The bad:

I tend to follow simple instructions to the letter and rarely improvise based on reality.

When my wife tells me her problem I try to solve it instead of empathizing - which is what she really wants.

I haven't developed street smarts or the ability to convince people with anything other than logic - but people are more emotional than logical.

I'm not good at small talk.

If all you have is a hammer, everything looks like a nail!

This was something which my tech lead used to tell me when I was so obsessed with nosql databases a few years back. I would try to find problems to solve that has a use case for nosql databases or even try to convince me(I didn’t realise it back then) that I need to use nosql db for this new idea that I have, without really thinking deep enough whether the data in question is better represented using an sql schema or not.

Now, leading a team of young developers, I come across similar suggestions from few of my team members who just discovered this new and shiny tech and want to use it in production projects.

While I am not against new and shiny, it’s not a good practice to jump right in to it without exploring it deep enough or considering all the shortcomings. The most important question to ask is, whether some of the problems you are trying to solve can be solved with the current stack.

Modifying your stack requires more than just a week’s experience of playing around with the getting started guide and stack overflow replies. This is something which need to be carefully considered after taking inputs from the people who would be supporting it, that include operations, sysadmins and teams that are gonna interface with your stack indirectly.

I am not talking about delaying adoption by waiting for long list of approvals to get some thing that would bring immediate value, but a carefully orchestrated plan for why and how to migrate to a new stack.

Just because one of the tech giants made a move to a new stack and wrote about it in their engineering blog doesn’t mean that you need to make a switch in the same direction. Take a moment to analyse the possible reasons that motivated them to do it, ask yourself if your organisation is struggling with the exact same problems, observe how others facing the same issue are addressing it, and then make an informed decision.
Collect enough data to support your proposal.
Ask yourself again if you are the one holding the hammer.
If the answer is no, forge ahead!

"Hey nephew, why doesn't the FB app work. It shows blank white boxes?"
- It can't connect or something? (I stopped using the FB app since 2013.)

"What is this safe mode that appeared on my phone?!"
- I don't know. I don't hack my smartphone that much. Well, I actually do have a customised ROM. But stop! I'm pecking my keyboard most of the time.

"Which of my files should I delete?"
- Am I supposed to know?

"Where did my Microsoft Word Doc1.docx go?"
- It lets you choose the location before you hit save.

"What is 1MB?"
- Search these concepts on Google. (some of us did not have access to the Internet when we learned to do basic computer operations as curious kids.)

"What should I search?"
- ...

"My computer doesn't work.. My phone has a virus. Do you think this PC they are selling me has a good spec? Is this Video Card and RAM good?"
- I'm a programmer. I write code. I think algorithmically and solve programming problems efficiently. I analyse concepts such as abstraction, algorithms, data structures, encapsulation, resource management, security, software engineering, and web development. No, I will not fix your PC.

Stackoverflow

When I was just starting with programming I used to google a lot (more) of my problems. But just just copying them made me feel guilty, since I could not handle the problem myself. So I decided to analyse a code to the point where i understand exactly how it works. Sometimes it took me a couple of hours to understand a method, which was written 1 or 2 levels over my current level, but it was totally worth it. I learned a lot about Java, how to write cleaner code in general and how to read and understand code quickly.

Install Kali
Configurate Kali
Testing with a VM
Testing with my own Network
FUCKED MY NETWORK FOR 4 DAYS
.
.
.
Analyse my Mistakes
Test again with my Network
Accomplished
Tested my Neighbours Network
Found 3 ways to get in less than 5 Minutes
Went to Neighbour
Said that his Network is pretty easy to hack
Earned 30€

Fellow devs,

If your boss asks you for an estimation don't follow your gut coz your gut sucks. Ask for time to analyse before giving any estimation. And yeah don't forget external factors such as :
- third party tool down (github I'm looking at you)
- updates (windows, IDE, etc.)
- 90% of the time it doesn't work
- if it involves front dev just go ahead and double your estimation
- YOUR BOSS THINKS YOU OVERESTIMATED

Sincerly.

Brain storming with senior lead developer. We try to add new tables in our database. But the Google spreadsheet goes wrong

I learnt something from every single project I made, but this one... it was really different, new language, new library, new hardware.

Problem:
there's an infopoint in a place, that was really hard to use (ball mouse over a monitor)

Solution:
make the screen be touch.

Developing the solution:
- after a bit of research I find out there's a library/project called OpenCV
- there are example programs that detect hands written in C++ (which I know) and Python (which I don't know)
- the whole infopoint works on a raspberry PI, with raspbian (I'm not new to linux, but it's somehow different, plus tons of customization)

So I spend like 3 weeks trying to understand how to make it work, at first, the webcam was on the TV and you could move the mouse just by shaking your hand, but it didn't work too well, so we tried making the webcam look at the screen and then calculate the differences between "no-hands" and "user-hand", but should have been calibrated, wasn't too precise... dropped solution.

put the webcam 30cm above the screen, let it just analyse a few centimeters of sight from the screen and it worked flawlessly, BUT it could just recognise the horizontal axis => had to rework the infopoint UI to make it dumb-easy

It all finally worked, I learnt python, openCV, a bit of photography

Then hated it all and decided to never do that again

Was on my first internship, told to analyse and prepare stuff for the Android dev to build an application for a big client. Did it before the end of the internship and team was satisfied with my job.

Because the Android dev had already lot of works on other stuff they let me start the development of the app.

The end of my internship is coming, the app is not finished but the team agreed that my work is not bad and that I should continue to work on it.

I finally get hired to finish the app, when we first publish it 95% of the code was mine and the boss started to stress because he let an intern (that became an employee) build the application from the ground. But the application got quickly its 4.5 stars on the playstore and more than 10.000 downloads.

I quit the job a few time after the publication of the app but I feel proud and happy that this team let me work on one of the biggest project they had as I was only an intern without any professional experience.

This is not "badass" but this is my first and best experience in the professional world !

My dissertation at university was to analyse chat logs of pedophiles in the hope that the application of a density metric could flag up both explicit chats between parties (which it did very well) and more importantly flag up potential on going grooming (it was a bit hit or miss) I love telling people about this because it freaks them out

The primary concept of reactive programming is great. The idea that things just naturally re-run when anything they rely on is changed is amazing. Really, I think it's the next step in programming language development and within a decade or two at least one of the top 5 programming languages will be built entirely on this principle.
BUT
Expecting every dependency to be used unconditionally is stupid. Code that checks everything it might need all the time even if a decision can be made from much less information is simply bad, inefficient code. If you want to build a list of dependencies automatically, you have to parse the source.
And I really hate that there are TONS of languages that either make the AST readable at runtime or ship with a very powerful preprocessor that could be used to analyse expressions and build dependency lists, but by its sheer popularity the language we're trying to knead into something it was never and still isn't meant to be is JavaScript.

If your “solution” fixes the test case which is failing, it does NOT guarantee that it is the correct fix. You don’t just blindly change whatever piece of code you like to make just the test case pass. You actually also need to analyse the code and ensure that the rest of the intended functionality is still intact.

Oh no AI can destroy hummanity in the future! It is like skynet and such... Bad! It will be the end! FEAR THE AI!

Yeah so i cant sleep now so im writting a rant about that.

What a load of bullshit.

AI is just a bunch of if elses, and im not joking, they might not be binary and some architectures of ML are more complex but in general they are a lot of little neurons that decide that to output depending on the input. Even humans work that way. It is complicated to analyse it yes. But it is not going to end humanity. Why? Because by itself it is useless. Just like human without arms and legs.

But but but... internet.... nukes... robots! Yeah... So maybe DONT FUCKING GIVE IT BLOODY WEAPONS?! Would you wire a fucking random number generator to a bomb? If you cant predict actions of a black box dont give it fucking influence over anything! This is why goverment isnt giving away nukes to everybody!

Also if you think that your skynet will take control of the internet remember how flawless our infrastructure is and how that infrastructure is so fast that it will be able to accomodate terabytes per second or more throughput needed by the AI to operate. If you connect it to the internet using USB 2.0 it wont be able to do anything bloody dangerous because it cant overcome laws of physics... If the connection isnt the issue just imagine the AI struggle to hack every possible server without knowing about those 1 000 000 errors and "features" that those servers were equiped with by their master programmers... We cant make them work propely yet alone modify them to do something sinister!

AI is a tool just like a nuclear power. You can use it safely but if you are a idiot then... No matter what is the technology you are going to fuck shit up.

Making a reactor that can go prompt critical? Giving AI weapons or controls over something important? Making nukes without proper antitamper measures? Building a chemical plant without the means to contain potential chemical leak? Just doing something stupid? Yeah that is the cause of the damage, not the technology itself.

And that is true for everything in life not only AI.

So new job started.
Just for context- old company was shit.
Promised the world but.
No benefits.
Terrible project management.
High pressure.
But green field interesting work (except by now it’s a few years in so it’s a ‘browning’ field but I was on it from the start).

New company first impressions..
Seems a fantastic company.
True to their word they have money for tools.
Making time for personal development.
Much bigger development community/department.
Seems like the term are under far less pressure so far at least.

But a MASSIVE amount of tech debt.
People seem to want to do the right thing and they’re making time to try and deal with it.
But one or two are very opinionated as to how to deal with it.

So this could go either way and only time will tell I guess.
Trying not to over analyse every little thing they say but I’m hyper sensitive to it at the minute while in the early days.

As always the real challenge in IT is the people not the tech. I count myself as part of the problem, sure I will form some opinions and sharing them too.

[Working on some really "urgent" report for an about to publish project]
dev: client, can you explain what this value is? we can't figure it out and we though tha...
client: im gonna stop you right there, DO NOT Analyse! we dont have time for silly questions, if the design says there's a 10, just put that freaking 10 in that place...
dev: but sr, we need to...
Client: what did i say? just stop saying things and build it!

Hello and welcome, to a presentation in which I will tell you my thoughts on the shortcomings of modern day computers and programming practices.

Computers are based on a very fundamental and old idea, folders, and files, a file is basically a concrete amount of data, whereas a folder is a group of files, and it comes from the real life concept of files and folders, now it might be quite obvious already that using a concept invented in 1898 by a guy called Edwin G. Seibels, might not be the best way for computers to function in the year 2020, but alas, it is.

Unless of course, you step into the world of a programmer.

A programmer’s world is much different, they use this idea of a data structure, or in simpler terms, an object. An Object is just like what you would think of as an object in your head, something with different properties that you can think about in different ways, for example your mobile phone, it has a battery percentage, it has a screen size, it has free space available. Programmers use these data structures to analyse data very quickly, like finding all phones with a screen size bigger than a certain size for example.

The problem is that programmers still use files and folders to create the programs that use these objects.

Consider this example.

Let’s say you want to create a virtual version of a drink bottle, consider what properties it will have, colour, volume, height, width, depth, material, etc..

As a programmer, you can leverage programming features and change the properties of a drink bottle directly, if you wanted to change the colour, you just say, drink bottle “dot” colour, equals blue, or red.

But if the drink bottle was represented as a file, all the drink bottles data would be inside the one file, so you would have to open the whole file, find the line or section of the file that has the colour data of the drink bottle, and select it, highlight it, delete what’s there, and type in your new value.

One way to explain this better is to imagine a folder that now represents the drink bottle, imagine adding a new file into that folder that represents each property I described before, colour, volume, etc.., well now, you could just open that folder, find the file for colour, either by looking with your eyes or you could do a file search in the folder for a file called colour, open it, and edit the value inside. This way of editing objects is the one that more closely represents the way programmers and a program itself interacts with objects inside a running programming language.

But the thing is, programmers don’t use the folder/file way of creating objects and putting them into programs, because it would be too cumbersome, they just create 1 file for an object, or have lots of objects in a file, and create all the objects in 1 file, and then run the program which creates the objects, then when they stop the program, it deletes the objects. So there is no actual link between the object in a file and the object that the program creates by reading the data from that file, if you change the object in your program, it does not get saved to the file.

So programmers created databases to house these objects, but there is still a flaw in databases, they are hard to interface with, and mostly databases are just used to send data or retrieve data from, programmatically, you can’t really browse a database the way you can browse the files on your computer. You can, but database interfaces are not made to be easily navigated the way files and folders are.

As it stands, there is no way to store objects instead of files on your computer and interact with them in complex ways the way programmers can inside the programs they create.

If the idea of an object became standard the way a file and folder is standard, I think it would empower human’s a great deal to express things far more easily and fluidly than they can today.

Thanks for reading.

Bug requires 2 developers, full-time for 4 days to trace, debug, scratch heads, analyse logs. Third developer helping occasionally. Finally identify fix. Fix is 2 lines. D'oh.

My IoT professor expects us to, somehow, learn Machine Learning and use that to analyse the data we obtain in the working of our project! How are we supposed to learn ML to implement it's techniques, while simultaneously create a IoT project, learning its own techniques and also handle our other courses in just one semester?!

Don't you guys think we need live programming?

Like a development runtime, instead of doing this whole file based development thing? We edit files, and then run them, why aren't we just running a program constantly and editing it as it runs? It would let us inherently take advantage of concepts like objects and lists instead of having to build plugins that analyse and modify our files to sort of act like complex programming data structures.

If we just programmed using these complex data structures to begin with.

Like do you realise how antiquated the idea of a file is, and folder, that's literally a paper based analogy.

Imagine if we just had objects, with pointers and property names, the best we have is ln -s file1 file2 but that's not a real pointer.

Anyway, hope someone understands me!

I'm writing a medium article called a world beyond files but I'm stuck at how low level to go and who the audience of the article should be.

I went really in depth into what this idea of an "object" is, and how it can be expressed in a file but once a program picks it up it becomes much more and almost alive.

Each time I try to study someone else’s (cool) JS files, to learn from it, there are always some funky function calls that throw me off. I wish the person could be beside me and just walk me through why they did what they did at each step.

It’s just tough sometimes. I see all these cool projects on GitHub and I go, “let me try to analyse it,” and then I see all these properties too. Sometimes I feel compelled to just check the API but it seems like I’d be going into a blackhole of never-ending API depths.

What are some tips that you JS pros have?

I’ve been bashing my head against a project for the past 8 weeks. The project creates a PDF pulling data from multiple APIs, scrapes and private DBs and plots charts using Plotly. We built it with Python, wkhtmltopdf and Celery+Redis. The input is an excel with a list of up to 5 influencers to analyse and compare. Runs on demand on a Linux machine and each report takes around 20 mins to generate. The project has no unittests so the only way I can check everything works is by running a bunch of different inputs. Even though you test 10 inputs (taking you more than a day), there is a high chance something goes wrong on the 11th input. I’m thinking that the only way to fix this mess is to go back to the drawing board and plan yet another refactoring to add unittests everywhere. What do you guys think?

I prefer it doing 2 tasks parallely during the initial phase of requirement gathering and design phase.(makes more sense if you are working extremely new system and framework)
1. Keep collecting requirements from clients and understand them.
2. Collect different designing aspects for the project and parallely, build a POC for 2 purpose: to get hands into the new Framework and also as a demo to clients. Working on POC helps in 3 ways: Improving understanding of requirement, improving framework knowledge, and playing around with code whenever bored of designing and reading tons of existing designs..
3. Once primary requirements are clear and fixed, analyse all different designs, if possible I setup meetings with senior devs, principal engineers (they help a lot when it comes to reviews on scalability and reliability of a design)
4. The above design is mostly architectural level. Once design is fixed, then I start taking each component and prepare a detailed implementation design. (Notice that whenever I am bored of designing, I spend sometime in building POC)
5. In detail design, I focus on modularity and flexibility. Anything defined should have getters and setters for example. This will help you reuse your code. Keep the interface between components in your design as generic as possible, so that in case your MySQL is change to Postgre or NoSQL, your design should be able to adapt new features..
6. Instead of building entire project, define feature targets and deliver small features.. this will help you to be in line with the requirements with minimum deviation.

Me, working hard on a SQL project with a deadline that is half what it should be with no support from the other people on the project and was mostly made with with data I imagined would be in there cos no one could get me any fucking shit done (i.e. effectively designed, built, tested, fixed, upgraded, documented on my own for an entire weekly/monthly/ad-hoc analysis process that would output various reports for internal/external/management)

Manager - man who is a known waste of space but for some reason is in charge of the smallest part of the project, shouldn't have been fucking involved fucking management guzzling stain magnet...

Manager: Hey, do I need to refresh the database?

Me: .................

Me: .................

Me: ............I dunno, do you think we should refresh the database that this entire project is reliant? I mean...why do we need up to date transactions to analyse? Wait....you telling me it's not been being refreshed this ENTIRE time?

Manager: No....you never said I should. So should I?

Me: ..................I never said you should!?!? Are you not in the meetings talking about dependencies?????? Do you think i should have up to date trans or just run this with old stuff????? Why would you not update it!??!!?!?!? Its transactions...... (Desperately trying not to punch through my screen, through his, into his throat)

Manager: ..............

Me: .................

Manager: I think i'll refresh it and add it to the job?

Me: ....................(goes back to work cursing with music in so I think its quiet but who knows).

Tard, don't know how he even gets to work without someone holding his fucking hand.

Happy ending, I don't work there anymore :p

Sad ending, his spirit of tard follows me to my new jobs and possesses someone (or three sometimes)

I don't know how it's out there, but where I'm from, we don't get a lot of practical classes. The curriculum has tried to include practical alongside theory but its just not working. All we do is theory and more theory. Maybe include a major portion of marks for practicals rather than theory. And yes, please no coding in paper.

Another major thing we lack is teaching logical thinking. I have met final year under grads who find using a (!foo) to invert the value of foo mind blowing. They would rather use a full blown if-then statement to do the same. I think we need to incorporate chapters that motivates students into logical thinking to make better programmers.

Another essential part CS education around here lacks is in relevant examples and chances for internship. If you're studying something, I believe you would understand it much better if you see and experience it. Curriculum should include a real world project that you would use in a daily basis. Maybe break down and analyse a successful application and its component.

I study and analyse all these intricate things and you think all I do is fix PCs? How dare you!

!rant
I did just talk with a client because they tried to analyse some data we send and they fucked up. the client told me they can't fix it because they cnat access the data because they have a divious virus. xD you're the god damn IT department of a pretty big company. wtf? really how?

Hello devs. I just doing analyse about Prestashop. I need answers.

Why not to use Prestashop?

Nothing much to ready today, keep scrolling..

I just asked you to keep scrolling, I am using this space to think out loud...

Damn you bloody rebel.. whatever..

Finally after a rough week, festivals, interviews, work stress, and pending tasks, I got a free weekend for myself to be with myself.

I managed to do bare minimum at work. My new line manager isn't quite pleased with how team and I am functioning but whatever.

On Fridays, I usually end the day early and start with personal tasks. I managed to finish some long pending activities.

Today, I was able to do a deep cleaning of digital housekeeping. Sorted some clashes with parents. manage to de-stress and relax my stiff neck muscles.

Apart from that I guess, I am all prepared to interview and get hired for a company on foreign land. I am confident that I can relocate to EU.

And for now, I am actively pursuing two of my hobbies, Music and Finances. I love managing my finances and learning more about technical aspects of audio and listening to more and more music.

I feel happier, relaxed, and calm. Having things under control is such a wonderful feeling.

And I am slowly building a framework to earn, manage, invest, and grow my finances. It's turning out really well. I have setup the base infrastructure.

For music, I have figured the fundamentals and now I will go out buy myself an DAC/AMP to build a portable rig.

This shit is so awesome and makes me happy. I am able to socialise at the end of each day so that keeps me going during the lock-down phase.

I have figured the top key and important things to do at work for my profile and I actually enjoy those.

1. Product discovery - talking to users/customers and finding their pain areas and opportunities to build the solution

2. Product vision/strategy - Dreaming on how the product would evolve and laying out a solid plan to materialise those dreams.

3. Roadmap and prioritisation - this should be self explanatory

4. Success metrics - I really want to get into data and I am getting opportunities to do so. This is super fun. This will help me analyse and show the impact of the what we are building and measuring it while making sure that LT recognises my and my teams' efforts.

I want to and I will excel these 4 keys skills of my profile and be more efficient at my job.

This will give me more time to pursue my hobbies (which will change over time and want to enjoy them the most while I am at them).

Guys, after a rough 2021, the end of the year seems promising with a lot of leaves and short vacation coming up.

Apart from all this, what is more important here is that I got the career and life clarity that I was struggling with for past few months.

For whoever has read till here, YOU ARE BLOODY AWESOME and thank you from the bottom of my heart for being there for me always.

I am grateful to be a part of this community and have awesome friends like you all who have been with me though my ups and downs since 2016.

LOVE YOU ALL :)

Since I quit binge-eating sugary stuff, my body became capable of feeling true hunger. Not in my stomach, as that kind of feeling in my body is probably fucked up forever, but in my head.

When I feel hungry, it’s probably too late. This is exactly what I feel:
- dizziness
- FOV slightly decreases
- tunnel vision, things in peripheral vision become blurry and obscure. I “see” them, but my brain doesn’t process them quite as good
- colors become less saturated
- it’s very difficult to combine and analyse multiple concepts to derive a conclusion, basically the thing I do at work that wins me bread
- thought process becomes “single-threaded”. I can follow just one thought at a time and cannot go deeper than 3-4 levels, my brain just drops it by making the whole thought feel like some kind of slimy clay that cannot be comprehended, let alone expressed with words
- difficult to express thoughts with language, I have hard time talking, especially explaining
- want to sleep, but can’t, as brain is frantically trying to stay awake

It’s probably the mechanism developed evolutionary. That single thread remains active at all costs to allow me to find food, and brain doesn’t let me sleep, as it thinks if I fall asleep I’ll die. It’s amusing to see my brain actively killing thoughts that are not “important”, I feel like a real-time OS or an Erlang application. Perhaps thinking is really a very costly process in terms of how much energy it takes.

When I finally eat something, especially if it’s a proper meal, I feel a very pleasant sensation, probably it’s my brain telling me “thank you”, releasing dopamine to actively reinforce that “finding food is a very very good thing and it’s very important”. FOV pops back into place, peripheral vision becomes clean and sharp, thoughts awaken, eager to occupy all the treads that became available.

Is there any other job where you can analyse a problem by breaking stuff?

Need to analyse the sentiment of any given text input in C# for assignment.
Can't find a library for it but i might not be searching the right thing.

Any ideas?

Think of an awesome sounding AI project while not knowing a thing about AI.
Tell the guy you will be working with that you will manage to keep the learning pace up (he doesn't know AI as well, woah!)
Fast forward 2 weeks - completely forget about how I wanted to do anything with AI.
Fast forward 1 week - that guy messages me that we ought to do a meeting to check how much each of us have learned and to decide on how we will tackle the project.
Somehow managed to get the deadline to be day after tomorrow.

'I am screwed...' is what I think when I skim through pages of 'Artificial Intelligence a Modern Approach'. So, I put down the book and try to find something easy to understand on youtube. I find a hyperactive looking guy that under a video titled along the lines of '5mins and you are linear gradient pro'. Not suscipious at all.
Watched video twice, managed to understand that I need calculus for this shit. Oh well.

AI seems so much fun until you understand that it requires a fuckload of knowledge to do anything at all! :'(

Going to try to analyse linear gradient until tomorrow and hope that it will be sufficient for our project.
Lol. Who am I kidding?

Terraform + helm-chart ... I really ned a break. Who the fuck invented this shit.
The HCL format sucks
The documentation sucks
The dev tools suck
The debug output sucks

But I'm ok with that, I can manage.
But today really it shot the bird ... I can't have a fucking comma in a string? Because idk why the fuck helm-release tries to parse that fucking string and wants to make an array or whatever out of it? Why, you fucking abomination?
Something in the docs? Nah, who reads them anyway.
Because you know it's totally not strange that a string is analyse and oh wait there's a comma in it, the dev surely wants me to make an array out of it, because you know ...
So now I have to escape my fucking comma to prevent it to parse my fucking string. I just want to have a fucking string you hideous monstrosity ....

Hey guys,
I have to Select my Bachelor thesis/topic in the next few days. I would like to do something with Crypto Currencies especially with the Blockchain System. There is a wide range of usage for that and i Think it could be very interesting.
The Problem is that am Not Really Sure what Topic or challenge my Project could contain. There is much to say about it but i dont Think it would be enough to just describe it.
There should be a Problem or anything like that I can solve..
Or Is it possible to just Analyse the blockchain and the affect it have These Days and the Future?
I would appreciate a few ideas or suggestions :)

Regards
Birdy513

Today I used NDepend to analyse my new jobs code base. It looks like the classic big ball of mud :(

I live under a rock.. sooo notepad++ for me..or even a paper notebook..

Joke aside, depends what kind of code I'm writing or what I'm doing with it.. if I have to analyse what some part does and modify it I actually do take it from VS to np++ to check & write.. same for PLSQL.. not sure why I prefer doing this the 'hard' way, but it suits me.. after I'm finished I'm pasting it back and correct possible typos and so on..

P.S. I'm also one of those weirdos who have no problem writing exams on paper..