Remember the Ububtu mobile OS ?

I remember working on the community UI drive for this project. To know that something as awesome as ubuntu would come down into the form factor of a phone , was just ecstatic.

The first build was out , people liked it. People nagged a bit about the performance issues , but it was going fine. Then the second build .. then the third no one heard about and the 4th that never came.

The interface for this system was unique because after Wondows , this is the only other OS developer that embraced the one ecosystem mantra of design.

Using Ubuntu phone was natural , it was a small desktop OS.

I remember logging on to launchpad one day and seeing the Ubuntu mobile channel with it's last post " Thank you and goodbye "

It was heartbreaking , but i could understand. Like windows phone ( which if you guys weren't aware of , had APK support by the end of its lifecycle ) felt crushed under the weight of android and iOS.

Waiting for a day when there will be a third champion in game. I miss having to see Ubuntu being on my phone , but they seem to be doing great in everything else , so good on that. 😄

Ok done .. thanks

Mantra of the day : "Three weeks of coding can save three hours of planning."

I actually like Microsoft these days. Despite developing on Mac machines, we use VSTS for code repo, build/release pipelines and work item tracking, and Azure for all things cloud. It all works incredibly well together and at low cost.

Microsoft has changed ethos massively in the last few years. In my opinion, the classic dev mantra of “Microsoft is shit and evil, Linux is flawless” is outdated and getting kind of boring.

I love to work in pubs/bars, this special kind of noisy environment works so well for me. I even go "into the zone".

Lets talk about this. Is anyone else the same? Just curious.

These are my 6 reasons:

0) Beer. 🍺
1) None of the activity in a bar actually interests to me, if you know what I mean. In my house, every single noise/movement will get my attention.
2) After some time all the noise blends into a kind of "homogeneous hearing blurb". Like a mantra. Maybe there are even white/pink/brown noise benefits (guess).
3) I go to places where I enjoy the music and atmosphere.
4) I like bars and pubs anyways. I feel good in these places.
5) Beer. 🍺

! exactly dev

I'd ditched Windows and spent a while exploring the Linux ecosystem for content creation. And I have to say, it was not a nice experience.

As much as I respect the Linux mantra of "free as in freedom" and "you need to roll up your sleeves and figure out stuff on your own", it just isn't good enough for non-dev work. Sorry guys, but I need software that gets out of my way and at least does what it's supposed to do. I can't stand a horrible UI or delays and random crashes, which is exactly what happens with most things under Linux.

To replace my Windows workflow I used the following:
1. Windows -> elementaryOS (because Debian/Ubuntu repositories seem to have the best software support, and elementaryOS is the least horrible looking thing that supports that) and then Arch, because, well, Arch.
2. Blender + Maya -> Blender + Maya on Linux.
3. Reaper + FL Studio -> Ardour + LMMS.
4. Photoshop -> GIMP + Krita + Inkscape.
5. ZBrush -> nothing :(

As you can see, my use cases are pretty much all over the spectrum.

Firstly, installing and configuring stuff. A pleasure on Windows, an absolute pain on Linux. Everything just worked on Windows, I had to wrestle with library versions and patches and unstable audio layers (Linux audio just sucks, except for JACK) on Linux.

Out of these, Blender and Maya were the best experience. But even then, both would suffer from random crashes that just didn't happen on Windows.
Ardour is actually really nice when it works. Its use of JACK for routing makes it really really flexible, but it just isn't stable enough to depend on. LMMS is utter crap. I'm sorry, but I just hate the UI. Can't stand it.
GIMP, Krita, and Inkscape can't beat Photoshop, even when you consider them together. Adobe software workflow is just so much better and more intuitive.
Blender 3D sculpting is not bad, but it's nowhere as good as ZBrush.

Also, if you're a C++ dev like me, nothing beats Visual Studio 2017. Nothing. That IDE just blows everything else out of the water. Even VSCode. And it's not slow at all, it handled a fairly large project (PBRTv3) just fine on my Windows development VM. Yes, a VM.

So...I ditched Linux and went back to Windows, but I keep Linux as a VM for when I actually want to mess with Blender or Ardour. Or some dev stuff which Windows sucks at (which is becoming less frequent because of WSL).

Out of all the above, the only one I'd consider ready for production use would be Blender. Developers of open source software, please learn from Blender. Kickass UI and user friendly operation is extremely important, you can't make a random window with GTK buttons and text boxes and arcane config files and expect people to use it for serious work.

Also, Windows beats Linux hands down as an everyday OS. It's always been rock solid, if you take care of it properly (and that goes for any OS). Updates hardly take any time because I run it on a SSD. As for all the advertising and marketing bullshit, you can block a large amount of stuff. And for what can't be blocked, well, I just have to live with it, because the alternative is compromising on my creative output, which is too much for me.

I still run Linux on my server, though. And on my embedded devices (Pi, BeagleBone, etc.). It absolutely rocks there.

I realize that Linux software is not going to improve unless we do something about it, so I'll be contributing fixes and code (the joys of being a C++ dev, yay). Still, I feel that the platform and software as a whole is just not mature enough.

My mantra while browsing devRant:

I will downvote and walk away. I will not take the bait.
I will downvote and walk away. I will not take the bait.
I will downvote and walk away. I will not take the bait.
I will downvote and walk away. I will not take the bait.

*exhales*

My programming mantra:

The problem is between keyboard and the chair.

I am currently doing my first ever internship. It is a medium-ish sized IT company and I basically do stuff in networking and software development. I sit on my chair, wheel it back and forth the small space behind my desk for like and hour. Then I go to the cafeteria, eat whatever is there (it’s absolutely free? Hopefully). There is a pool table which is always occupied. Then I sit in the lab and configure routers till 8 in the night. Boring.
I am developing a management system side by side so I break my head over server side routes (seriously, they are confusing) over the night.
So coffee is my mantra and boring is my life.

lately my IT mantra in the vein of "have you tried turning it off and back on again" has become "did you check the logs for error output"😡

NOTE to all developers of any level: if you want help do your due diligence! Check the logs, try to step debug and at the very least please at least pretend to perform a cursory search

Program failed to load with an error message.
Tried resolving, failed.
Searched the internet, Stack overflow failed.
Tried 4-5 solutions, failed.
Disappointments!

Tired of my life, restarted the PC. Program opened perfectly and worked smoothly.

Programmer's mantra:
Everything is fine at the end because "restart" is the real magic!

Day 1 of a new semester in college. Our 50 yr old H.O.D is a guest lecturer of this new subject called "Industrial Management" (why its included in the syllabus of CSE degree i wonder) . As there were only 6 students , the guy went on like a drunkard telling life lessons :

1) only 20% of the people in a company are only working. Rest 80% of them are just using sugar coated words at the right place ; doing politics and taking credits of the others .

2) those 80% getting benefits are usually the bosses (and in his example, the senior deans and H.O.Ds buttering the administrative dept and director ) and the hardworking 20% are the Juniors or the new joiners ( and in his example, the latest recruited ,honest teachers. Makes sense why we have shitty teachers :/ ). They altogether make sucesses to the company(although its just those 20%hardworkers doing the actual job) . But at the time of salary everybody gets the benfit.

3) Its always perfect to throw blames at senior or junior. (explaining how a parent complaining about the poor study environment to director is made to think that it's only the fault of his own child. blames going from director to dean to HOD to teachers to your own child's mistakes.)

4) Being your boss's favourite is super important. He gave example as : 2 teachers meets him with 100% results and 100% reviews. One of them is a known asshole with 0 knowledge, who makes jokes and sexist comments during the class, gives free attendence and question papers before the exam{therefore 100%reviews} . But he is dean's great ass-licker . The other one is honest hard-working teacher with real reviews and results. So he says he shows their combine results to the director along with his own buttering and ass licking, gets a hike himself and permit to give hije to one junior teacher. And who would it give hike to? The ass licking asshole, because that's how it works. What about the honest teacher?what reply would he get? Simply, appreciations and sugar coated words : "thank you for working so hard. But you did not do anything new. You were only hired to DO hardwork and give good results"

( and i was like fuck? Like seriously? Because that is something resonating with what i once heard in my internship :"yeah you are developing nice and all good, but that's what you are expected to do. You were only hired to achieve results, and you did nothing new". So that's what we are missing? Ass licking?-_- )

5) He believed its important to "look working" than being "actually working" . Quoting an example from his days as a dev, he told a story about how he once worked on a project with deadline of 1 month . He was young and worked hard and in 2 days completed the complete project and accidentally reported success to boss instead of his seniors. The boss simply congratulated his team(seniors and him) and assigned them another project. Later that day , he got an ass-wipe scolding from his seniors that if he had kept his mouth shut, they would have simply watched movies and relax for next 15 days, and submit the project during the salary time to gain bonus attention.
He even gave his short mantra or principle for such situation "kaam ki fickar kar, fickar ka zickar kar, par kaam mat kar " (get worried and tensed about the work. Display your tention and worries to the world (esp bosses) . But don't work.)

And there were many other short stories like that.

Mann, i was about to shout " you corrupt asshole ", but one thing He just told us about the importance of being in boss's good books made me stop ( nd he is a fucking HOD, senior to teachers)

But hell he told some relatable truths. Make me sad about the job life.

Bloody Office politics :|

!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.

I Google
I stack overflow
I am an index that references
The internet memory

The modern day code-er mantra

So, I've had a personal project going for a couple of years now. It's one of those "I think this could be the billion-dollar idea" things. But I suffer from the typical "it's not PERFECT, so let's start again!" mentality, and the "hmm, I'm not sure I like that technology choice, so let's start again!" mentality.

Or, at least, I DID until 3-4 months ago.

I made the decision that I was going to charge ahead with it even if I started having second thoughts along the way. But, at the same time, I made the decision that I was going to rely on as little external technology as possible. Simplicity was going to be the key guiding light and if I couldn't truly justify bringing a given technology into the mix, it'd stay out.

That means that when I built the front end, I would go with plain HTML/CSS/JS... you know, just like I did 20+ years ago... and when I built the back end, I'd minimize the libraries I used as much as possible (though I allowed myself a bit more flexibility on the back end because that seems to be where there's less issues generally). Similarly, any choice I made I wanted to have little to no additional tooling required.

So, given this is a webapp with a Node back-end, I had some decisions to make.

On the back end, I decided to go with Express. Previously, I had written all the server code myself from "first principles", so I effectively built my own version of Express in other words. And you know what? It worked fine! It wasn't particularly hard, the code wasn't especially bad, and it worked. So, I considered re-using that code from the previous iteration, but I ultimately decided that Express brings enough value - more specifically all the middleware available for it - to justify going with it. I also stuck with NeDB for my data storage needs since that was aces all along (though I did switch to nedb-promises instead of writing my own async/await wrapper around it as I had previously done).

What I DIDN'T do though is go with TypeScript. In previous versions, I had. And, hey, it worked fine. TS of course brings some value, but having to have a compile step in it goes against my "as little additional tooling as possible" mantra, and the value it brings I find to be dubious when there's just one developer. As it stands, my "tooling" amounts to a few very simple JS scripts run with NPM. It's very simple, and that was my big goal: simplicity.

On the front end, I of course had to choose a framework first. React is fine, Angular is horrid, Vue, Svelte, others are okay. But I didn't want to bother with any of that because I dislike the level of abstraction they bring. But I also didn't want to be building my own widget library. I've done that before and it takes a lot of time and effort to do it well. So, after looking at many different options, I settled on Webix. I'm a fan of that library because it has a JS-centric approach. There's no JSX-like intermediate format, no build step involved, it's just straight, simple JS, and it's powerful and looks pretty good. Perfect for my needs. For one specific capability I did allow myself to bring in AnimeJS and ThreeJS. That's it though, no other dependencies (well, at first, I was using Axios because it was comfortable, but I've since migrated to plain old fetch). And no Webpack, no bundling at all, in fact. I dynamically load resources, which effectively is code-splitting, and I have some NPM scripts to do minification for a production build, but otherwise the code that runs in the browser is what I actually wrote, unlike using a framework.

So, what's the point of this whole rant?

The point is that I've made more progress in these last few months than I did the previous several years, and the experience has been SO much better!

All the tools and dependencies we tend to use these days, by and large, I think get in the way. Oh, to be sure, they have their own benefits, I'm not denying that... but I'm not at all convinced those benefits outweighs the time lost configuring this tool or that, fixing breakages caused by dependency updates, dealing with obtuse errors spit out by code I didn't write, going from the code in the browser to the actual source code to get anywhere when debugging, parsing crappy documentation, and just generally having the project be so much more complex and difficult to reason about. It's cognitive overload.

I've been doing this professionaly for a LONG time, I've seen so many fads come and go. The one thing I think we've lost along the way is the idea that simplicity leads to the best outcomes, and simplicity doesn't automatically mean you write less code, doesn't mean you cede responsibility for various things to third parties. Those things aren't automatically bad, but they CAN be, and I think more than we realize. We get wrapped up in "what everyone else is doing", we don't stop to question the "best practices", we just blindly follow.

I'm done with that, and my project is better for it!

(Not a rant)
Mantra for a good life : Stage the good bits, .gitignore the bad ones. Commit and push to Memory !

Peace ☮️

Our approach is to get a loose feel for what the client wants, lift some visuals from Theme Forest then spend the next few weeks persuading the client to use our crappy server rather than their preferred AWS solution. Then once the project is behind schedule we break the work down into disparate tasks each of which gets a single line brief from the PM (such as 'create admin' or 'do css'). These then get assigned to different devs with no consideration of their skillset. The PM is available for 10 mins every day to answer queries, the rest of the time our devs are expected to work autonomously. Meanwhile we'll tell the client that we're back on schedule and arrange a demo for an impossibly short deadline. We have the mantra ”dont worry about it” which the PM uses to quash any dev's concerns up until the day before the deadline at which point we'll swap some devs on to unrelated work whilst others concentrate on getting "just the pages the client wants to see looking right" (we have a policy of making it look like it works before it actually does.) Following the demo we will announce all the missing features we had forgotten about from the initial undocumented agreement and set the project aside whilst we service another client.

My soul cringes a bit every time some smart ass decides to put "Smart" before the product name.
As though nothing means smart as much as digging your own hole.

More broadly, the whole whole world is buying into this "smart" mantra. As if anything and everything that existed before was not smart. Basically "I'm the best" attitude. Don't forget that you can see far only because you're standing on the shoulders of giants.

Case in point:
1. Smart phone which is smart enough to start causing trouble after a couple of years.
2. Smart watch
3. Smart car
4. Smart planes
5. Smart home
.
.
Fucking non sense

Wk88 i basically see "I'm a beta that belittles myself, because everybody else seems to be so much better than me.."

While I certainly know how it feels, that mantra & mindset will lead to void or null.

It's a self-fulfilling prophecy and life's a bitch that'll keep ya down if you let it.

It's gonna be rough, but ye gotta stop calling yourself inadequate and start working on honing your skills.

No great feat happens over night, it takes practice and dedication.

When I’m getting to 100k MRR, if I have any developers but me, I’m gonna spoil them. I mean making them obscenely spoiled. Here, take your 4 times the market salary. Enjoy the culture and never leave.

Why? Because my architecture approach makes products that don’t need many devs, plus I don’t like making useless features. Every product has a scope. Every scope can be completed. “There are always tasks” notion is wrong.

Also, because to me 1000% and 10000% margins aren’t different at all. Those who seek MOAR and MOAR money, amassing more money than they can ever spend, do it out of fear.
I don’t have any kind of fear. Those who looked their death straight in the eyes don’t fear materialistic misfortunes.

My favorite word is “enough”. I speak it to myself several times a day, over and over, like a mantra. It helps me overcome but-what-ifs that plague people to the point of using next.js just to make trivial saas apps that can be replaced by Excel in one week of work.

I get so irritated when i see people pirate things, i get it, they want it yeah but the fact that someone gets pissed off because i use opensource software, try collaborate and better the software and support by donating some projects. Then they try and convert me to their "copy and paste" mantra. Fuck no.

If only they knew the hours and time given up from their lives, taken away from famillies and social lives developers spend trying to make apps that alfeady makes everyones lives simpler but they dont see that, they are so use to having things given to them they wont realise hoe important it is until it was taken away.

Support the developers because if it was the other way around. Regardless if you wanted it or not, you would like support. We do do this because we love it and with everyones help, we can progress forward together.

I really dont care that i look like as ass to the guy now, i really dont care what takes from it but just venting i guess..

I'm so fucking done with this shit. If someone forgets every git command every single fucking tim le is ok to ask. Every time someone asks advice on how to write a fucking retarded workaround (out of lazyness, because fixing their own code is too much to ask), it'a ok.
The *ONE* fucking time i ask the name of the fucking function to generate a filter via code using their fucking cms? "you should do that via gui!" "who cares if there'll be conficts with git, just manually redo everything in production!".
God fucking dammit how can you even have the balls to complain about terrible planning and stuff not working if that's your fucking mantra?!

I have a mantra: don't get too attached to the shit you build

That mantra is about to be thoroughly tested - we might be just about to trash one year worth of work coz the 3rd party we were working with doesn't look like they'll be able handle our load

Working for early-stage startup is like living with alcoholic father. Fuck lean startup mantra! Fuck any kind of bullshit about agility and business sustainability.

Doesn't Python kind of contradict its own mantra. When they write explicit is better than implicit but at the same time they provide collection literals?

Dev Mantra

I do not write code with my keyboard. He who writes code with his keyboard has forgotten the days of the punch cards. I write code with mind.

I do not write non descriptive variables. He who writes non descriptive variables has forgotten the days of the punch cards. I write self descriptive code.

I do not debug by brute force. He who debugs by brute force has forgotten has forgotten the days of the punch cards. I debug with breakpoints and stack traces.

Our generation has accepted that time management isn't cool. Doing things at whim and as you like is cooler and accepted to be non-monotonous.

Though haven't cracked the mantra behind proper time management, I am of the opinion that those who manage a fixed skeletal time management live a way more cooler life than others. 😅

P.S.: Time management hasn't nothing to do with being geeky or not going to parties. FYI. Time utilisation is an entirely different concept. 😉

"Delete all code!" That should be the mantra!

Was watching some stuff from destroyallsoftware.com. Not entirely convinced. So I should cook up my own shit.

So here is how the argument goes:
There's quite some negativity in the term "legacy" software. Partly it may be the envy to software that runs on actual machines and is not that phantasm, that perfect first lines on a greenfield project until it gets messed up as it has to put up with all the real world messiness. But the negativity it deserves is actually for the code that we cannot get rid of. This ugly class or function that soaked all the complexity and functionality so it defies any positive change. And always when it appears on your screen, it irks you, enrages you, makes you punch the screen, because you can almost feel the distaste physically. - *That* is the definition of "legacy" in its true negativity. No software should be like that. On the contrary. Every line should be replaceable, dispensable, disposable. At the verge to deletable. Because you know: the best code is no code.

This is where my hatred of code could get productive: Delete all the wretched, loathsome stuff and replace it, with something that just sucks less and can be thrown away any time. Don't expect beauty or perfect design. It'll never finish.

The mantra for success, "Better an OOPS, than a WHAT IF !"

Context:
At work, I code primarily with Java.

I'm a big believer in the mantra, "if it ain't broke, don't fix it", but I find myself conflicted with that when I can see how much of an improvement it would be to use a different language for some of the simple pieces in our integration.

Question:
When should one start considering other languages for your team? And if you choose other options, how do you do it in such a way where you don't end up building a chimera of an integration?

More like a confession.

Had a task that involved invalidating a string if it contained more than five digits (anywhere in the string.)

"No problem", I thought. That sounds like a simple regex!

^(\D*\d?\D*){5}$

Turns out catastrophic backtracking had other ideas, and I revert to my usual "atomic grouping fudge that will hopefully work without me really understanding what's going on" of:

^(?>\D*\d?\D*){5}$

...anyone else shamefully follow this mantra, or am I the only one that hasn't skilled up properly on regexes...

1) I like to break through complex systems to understand them on a fundamental level
2) I live by the mantra of "If you're going to do something, do it right"
3) I'm a stickler for detail and strive for simplicity and organization

These three descriptions of my personality describe why I love to code: there's nothing more satisfying than taking a jumbled, wrong ugly mess of software and turn it into something beautiful and simple that anyone can effectively use. Makes all the hardship worth it IMO

Success Mantra -

Leave your home . ASAP

Theacher said "write 100 times :"I'll not write bad code and also I'll use TDD "... but she specify how "

As a Computer Science student, I've come to the conclusion, most issues can be fixed by simply switching off and on again.
This is a mantra I use in my daily personal life now.

Our mantra this week

Mantra for any development work should be-

" It should be intuitive, pre-cognitive ! "

I guess the whole "can work from anywhere!" mantra doesn't apply to those looking at junior positions. I wonder how the industry will handle the lack of new hires coming through as more and more seniors demand WFH accommodations.