It has to be the community. Just look at devRant - an open community where - unlike on the rest of the internet - people are friendly and warm. Then there's the concept of open source and GitHub, where people post large and complex projects for free and even the smallest of developers can create issues and pull requests (shouldn't they be called push requests though?) - no other profession will help others out in over 15 million different ways.

A repo on GitHub I'm maintaining has grown with 200k downloads / month since I started working on it a year ago. My recipe? I added an npm badge in the readme showing downloads / month and I responded to every issue and reviewed every PR. Now there's so much issues and PRs coming in that we had to add an extra maintainer, feels great! Teamwork, fuck yeah!

Not every PR got merged of course, but every single one of them got reviewed. Just being a good and friendly developer, giving back to the community that has given me so much. Some tips for you maintainers out there. If you have a popular project and no time there's always someone else who's willing to spend time on it, ask around and you will surely find someone else.

Enjoying this friendly, yet unformal and sarcastic community :)

Is this community newbie friendly or is this just for established devs?

The folks on steam are so friendly, devRant ain't got shit on them.

I've been using microsoft dev stack for as long as i remember. Since I picked up C#/.NET in 2002 I haven't looked back. I got spoiled by things like type safety, generics, LINQ and its functional twist on C#, await/async, and Visual Studio, the best IDE one could ask for.

Over the past few years though, I've seen the rise of many competing open source stacks that get many things right, e.g. command line tooling, package management, CI, CD, containerization, and Linux friendliness. In general many of those frameworks are more Mac friendly than Windows. Microsoft started sobering up to this fact and started open sourcing its frameworks and tools, and generally being more Mac/Linux friendly, but I think that, first, it's a bit too late, and second, it's not mature yet; not even comparable to what you get on VS + Windows.

More recently I switched jobs and I'm mainly using Mac, Python, and some Java. I've also used node in a couple of small projects. My feeling: even though I may be resisting change, I genuinely feel that C# is a better designed language than Java, and I feel that static type languages are far superior to dynamic ones, especially on large projects with large number of developers. I get that dynamic languages gives you a productivity boost, and they make you feel liberated, but most of the time I feel that this productivity is lost when you have to compensate for type safety with more unit tests that would not be necessary in a static type language, also you tend to get subtle bugs that are only manifested at runtime.

So I'm really torn: enjoy world class development platform and language, but sacrifice large ecosystem of open source tools and practices that get the devops culture; or be content with less polished frameworks/languages but much larger community that gets how apps should be built, deployed, monitored, etc.

Damn you Microsoft for coming late to the open source party.

Linux is hard to learn and master. That's fine with me. Windows is intuitive, but not user-friendly. Linux has a steep learning curve, but then is far more user-friendly than any other operating system. To me, that steep learning curve was far more than worth it, as I now have a desktop that does whatever I want, and behaves exactly as I want.

People come to Linux hoping that it will be easy to pick up, and then get angry when it isn't. Then they claim that the community is toxic, because Linux users are happy with something they think is broken.

Linux is hard to learn, and that's fine. That's valuable, to me. That's part of the appeal to me(and millions of others). Linux is unforgiving when you lack the knowledge gained in that steep learning curve. That's fine with me too. As its userbase grows, so too does the number of knowledgeable people who work to make it better and invent more amazing things for it.

If Linux was easy to learn, it wouldn't be as good as it is, and to me, that's reason enough to love it.

Dev Community

On Facebook groups- most are scams.
On SFO - strict.
On Reddit - Somehow helpful
On Telegram - 'nobody cares about you'
On Wechat or CSDN - They curse you.
On Dev.to - incomplete.
On Gitter - 'no body cares'
On slack - boring.
On Naver blog - somewhat helpful.
On whatsapp - crypto referal links everywhere
On Twitter - 'JAVASCRIPT bla bla bla'
On Google GRoups - classic
On discord - friendly

So far what I experienced, what about you guys?

devRant community is so awesome. I recently joined and everyone is so welcoming and friendly. Thanks! :)

Update on my Facebook and Booking.com interviews. I had them back to back today.

Even before I start, I accept and admit that I am a hypocrite. I hate Amazon yet order stuff from there. I hate Microsoft yet use their products. I hate Facebook yet went ahead to interview with them.

I fucking hate myself for compromising my ethics, values, and integrity. I had promised myself that even if I work for any major shit company, I'd never go with Facebook. Here I am after many years. Not an excuse, but I am doing it because I see it as an entry point into the UK. That's all.

Community's hate towards me is justified and I'd accept the discrimination from this community because this place is my digital home and you all are my family. Infact first thing I told mom was, dR boys are gonna disown me when they get to know about this.

Anyway, coming to the update part.

I had applied leave at work from last Friday. 4 days of leave earned me 10 days off (including weekends and 2 days of Diwali company holiday).

Last Thursday I got to know that Facebook has scheduled their interview today (Friday). I spent insane amount of time preparing. Approximately 8 hours everyday including weekend. I added nearly 40+ hours preparing for it in last 7 days, because I had to get in. Failure isn't an option now.

I sacrifice my family time, preparing for the interview.

I sacrifice Diwali break, sitting in front of the screen and studying.

I sacrifice my only vacation of 2021, doing mock interviews as late as 11.30 PM.

I sacrifice my free time and enjoyment, stressing over what could happen.

I was prepared like perfect for screening stage.

Interview 1: this guy comes and ask 'what is the best compliment you have got as a PM?' and 'Why do you want to quit the current company?'

He wasn't supposed to ask those as per Facebook's policy and interview stage.

Then he gave me a shit problem to solve and rejected my approach and wanted it his was. I tried to follow him and made sure I was able to convince with the reasoning but he kept pushing me back. He kept putting me down. Did not listen to me or what I had to convey or what was expected as an answer. He had certain output in his mind and wanted me to come up with it as an answer.

For the uninitiated: Facebook gives ton of preparation material and tells upfront the kind of questions they'll ask they just focus on few things. Moreover, in Product interviews, there isn't right or wrong answer.

Anyway, this guy started making funny expressions which put my morale down and I stood my ground with losing my cool. I managed to get all my answers right and the key points the look into a candidate. It went decent. Yet the interviewers attitude was something I did not like.

Interview 2: the lady was really kind and warm. Very accommodating and easy person to deal with. It went amazingly well.

I have two observations I want to share with you all.

1. I hate what Facebook does. Lizardberg is awful human being. But I absolutely liked HOW they are doing things, at least from an interview stand point. They even had mock sessions by their PMs and upfront told how to prepare and how to answer.

2. While it seems to be a 5 star experience, I found them to function mechanically. No small talk, no human connection (ironic to their mission), no conversational flow of the interview (again something that they kept saying a zillion times in all their material). They came, formally introduced themselves, and had a checklist kind of attitude, and left.

I now await for the feedback.

In the next hour, I had Booking.com first round.

Amazing people. Warm friendly experience. Treated me as a human. Heard me. Made me feel part of the conversation rather than someone just being judged.

It went 1000x better than Facebook.

I await the feedback from them as well.

I don't know what's gonna happen but one thing for sure, the kind of expectations Facebook set for their interviews, was nowhere close to the reality. It was awful.

180° was for Booking.com

Guess the saying stands true, expectations always lead to disappointment.

Finally I feel de-stressed and my Diwali vacation starts AFTER Diwali ended. Or rather just a regular weekend.

2021 has been terribly awful year for me. Hope this shitty year ends soon.

Just signed up today and I have spent the last few hours on here. I don't know how you guys get any work done while being members on here :-P

Thanks for being an awesome and friendly community.

Now I'll have to figure out a way to collect all the points!

I haven't really known what to post. But I've decided not to care about being relevant or care about the like count. I'm a very competitive person so things like like count tend to effect the way I see the quality of a post.

I want devRant to be a place where I can be honest and feel safe even if I don't get the validation I sometimes wish I had. And hey maybe someone will think my opinions or thoughts are interesting.

So let's start with a little about me. I'm a 17 year old kid that loves programming. I work full time as a full stack web developer and I'm really the only web person. The current system is built on WordPress because of fucking course it is. I don't like it but I gotta keep it user friendly for less techy people to manage. No one likes have all minor changes and tweaks having to go through one person when they could do it themselves. So I manage.

I'd say my passion is more backend development but I do love having a pretty UI to display the results.

I've struggled with mental health the past few years but I'm doing much better. Even just last week I had an anxiety attack during a social event. I came here for the community and I do enjoy it, but I'm gonna try to make it an outlet. My best friend went off to university and I don't really have any IRL friends I can just be me around.

I don't have anything special to say. But if you read this thank you for listening to some random kid on the internet. I hope you have a great day.

Hey guys,

I think the topic of this week is very important.

Older, experienced devs are giving their skills and advices to the younger one.

Some of you maybe know it, I'm a young developer, who started his apprenticeship at september.

I'm feeling good there, the others are friendly. I learn a Lot there. I had experience before I started there. It's my Hobby to code so I started coding when I was 14.

You can't know anything, everyone makes mistakes, this is what I've learned and this is important to remember.
There are these days like today, when your Boss isn't there and you have to work alone. You have to do many things, and you are desperated because nothing Works, you can't ask anyone, you are completly alone. There are these days, when nothing seems to work. But there are also these days when everything Just Works fine and you are happy with yourself.
This is important to remember.
For me its very hard. Days like today are driving me crazy and I'm very sad, even when I know, that this is Kind of normal not to know everything and have Problems, especially when you are young as me and started your first apprenticeship 3 months ago.

Tomorrow I'm also alone, I'm a Little Bit feared of tomorrow (you say that in that Way? :P) When I think of tomorrow and that I don't know How to proceed and sitting there, I'm getting frustrated and Kind of sad. But I know that this will Make you even better some day, because you learn and gets better - day for day.

At least there was something good today. My stickers finally arrived! To Germany! That was fast! Thanks everyone, Thanks! And Thank you @dfox for building this great community!

What are you advices? And how you handle these situations? I hope tomorrow everything Works fine :/

I worked on a game jam last year, and for the first time I managed to finish a full software project that wasn't for a job or university. It was really fun to work on, and seeing my vision come to life, even if compromises had to be made, as well as applying all the programming and project management knowledge I'd picked up until then was an experience unlike anything I'd had before.

The community aspect was great too, everybody shared and discussed each other's games and were super friendly and encouraging.

My friend told me to join this app/community and I am so happy that i did mainly because of the friendly community and ofc humourous posts about coders life

🐙/* Friendly reminder */ 🐙

Don't forget about Hacktoberfest, a great way of giving back to the open source community 👨‍👩‍👧‍👦. And remember, if you create at least 4 pull request you'll get a t-shirt! 👕👚

!dev

I didn’t posted for a while cause I didn’t have anything interesting to say. My job is fine, got no major problems in life, everything looks good so I started thinking about the fucking civilization future stuff.
Either I’m to old or we’ll end up back in ancient Egypt one day.

The knowledge is still not moved from old to young, not categorized and protected well enough and we’re busy fighting with each other about nothing important. We’re carrying about stuff that have nothing to do with our lives. All those fucking movements make world worse place then it was. Just marginalize those that are good and give more powers to those who shout more and have more money.

As a result I think in a matter of couple generations there won’t be anyone who could replace grandfathers keeping this machine alive and future people will end up looking at pictures and videos of ancient stuff that nobody is capable of doing cause nobody understands it.

This super friendly human politics of the world like any other politics will make people unfriendly and not able to communicate with each other - stupid and unable to think reasonably.

My advice I also took as a mantra, turn off the internet and read or listen to the books - at least one book a month is your goal.
My last book I listened to was about history of gender and you know what ? I learned that clown fish can change gender when it’s young. I learned more from listening to this book for 8 hours then from a year reading stupid articles in the internet. I understand what gender is, what are the problems and all the fucking history of it staring in 1800-something or maybe even earlier. Maybe because there is still lots of difficulty to write something interesting that is more than 1 page of paper long. Most of stuff in the internet weather it’s an article or video have only 1 page amount of content. This content is none, it have no value to the community. You won’t learn anything from it. If you want to learn something read book cause making good quality book is very expensive and takes lots of person life and self esteem. Probably one book takes more time then most of influencers spend making their stupid pictures and stuff like that.

That’s sad truth of our times. We turned technology made for knowledge exchange to advertising tv - again.

1) Never be afraid to ask questions.

There are so many instances of situations where assumptions have been made that shouldn’t have been made, resulting in an oversight that could have been rectified earlier in a process and wasn’t.

Just because no one’s asking a question doesn’t mean you’re the only person who has it.

That being said, it’s really important to figure out how to ask questions. Provide enough context so that the audience for your question understands what you’re really asking. If you’re trying to troubleshoot a problem, list out the steps you’ve already tested and what those outcomes were.

2) When you’ve learned something, try to write about it. Try to break it down as though you were explaining it to a child. It’s through breaking down a concept into its most simple terms that you really know that you understand it.

3) Don’t feel like you have to code *all of the time*. Just because this is what you’re doing for a living doesn’t mean that you have to make it your life. Burnout is real, and it happens a lot faster if it’s all you do.

4) Find hobbies outside of tech!

5) Network. There are a number of great communities. I volunteer for and am a member of Virtual Coffee, and can vouch for that community being particularly friendly and approachable.

6) Don’t let a company pay you less than industry standard and convince you that they’re doing you the favor of employing you.

7) Negotiate salary. Always.

8) If you’re a career transitioner, don’t be afraid to talk about your previous work and how it gave you experience that you can use in programming. There’s a whole lot of jobs that require time management, multi-tasking, critical thinking, etc. Those skills are relevant no matter where you got them.

9) If it takes a while for you to get a gig, it’s not necessarily a reflection on you or your abilities.

10) Despite what some people would say, coding’s not for everyone. Don’t feel like you have to continue down a road just because you started walking down it. Life’s not a straight path.

Hey guys, this is my first rant. I like this friendly community very much so far and hope it stays that way. So here it goes...

I have this Trello app on my Android phone. It has this nice feature - calendar... But week starts on Sunday. So I started investigating, how I could change it to Monday. Googled and found that you have to change the language, which I did. Now I wish I had this nice ISO date format yyyy-MM-dd, but this motherfrakker doesn't allow me to!

How much I hate this little piece of shit! What does he want from me? Download the sources, add the functionality, compile for a week and flash it into my Xiaomi?!

!rant
How about a feed where people can ask for help?

I know there are sites such as stack overflow for things like that, but I find devrant's community to be a lot more friendly and just better overall.

Also I believe it would be kinda funny if the questions would not be required to be 100% dev related.

I saw a lot of rants about StackOverflow and its community.
I really couldn't understand, I always found friendly comments and answers, so it was hard for me to imagine why the community was tagged as "sadist assholes".

Then I found this gem and all was suddenly clear.

🔥👽🤘🏻
I've been CRUSHING it lately, so stoked!!!
**Also, this means that in the near future something will crush me because I have a few subjects on deck I need to lock down.

1. Deno

2. TypeScript(deep dive)

3. CPP (currently 75% done with my 2nd masterclass, first one complete)

4. Multi-platform local device storage (Sqflite/mongoDB/shared preferences/Hive)

5. REST/api/requests/json management && application

6. Implementing Firebase authentication using Apple, Twitter, and mobile OTP

7. Cloud functions && server scripting/automation

8. Intro to embedded systems/OS/kernels

9. Steadily improve my code style, design strategies, and build patterns that are team friendly && provide easier code base maintainibilty

10. Influence, teach, and/or spark the interest of someone new to development in any possible- all that matters is getting new people on board, making sure they are stoked about, and last but not least making sure they feel welcome in the community and are able to start off in the right direction.

cheers, ya fockers!!!!

is being a tech/dev person, a dead end job?

i have been thinking about this for sometime. as a dev, we can progress into senior dev, then tech lead, then staff engineer probably. but that is that. for a tech person :

1. their salary levels are defined. for eg, a junior may earn $10k pm , and the highest tech guy (say staff engineer) will earn $100k pm, but everyone's salary will be spread over this range only, in different slots.

2. some companies give stocks and bonuses , but most of the time that too is fixed to say 30% of the annual salary at max.

3. its a low risk job as a min of x number of tech folks are always required for their tech product to work properly. plus these folks are majorly with similar skills, so 2 react guys can be reduced to 1 but not because of incompetency .

4. even if people are incompetent, our domain is friendly and more like a community learning stuff. we share our knowledge in public domain and try to make things easy to learn for other folks inside and outside the office. this is probably a bad thing too

compare this to businesses , management and sales they have different:
1. thier career progression : saleman > sales team manager> branch manager > multiple branch manager(director) > multiple zones/state manager (president) > multiple countries/ company manager (cxo)

2. their salaries are comission based. they get a commission in the number of sales they get, later theybget comission in the sales of their team> their branch > their zone and finally in company's total revenue. this leads to very meagre number in salaries, but a very major and mostly consistent and handsome number in commission. that is why their salaries ranges from $2k pm to $2-$3millions per month.

3. in sales/management , their is a always a room for optimisation . if a guy is selling less products, than another guy, he could be fired and leads could be given to other/new person. managers can optimise the cost/expenses chain and help company generate wider profits. overall everyone is running for (a) to get an incentive and (b) to dodge their boss's axe.

4. this makes it a cut-throat and a network-first domain. people are arrogant and selfish, and have their own special tricks and tactics to ensure their value.

as a manager , you don't go around sharing the stories on how you got apple to partner with foxconn for every iphone manufacturing, you just enjoy the big fat bonus check and awe of inspiration that your junior interns make.

this sound a little bad , but on the contrary , this involves being a people person and a social animal. i remember one example from the office web series, where different sales people would have different strategies for getting a business: Michael would go wild, Stanley would connect with people of his race, and Phyllis would dress up like a client's wife.
in real life too, i have seen people using various social cues to get business. the guy from whom we bought our car, he was so friendly with my dad, i once thought that they are some long lost brothers.

this makes me wonder : are sales/mgmt people being better at being entrepreneur and human beings than we devs?

in terms of ethics, i don't think that people who are defining their life around comissions and cut throat races to be friendly or supportive beings. but at the same time, they would be connecting with people and their real problems, so they might become more helpful than their friends/relatives and other "good people" ?

Additionally, the skills of sales/mgmt translate directly to entrepreneurship, so every good salesman/manager is a billionaire in making. whereas we devs are just being peas in a pod , debating on next big npm package and trying to manage taxes on our already meagre , "consistent" income :/

mann i want some people skills like these guys

Drupal 8 fractured the community, dead ended projects that had years of being built up and supported, started a downward trend in overall number of websites using Drupal when it was still increasing market share, homogenized Drupal with other less successful frameworks that had already attempted it and failed by using composer to replace drush, twig to replace PHPtemplate, and Symfony to butcher Drupal and hang parts of it on.

The mission statement was to "bring Drupal to the modern era" and "be more enterprise friendly". All I've seen them do is make it worse. I have stopped using Drupal now, I still maintain some Drupal 7 sites but now that they killed the Drupal 7 community it's basically dead. Some small attempt was made to salvage it with Backdrop but it will likely never be as big as Drupal was and is mostly dead itself, for one thing it's not directly compatible with the huge library of modules either.

Another thing I loved killed by those without vision and giving into the "industry standards" that make one question the intellect of everyone who subscribes to them being a good idea. But hey that evil procedural programming that worked so long for so many was finally defeated. It's surely better now right... right?

At least this movement was supported by people that can't even tell the difference between the use cases in real projects between Drupal and Wordpress. Software Development is in such a good place and has no hypocrisy. One would never suggest it has lost sight of its original purpose of solving real world problems with computing and become self absorbed with its own navel gazing.

If still in doubt check attached image, it tells a very clear story about how to ruin the life of a CMS. It honestly feels like a hitjob attempted to sabotage it rather than an earnest attempt to improve something that has been doing well since 2001.

WHY ARE GRAV SLIDESHOW PLUGINS USELESS FUUUUUUUUUUUUCK

OWL SHORTCODES DOES NOTHING, LIGHTSLIDER DOCUMENTATION IS THE VAGUEST THING EVER AND THEIR NON-MODULAR EXAMPLE DOESN'T WORK, AND THERE AREN'T GOOD ALTERNATIVES.

... I ended up installing Bootstrap on the site just to get the slideshows working. It looks like shit and is bloating my page so I'M EITHER FIXING THOSE PLUGINS OR SWITCHING BACK TO WORDPRESS. IT MIGHT BE HORRIBLE BUT AT LEAST IT'S FRIENDLY AND THE COMMUNITY DOESN'T IGNORE ME ON THE SLACK CHANNEL

During my small tenure as the lead mobile developer for a logistics company I had to manage my stacks between native Android applications in Java and native apps in IOS.

Back then, swift was barely coming into version 3 and as such the transition was not trustworthy enough for me to discard Obj C. So I went with Obj C and kept my knowledge of Swift in the back. It was not difficult since I had always liked Obj C for some reason. The language was what made me click with pointers and understand them well enough to feel more comfortable with C as it was a strict superset from said language. It was enjoyable really and making apps for IOS made me appreciate the ecosystem that much better and realize the level of dedication that the engineering team at Apple used for their compilation protocols. It was my first exposure to ARC(Automatic Reference Counting) as a "form" of garbage collection per se. The tooling in particular was nice, normally with xcode you have a 50/50 chance of it being great or shit. For me it was a mixture of both really, but the number of crashes or unexpected behavior was FAR lesser than what I had in Android back when we still used eclipse and even when we started to use Android Studio.

Developing IOS apps was also what made me see why IOS apps have that distinctive shine and why their phones required less memory(RAM). It was a pleasant experience.

The whole ordeal also left me with a bad taste for Android development. Don't get me wrong, I love my Android phones. But I firmly believe that unless you pay top dollar for an android manufacturer such as Samsung, motorla or lg then you will have lag galore. And man.....everyone that would try to prove me wrong always had to make excuses later on(no, your $200_$300 dllr android device just didn't cut it my dude)

It really sucks sometimes for Android development. I want to know what Google got so wrong that they made the decisions they made in order to make people design other tools such as React Native, Cordova, Ionic, phonegapp, titanium, xamarin(which is shit imo) codename one and many others. With IOS i never considered going for something different than Native since the API just seemed so well designed and far superior to me from an architectural point of view.

Fast forward to 2018(almost 2019) adn Google had talks about flutter for a while and how they make it seem that they are fixing how they want people to design apps.

You see. I firmly believe that tech stacks work in 2 ways:

1 people love a stack so much they start to develop cool ADDITIONS to it(see the awesomeios repo) to expand on the standard libraries

2 people start to FIX a stack because the implementation is broken, lacking in functionality, hard to use by itself: see okhttp, legit all the Square libs, butterknife etc etc etc and etc

From this I can conclude 2 things: people love developing for IOS because the ecosystem is nice and dev friendly, and people like to develop for Android in spite of how Google manages their API. Seriously Android is a great OS and having apps that work awesomely in spite of how hard it is to create applications for said platform just shows a level of love and dedication that is unmatched.

This is why I find it hard, and even mean to call out on one product over the other. Despite the morals behind the 2 leading companies inferred from my post, the develpers are what makes the situation better or worse.

So just fuck it and develop and use for what you want.

Honorific mention to PHP and the php developer community which is a mixture of fixing and adding in spite of the ammount of hatred that such coolness gets from a lot of peeps :P

Oh and I got a couple of mobile contracts in the way, this is why I made this post.

And I still hate developing for Android even though I love Java.

A very long rant.. but I'm looking to share some experiences, maybe a different perspective.. huge changes at the company.

So my company is starting our microservices journey (we have a 359 retail websites at this moment)

First question was: What to build first?

The first thing we had to do was to decide what we wanted to build as our first microservice. We went looking for a microservice that can be used read only, consumers could easily implement without overhauling production software and is isolated from other processes.

We’ve ended up with building a catalog service as our first microservice. That catalog service provides consumers of the microservice information of our catalog and its most essential information about items in the catalog.

By starting with building the catalog service the team could focus on building the microservice without any time pressure. The initial functionalities of the catalog service were being created to replace existing functionality which were working fine.

Because we choose such an isolated functionality we were able to introduce the new catalog service into production step by step. Instead of replacing the search functionality of the webshops using a big-bang approach, we choose A/B split testing to measure our changes and gradually increase the load of the microservice.

Next step: Choosing a datastore

The search engine that was in production when we started this project was making user of Solr. Due to the use of Lucene it was performing very well as a search engine, but from engineering perspective it lacked some functionalities. It came short if you wanted to run it in a cluster environment, configuring it was hard and not user friendly and last but not least, development of Solr seemed to be grinded to a halt.

Elasticsearch started entering the scene as a competitor for Solr and brought interesting features. Still using Lucene, which we were happy with, it was build with clustering in mind and being provided out of the box. Managing Elasticsearch was easy since there are REST APIs for configuration and as a fallback there are YAML configurations available.

We decided to use Elasticsearch since it provides us the strengths and capabilities of Lucene with the added joy of easy configuration, clustering and a lively community driving the project.

Even bigger challenge? Which programming language will we use

The team responsible for developing this first microservice consists out of a group web developers. So when looking for a programming language for the microservice, we went searching for a language close to their hearts and expertise. At that time a typical web developer at least had knowledge of PHP and Javascript.

What we’ve noticed during researching various languages is that almost all actions done by the catalog service will boil down to the following paradigm:

- Execute a HTTP call to fetch some JSON

- Transform JSON to a desired output

- Respond with the transformed JSON

Actions that easily can be done in a parallel and asynchronous manner and mainly consists out of transforming JSON from the source to a desired output. The programming language used for the catalog service should hold strong qualifications for those kind of actions.

Another thing to notice is that some functionalities that will be built using the catalog service will result into a high level of concurrent requests. For example the type-ahead functionality will trigger several requests to the catalog service per usage of a user.

To us, PHP and .NET at that time weren’t sufficient enough to us for building the catalog service based on the requirements we’ve set. Eventually we’ve decided to use Node.js which is better suited for the things we are looking for as described earlier. Node.js provides a non-blocking I/O model and being event driven helps us developing a high performance microservice.

The leap to start programming Node.js is relatively small since it basically is Javascript. A language that is familiar for the developers around that time. While Node.js is displaying some new concepts it is relatively easy for a developer to start using it.

The beauty of microservices and the isolation it provides, is that you can choose the best tool for that particular microservice. Not all microservices will be developed using Node.js and Elasticsearch. All kinds of combinations might arise and this is what makes the microservices architecture so flexible.

Even when Node.js or Elasticsearch turns out to be a bad choice for the catalog service it is relatively easy to switch that choice for magic ‘X’ or component ‘Z’. By focussing on creating a solid API the components that are driving that API don’t matter that much. It should do what you ask of it and when it is lacking you just replace it.

Many more headaches to come later this year ;)

Hi there

Every few months I switch my Linux distro, currently I’m having a look at Manjaro.

I really like it so far, but there’s one thing that sucks freaking donkey balls..

Everything works perfectly until I shutdown.
On shutdown the whole OS freezes.

Although Manjaro is known for its big and new-to-arch friendly community, I didn’t find many posts about this problem and if I did, the questions were not answered.

Any ideas?

Mostly on hackathons and dev related events.

The community can be so friendly. Even I learned some good stuff.

Good people, good times.

Yo, DevRat! Python is basically the rockstar of programming languages. Here's why it's so dope:

1. **Readability Rules**: Python's code is like super neat handwriting; you don't need a decoder ring. Forget those curly braces and semicolons – Python uses indents to keep things tidy.

2. **Zen Vibes**: Python has its own philosophy called "The Zen of Python." It's like Python's personal horoscope, telling you to keep it simple and readable. Can't argue with cosmic coding wisdom, right?

3. **Tools Galore**: Python's got this massive toolbox with tools for everything – web scraping, AI, web development, you name it. It's like a programming Swiss Army knife.

4. **Party with the Community**: Python peeps are like the coolest party crew. Stuck on a problem? Hit up Stack Overflow. Wanna hang out? GitHub's where it's at. PyCon? It's like the Woodstock of coding, man!

5. **All-in-One Language**: Python isn't a one-trick pony. You can code websites, automate stuff, do data science, make games, and even boss around robots. Talk about versatility!

6. **Learn It in Your Sleep**: Python's like that subject in school that's just a breeze. It's beginner-friendly, but it also scales up for the big stuff.

So, DevRat, Python's the way to go – it's like the coolest buddy in the coding world. Time to rock and code! 🚀🐍💻

Last week I finally deleted my Twitter account. DevRant has succeeded where Twitter deeply failed me: in providing good laughs, a friendly community, a less popularity-biased algo, and interesting content. I kept it for promotion just in case I'd ever get around to publishing a blog regularly, but even if I eventually do, I no longer give a **** about Twitter.

Once upon a time in the bustling city of Techville, there lived a talented web developer named Alex. Known for their exceptional coding skills and innovative designs, Alex had a reputation as a brilliant but often solitary worker. Despite their immense talent, they often struggled with social interactions and found it challenging to connect with their colleagues.

One sunny morning, as Alex arrived at the sleek offices of WebWizards Inc., they noticed a new face amidst the sea of familiar coworkers. Her name was Lily, a warm and friendly individual with an infectious smile. Alex couldn't help but be drawn to her positive energy and kind nature.

Over time, as they worked on various projects together, Alex and Lily formed an unexpected bond. Lily's patience and willingness to collaborate made their partnership seamless. She recognized Alex's expertise and valued their creative input, which helped foster a deep sense of mutual respect.

As their professional relationship grew, Alex began to see beyond the surface of the company they worked for. They realized that WebWizards Inc. was more than just a business; it was a family of talented individuals who genuinely cared about one another. The company fostered an inclusive and supportive environment, encouraging personal growth and celebrating achievements.

One day, overwhelmed by gratitude for both Lily and the company they worked for, Alex decided to express their feelings. They sat down and poured their heart out, typing a heartfelt message of appreciation and admiration. Alex couldn't contain their excitement as they hit the "Send" button, eagerly awaiting a response.

To their delight, Lily responded promptly with overwhelming joy and gratitude. She confessed that she had also felt a strong connection with Alex and considered them an invaluable asset to the team. Furthermore, she shared that the supportive culture and caring nature of WebWizards Inc. had made her job more fulfilling and enjoyable.

The two coworkers became closer friends, their collaboration flourishing both in and out of the office. Alex's once-rare smiles became more frequent, and their confidence grew. They no longer felt like an outsider but an integral part of a wonderful community.

Together, Alex and Lily continued to create outstanding web projects, surpassing expectations and leaving their clients amazed. Their passion and dedication were fueled by the genuine camaraderie they shared with their colleagues at WebWizards Inc.

As time passed, Alex realized that their journey as a web developer had been transformed not only by their skills but also by the amazing people they had the privilege to work with. They learned that a kind coworker and a supportive company could make a world of difference, turning an ordinary job into an extraordinary experience.

And so, the tale of Alex, Lily, and the remarkable WebWizards Inc. serves as a reminder that in the vast realm of work, the bonds we form and the culture we foster can be as impactful as the tasks we accomplish.

Today I had the chance to participate as a community member of an ecommerce platform to represent the community and vendor towards developers that are getting in touch with a new product from the vendor. This event was completely covered by the vendor and was awesome in many different ways. Features, tutorials, workshop, presentation, attendees.

Previously I worked on a closed source patent management software and one felt stuck and rigid. The only contact outside were customers. They were sort of the community and friendly as well just without technical knowledge. Events with the customers with a hands on the product was also covered by the vendor and great in their kind.

I am unsure what the reason for the different feeling towards this is. Is it about being a dev at a company that let me participate on a vendor product compared to be the vendor? Is it about the product license? The external people being devs or no-devs? Do you have similar experiences after switching jobs?

They were both friendly so it is not just about people being nice. Both products dont personally affect me as I neither file a patent or trademark myself nor do I own a web shop.

Seriously, Elixir Community is the most friendly group of people I have ever deal with, in reddit or the Elixir Forum. I beginning to love elixir because of the supportive community <3