Got this from a recruiter:

We are looking for a **Senior Android Developer/Lead** at Philadelphia PA

Hiring Mode: Contract

Must have skills:

· 10-12 years mobile experience in developing Android applications
· Solid understanding of Android SDK on frameworks such as: UIKit, CoreData, CoreFoundation, Network Programming, etc.
· Good Knowledge on REST Ful API and JSON Parsing
· Good knowledge on multi-threaded environment and grand central dispatch
· Advanced object-oriented programming and knowledge of design patterns
· Ability to write clean, well-documented, object-oriented code
· Ability to work independently
· Experience with Agile Driven Development
· Up to date with the latest mobile technology and development trends
· Passion for software development- embracing every challenge with a drive to solve it
· Engaging communication skills

My response:

I am terribly sorry but I am completely not interested in working for anyone who might think that this is a job description for an Android engineer.

1. Android was released in September 2008 so finding anyone with 10 years experience now would have to be a Google engineer.
2. UIKit, CoreData, CoreFoundation are all iOS frameworks
3. Grand Central Dispatch is an iOS mechanism for multithreading and is not in Android
4. There are JSON parsing frameworks, no one does that by hand anymore

Please delete me from your emailing list.

A: So are you the programmers of this software?

B: Yeah, I did the front end

A: Oh it looks so fantastic! It is simple, yet beautiful and responsive. Truly great design, you are so talented!

C: I did the back end...

A: Oh, you mean the server stuff?

C: Yeah

A: Niceeee

Looks good to me!

Guide to Software Design...

The problem with being a programmer...

I just broke up with a girl I've been seeing the past 2 months, that I was really into.

But in the end, it became a question of, either i'm with her, or I'm with my work.

I don't think that would happen with other professions, at least, not as easily.

I think, with other professions or projects, you tell someone "I need to work" and it's really fucking understood. "Ok, you need to work"

They understand it. If I was a lawyer.. I have a case. if I was a carpenter, I have a wall to build,
or a house. Etc. All understood things. Or physical things that can be seen.

But with programming, first of all, I work my own hours, I write software and then sell it. I do it all myself, I own my own business. I don't have normal hours like a job, but I do know my requirements, which is at LEAST 8 hours a day of solid, uninterrupted work.

If I had a "job" it would be like "gotta go to work" and that would be it.

But, because I work for myself, and because the things I build, aren't like something you physically see, nobody gets it.

My parents, as supportive as they are, will never understand how I just implemented a new design pattern and like, leveled up because of it.

They see software... buttons, and even then, when I try to explain what excites me, it's like trying to get a 3 year old interested in calculus.

How could they possibly understand the richness of what I do, how fulfilling it is
and how much I love it, when all they see
is me on a computer, clicking keys.

The same for this girl I dated.

The only place I feel where people understand,
is here.

Do you have any similar experiences to share?
Would love to hear it right now.

I am an indie game developer and I lead a team of 5 trusted individuals. After our latest release, we bought a larger office and decided to expand our team so that we could implement more features in our games and release it in a desirable time period. So I asked everyone to look for individuals that they would like to hire for their respective departments. When the whole list was prepared, I sent out a bunch of job offers for a "training trial period". The idea was that everyone would teach the newbies in their department about how we do stuff and then after a month select those who seem to be the best. Our original team was
-Two coders
-One sound guy(because musician is too mainstream)
-Two artists
I did coding, concept art(and character drawings) and story design, So, I decided to be a "coding mentor"(?).
We planned to recruit
-Two coders
-One sound guy
-One artist (two if we encountered a great artstyle)
When the day finally arrived I decided to hide the fact that I am the founder and decided that there would be a phantom boss so that they wouldn't get stressed or try flattery.
So out of 7, 5 people people came for the "coding trial session". There were 3 guys and 2 girls. My teammate and I started by giving them a brief introduction to the working of our engine and then gave them a few exercises to help them understand it better. Fast forward a few days, and we were teaching them about how we implement multiple languages in our games using Excel. The original text in English is written in the first column and we then send it to translators so that they can easily compare and translate the content side by side such that a column is reserved for each language. We then break it down and convert the whole thing into an engine friendly CSV kind of format. When we concluded, we asked them if they had any questions. So there was this smartass, who could not get over the fact that we were using Excel. The conversation went like this:(almost word to word)

Smartass: "Why would you even use that primitive software? How stupid is that? Why don't you get some skills before teaching us about your shit logic?"
Me:*triggered* "Oh yeah? Well that's how we do stuff here. If you don't like it, you can simply leave."
Smartass: "You don't know who I am, do you? I am friends with the boss of this company. If I wanted I could have all of you fired at whim."
Me:"Oh, is that right?"
Smartass:"Damn right it is. Now that you know who I am, you better treat me with some respect."
Me: "What if I told you that I am not just a coder?"
Smartass:"Considering your lack of skills, I assume that you are also a janitor? What was he thinking? Hiring people like you, he must have been desperate."
Me:"What if I told you that I am the boss?"
Smartass:"Hah! You wish you were."*looks towards my teammate while pointing a thumb at me* "Calling himself the boss, who does he think he is?"
Teammate:*looks away*.
Smartass:*glances back and forth between me and my teammate while looking confused* *realizes* *starts sweating profusely* *looks at me with horror*
Me:"Ha ha ha hah, get out"
Smartass:*stands dumbfounded*
Me:"I said, get out"
Smartass:*gathers his stuff and leaves the room*
Me: "Alright, any questions?"*Smiling angrily*
Newcomers: *shake heads furiously*
Me:"Good"

For the rest of the day nobody tried to bother me. I decided to stop posing as an employee and teaching the newcomers so that I could secretly observe all sessions that took place from now on for events like these. That guy never came back. The good news however, is that the art and music training was going pretty well.

What really intrigues me though is that why do I keep getting caught with these annoying people? It's like I am working in customer support or something.

My CEO: "So! You are the new guy we hired to design and manage the implementation of our new state of the art super-duper fancy ERP solution with badass Business Intelligence systems to grow our company which already spans over several localities across the county, that has to live for at least the next 12-15 years?

Please remember that the Windows Server in the rack in the basement needs replacement soon, and that our new fancy solution must not in any way utilize cloud-technology or SaSS! I don't like that! I think it's a scam! We store everything on premises, own our infrastructure and we buy our software...Because I think that is best!"

Me: "So... let me get this straight: You want me to build you a one-off, concept sports car that can outperform a Lamborghini using only plywood, duct-tape and a donkey cart?"

He walked off... I may need a new job next week!

So lot of people ask me here what is Testing?

Well, I have decided to post about it instead of answering every request individually as it is tiresome. So here we go...

- Why to test?
Testing is breaking down a piece of code so that all the possible logical and functional errors can be detected while in development phase, so that the disaster can be prevented in production.

- How to test a piece of code/software?
There are various types of testing like unit, sanity/smoke, functional, regression, performance, security, penetration to name a few. Each has it's own significance and to know more you can Google/DDG them.

- What to test?
We can test any and everything. You can test code, UI, UX, speed of application, database flow, logical flow, functional flow, et cetera.

Testing is an attitude, not a skill. Cannot be taught but only developed by one ownself.

To be good at testing, one needs to have a good design and business sense, apart from technical and functional knowledge.

Many will say, to test one needs to think outside the box. Fuck that. There is no box. Everything is a sandbox and do whatever the fuck you want to, to break things.

Most importantly, thinking from other person's perspective is critical as this helps you think what can an user do with your software. Trust me, humans are idiots and can literally fuck your software doggy style and make you wonder why your code isn't working?

To build an idiot proof software, we need to think beyond human levels.

Never think the obvious. NEVER.

Always try what you think can never happen. System will break, I promise.

Finding loopholes is way easier than you think. Fixing them is surely a challenge.

Moreover, to survive in corporate world leaning the processes is important. The SDLC cycle is what makes a software great.

And today I realised that no role is stupid. Testing is looked down upon in my country. Possibly, IT is the only field where testing has least value as compared to other places like food testing or automobile crash testing et cetera.

And I, myself used to think support is a stupid job requiring no skills. But today I talked to a friend in support and realised that they have more technical skills than a tester.

Everyone is important and we shouldn't look down upon any person or role. Nobody is superior, nobody is inferior. We all are equal.

Together we shall work as a team and a great teamwork can achieve wonders.

Hope this helps. Thak you for reading and do provide your feedback as it shall help me improve.

P.S.: last week somebody tagged me to a new comer's post seeking advice for testing. I don't recollect that so please tag them here again. Thanks.

Edit: I feel like and I might have, missed out some points so please excuse me for that.

Many, many years ago, Apple had this software you could install which allowed you to take full control of someone else's machine. Well, my mate who was a designer worked in a different office downstairs. I was often in their fixing stupid shit problems. While he was out on lunch, i installed and configured the software on his mac. After lunch I went back upstairs and watched his every move on my mac. He was in adobe inDesign creating some design for a brochure. He was in a text box changing the heading, i seized the opportunity and took control typing in the text box "i am a useless cunt", pissing myself, I then selected the text and increased the size and made it bold... then the phone rang.

Just interviewed a guy with ~8 years of experience:
Me: *Asked him to write a simple algo logic on a paper*

Him: I don't do much of algo design. I'm much of a design patterns and software design guy.

Me: How would you design a singleton class in Java?

Him: *writes a sloppy code*

Me: Hey, thanks for your time. Our HR will get back to you with further updates.

Moral: Interviews can be very short when the candidate doesn't code.

We're using a ticket system at work that a local company wrote specifically for IT-support companies. It's missing so many (to us) essential features that they flat out ignored the feature requests for. I started dissecting their front-end code to find ways to get the site to do what we want and find a lot of ugly code.
Stuff like if(!confirm("blablabla") == false) and whole JavaScript libraries just to perform one task in one page that are loaded on every page you visit, complaining in the js console that they are loaded in the wrong order. It also uses a websocket on a completely arbitrary port making it impossible to work with it if you are on a restricted wifi. They flat out lie about their customers not wanting an offline app even though their communications platform on which they got asked this question once again got swarmed with big customers disagreeing as the mobile perofrmance and design of the mobile webpage is just atrocious.

So i dig farther and farthee adding all the features we want into a userscript with a beat little 'custom namespace' i make pretty good progress until i find a site that does asynchronous loading of its subpages all of a sudden. They never do that anywhere else. Injecting code into the overcomolicated jQuery mess that they call code is impossible to me, so i track changes via a mutationObserver (awesome stuff for userscripts, never heard of it before) and get that running too.

The userscript got such a volume of functions in such a short time that my boss even used it to demonstrate to them what we want and asked them why they couldn't do it in a reasonable timeframe.

All in all I'm pretty proud if the script, but i hate that software companies that write such a mess of code in different coding styles all over the place even get a foot into the door.

And that's just the code part: They very veeeery often just break stuff in updates that then require multiple hotfixes throughout the day after we complain about it. These errors even go so far to break functionality completely or just throw 500s in our face. It really gives you the impression that they are not testing that thing at all.

And the worst: They actively encourage their trainees to write as much code as possible to get paid more than their contract says, so of course they just break stuff all the time to write as much as possible.
Where did i get that information you ask? They state it on ther fucking career page!

We also have reverse proxy in front of that page that manages the HTTPS encryption and Let's Encrypt renewal. Guess what: They internally check if the certificate on the machine is valid and the system refuses to work if it isn't. How do you upload a certificate to the system you asked? You don't! You have to mail it to them for them to SSH into the system and install it manually. When will that be possible you ask? SOON™.
At least after a while i got them to just disable the 'feature'.

While we are at 'features' (sorry for the bad structure): They have this genius 'smart redirect' feature that is supposed to throw you right back where you were once you're done editing something. Brilliant idea, how do they do it? Using a callback libk like everyone else? Noooo. A serverside database entry that only gets correctly updated half of the time. So while multitasking in multiple tabs because the performance of that thing almost forces you to makes it a whole lot worse you are not protected from it if you don't. Example: you did work on ticket A and save that. You get redirected to ticket B you worked on this morning even though its fucking 5 o' clock in the evening. So of course you get confused over wherever you selected the right ticket to begin with. So you have to check that almost everytime.

Alright, rant over.
Let's see if i beed to make another one after their big 'all feature requests on hold, UI redesign, everything will be fixed and much better'-update.

For people who think/find that open source solutions are always better than commercial/paid/proprietary ones, you are not going to like this rant.

I'm starting to get really fucking fed up with people always, whenever I see someone (including myself) mentioning that an open source solution which is an alternative to a closed source one, saying that it's shit.
I've had countless encounters on here (also irl) where someone mentions that an open source solution (GIMP or Libre Office for example) is shit by default while they've maybe (or probably?) not even used it themselves.
Also people going "you can't even compare those two as for what they can do/features/functions". I'm definitely not saying that those open solutions are perfect. But to call them worthless or shit and/or to say that you literally 'cannot compare them' or that the open solution just doesn't work as a *FACT* is fucking bullshit.

Let's take GIMP for example, the use case of a friend of mine:

- He works both with macOS and Linux Mint, he *needs* a design/photo editing tool which is cross platform. (or at least one which works on macOS+Linux)
- He does not mind paying for software but he prefers to use software which is free as in freedom because he also likes to tinker with the software (a lot of people find this argument bullshit, I noticed on here. Why is that? It's a valid reason. Maybe not for you but we're not talking about you right now).
- He likes Photoshop but due to Linux incompatibility and the fact that he can't tinker around with the code, it's not an option for him.
- He'd gladly go for paid software but GIMP fills all his design/photo editing needs (also the more advanced ones but don't ask them to me because I have no fucking clue how that shit works)
- GIMP *just works* for him, he never has trouble with it.

Let's take Libre Office, my own use case:

- It *NEEDS* to work on Linux, which Libre does.
- It *HAS* to be open source, ethic/moral thingy; Libre Office is open source.
- It doesn't need to work complete magic but it needs proper basic document and 'excel' sheet functionalities which is the case with Libre and it works *for me*.
- I don't mind paying for it, will probably donate in the future (seeding the macOS+windows+linux versions fulltime at the moment)

See, for our use cases, it works very well. So why go into "it's no match for proprietary alternatives" mode right away? It actually is, as you see in the examples above.

Please stop saying that those solutions *don't work* or *are shit* because they do work and are useful for me and loads of people around the world.
Do they have *ALL* the features which their proprietary alternatives have? Maybe, maybe not, maybe they're missing some and maybe they even have some features which the proprietary alternatives don't have, I haven't checked out every feature.

I'm not saying that it works for you, for the record, I'm just saying that just because for you it is a fact that they're bad/shit/hardly working, doesn't mean they are for others.

After our Head Of Software has terminated.

I started to take control over our development crew. And in this year I did more then the old head in the last 6 years.
- Swapped from plain old SVN to Gitlab.
- Build a complete autonomous deployment with Gitlab.
- Introduced code reviews.
- Started to refactor the legacy product with 500.000 lines of code...
- learned how to use confluent apache kafka and kubernetes to split the legacy project in many small and maintainable one.(not done yet)
- Last 3 weeks I learned how to use elasticstack with kibana and co. That we aren't blind anymore. Big dashboards are now shown in the middle of the room :) and maybe convinced my coworker that we use unity3d for our business application cause of support for all devices and same design on them. And offline capabilities. (Don't know if this was my best idea)
When I look back, I'm proud to did that much in one year alone. And my coworkers are happy too that they have less work with deployments and everything.
But I can't decide what's the title for this. System or Software Architect cause I litterallity did both :/

TL:DR Software company is shit

So. Our company hired a software company to build us an online app. A garment designer shop type thing.

2 years later, their lead devs quit and we have to take it as it is... not finished, but they said “it’s perfectly usable, there’s just some angular bugs and UI fixes to do”.

Ok so no problem, fixed the bugs and sorted the UI out, we launched the app. All seems fine for a week or so, then the Project Manager tells me that a certain feature isn’t work as expected, I said no problem, I’ll look into it.

After 3 hours, I stumble across the biggest , most ridiculous thing in the world, something so big, that I was forced to Docker-down the backend immediately without approval.

PM comes screaming into my office literally 3 mins later whilst I’m just triple checking my findings before reporting it.

Basically the app is an Angular front end with a Laravel backend.

So the site has Users, which belong to a team, which can create campaigns, which have products. So you design a teeshirt, give it a url, set your own price and do your own selling blah blah...

The problem is, when anyone visits the site, and adds your product to their basket, in your console, you’re returned all the product JSOn, which isn’t a bad thing, except you’re also given the Campaign that this product belongs too, and the team it belongs to, and its users of that team (email address, address, phone) and any orders for that campaign, with customer data like name address, Stripe ID, last 4 digits of credit card.

Literally every bit of personal information in an unguarded endpoint to be publicly visible even if you went to site.com/api/campaigns

You got all that info, echoed out as JSON on your webpage.... no JWT needed, No authentication.

When I quizzed the company that built it, they were like, “yeah so, we don’t really care anymore, we lost interest in the project”.

What a bunch of cunts...

GUI user: "How can you work from such a basic text interface like that terminal?"
Me: "How can you work with all those stupid buttons that more often than not can't do jack shit?"

Being a Powerline user, I do think that design matters a lot. But so does usability (I don't want my programs to take half a minute to load their bloated UI's) and the ability to use every feature that this or that piece of software has in its command line arguments but not necessarily as a GUI option.

To all the design pattern nazis..

Don't you ever tell me that something is impossible because it violates some design pattern! Those design principles are there to make your life easier, not something you have to obey by law.
Don't get me wrong, you should where ever possible respect those best practices, because it keeps your software maintainable.
But your software should foremost solve real world problems and real world problems can be far more complex than any design pattern could address. So there are cases where you can consciously decide to disregard a best practice in order to provide value to the world.

Thanks for reading if you got this far.

1. Submit my resume, get an email asking to schedule an interview
2. Schedule the interview
3. One day before the scheduled time, I get an email saying that the interview is being rescheduled to another time two days later (no explanation for why they did this)
4. I clear out my schedule and wait for the interview call (it’s suppose to be at 2:30, but I wait like 15 minutes early because I don’t want to miss it)
5. I don’t get a call
6. At 3:00, I call the company and ask whats going on. They apologize and say my interviewer will call me back as soon as he gets back from lunch.
7. He doesn’t call.
8. At 4:00 I call them back. Apparently the guy who was suppose to interview me went home. I ask them wtf they are doing and if this is how they treat their employees. They said they would reschedule the interview and call me back once they did.
9. No one calls.
10. I wait a week, call them back, and am told that the funding for my position didn’t come through (what does that mean? You’re not hiring programmers to design the software for your billion dollar war machines anymore? Seriously?).

I’ve had it with this company. I don’t know if it was just this incompetent recruiting group or if this is a company full of scumbags, but I mean, really?

Every single one of them, and every one that will come after them.

Google, it started out as 2 people in their garage, wanting to make a search engine that was better than the others. Nothing else, nothing evil. Just make the world a little bit better. And look what it's become now. A megacorporation with little to no regards for their user base. Because who cares about users anyway?

Microsoft, it started out with Bill Gates - young high school computer nerd - who wanted to make an operating system for the world to use. Something that's better than the competition. And boy did he do so. Well "better than the competition" aside, he did make it for the world to use. And the world adopted it. And look what it's become now. A megacorporation with little to no regards for their user base. Because who cares about users anyway?

See where I'm going here?

Apple, it started out with Steve Jobs and Steve Wozniak in their garage, just like Google did, wanting to make hardware that was better than the others. Nothing else, nothing evil. Just to make the world a little bit better. And look what it's become now. Planned obsolescence has been baked into it, just like it is in every other piece of technology. Quality control and thinking through the design has become a thing of the past. User choice, yeah who cares about that.

Samsung, it started out centuries ago actually, and I don't really remember the details of it.. ColdFusion has a video on it if memory serves me right. Do watch it if you're interested. Anyway, just like all the others they started out as a company which wanted to make the world a little bit better. And damn right did they do so.. initially. Look what they've become now. Forcing their stupid TouchWiz UI upon their customers (or products?), a Bixby button that can't even be reprogrammed.. and the latest thing.. Knox, advertised as a security feature, but as everyone who likes rooting their devices and mucking with it knows, it is an anti-feature that only serves for lockdown. Why shouldn't you be able to turn in a phone for RMA when a hardware error occurs, when all you've personally modified is the software? Why should changing the software blow that eFuse, so that you can be sure that you can't replace it without specialized equipment and a very steady hand?

I could go on and on forever about more of the tech giants out there, but I feel like this suffices for now. Otherwise I won't have anything else left for future rants! But one thing I know for sure. Every tech company started, starts, and will start out with a desire to make the world a better place, and once they gain a significant customer base, they will without exception turn into the same kind of Evil Megacorp., just like the ones before them. Some may say that capitalism itself is to blame for this, the greed for more when you already have a lot. Who knows? I'd rather say that the very human nature itself is to blame for it. We're by design greedy beings, and I hate it. I hate being human for that. I don't want humans to be evil towards one another, and be greedy for ever more. But I guess that that's just the way it is, and some things do actually never change...

FUCKIN advertising man...

I remember when the iPhone came out ten years ago, and everyone figured out that all they had to do was make a free app that had ads and they could get rich enough to retire. So there’s billions of apps now that are free adware bullshit. And it’s sad that even today in 2017 people still think this applies. The truth is there’s bout three people in the world that have made this work. People, if you’re considering generating a revenue stream, this does not work. Make something that is worth paying for, or don’t make it. Same goes for websites. Even if something not worth paying for gets enough users to make the ad revenue substantial (and that’s almost guaranteed not to happen with the current state of things) at best you have a bunch of people wasting their time on something not worth paying for. Which is just sad...

It’s one thing if you’re making it because it’s worth something to you to put something out there. Even if it’s not something worth paying for like your personal blog, take your pride and dignity and swallow the hosting cost. It’s the classy thing to do, and that way you don’t willingly sign up to be a google slave and subject your readers to relentless abuse and data mining (loading ads from a party is just one of the many ways google will figure out who visited where)

If you’re running a small installation that nobody wants to pay for, then you don’t need help paying for it, and if you’re running a large installation that nobody wants to pay for, then why the hell are you doing that!?

If you’re running any size installation that people are willing to pay for, problem solved. Imagine that. And you don’t have to ruin it with ads and subject your users to that kind of abuse. Put the dignity back in software design for the love of god.

The only winners in advertising are the advertisers and the ad companies. The advertisers win because they change your behavior in their favor in the long run, and the ad companies win because their product scales across as many websites as they want and it costs them NOTHING to do so, and requires NO work. And it matters not to them how many apps and websites and developers go under. There’s plenty more who think they can make a living off of ads in line to take their turn. As the end user, you will not be a winner. Just used to make other people winners

Dignity. Put it back in software development.

Sometime in mid 2013 or 2014 as a junior dev I woke up to a call from my company's CEO. He informed me that the legacy system they use for order processing is down nationwide that nobody can add new orders until it's fixed and that I needed to fix it. I had been working there 6 months and was hired along with a senior dev to begin developing a web app to replace this legacy system. The senior dev had left the company two weeks earlier for a better offer so it was put on me to figure it out. I was very frank with the CEO and told him I didn't know if I could fix it and suggested he try to call the company they hired to create it. I didn't even know where the source code was let alone what the design paradigm was or whether or not there was any documentation. He said he would try figuring out who created it and give them a call and asked "As a developer you shouldn't you be able to fix this?" I just told him it wasn't that simple and left it at that.

I get to work and the CEO has discovered that the company who created the software no longer exists and I tell him he may need to find a company to consult on this if I can find the source code and if I can't find the code he might be screwed.
I found the source code in a random IT shared folder there is no source control, no documentation, no unit tests, no test environment, and it looks like nobody had touched it since 2005 or about 8 years.

Despite being completely unfamiliar with the code and the design paradigm I was able to figure out that they were validating customer addresses against an old Google geocoding API that was shutdown the day before and the lack of response was killing the application. I fixed the issue and warned the CEO before deployment that I wasn't able to test but he said to go ahead and thankfully all went well.

Dev1: We need you to name this service
Dev2: Name it whatever
Dev1: You should name it
Dev2: Can we change it later?
Dev1: No
Dev2: Are you going to have dependencies on the name
Dev1: Yes
Dev2: Call it StupidDev1
Dev1: Ok we will name it

I had been a "hobby" programmer for well over a decade, with my primary career being in repair or a "technician". I had taught myself dozens of languages because it was fun, but never really accomplished much.

I was laid off from my job as a technician and I found myself listless and without purpose. I started doing development again on random things to pass the time and I ended up volunteering as a developer for a game I had played for years.

At the same time I had an uncle who encouraged me to consider software as a career. These two things gave me the confidence to apply for a local software job I saw on Indeed.

They called me pretty quickly, and I was brutally honest. "No, I don't have a degree. I'm self-taught. I have no professional experience really."

I got a proficiency exam anyway and I took it - apparently doing well enough on it that the CTO called me a week later. We had a long talk and I finally asked him why he called me.

He told me that while a degree means something, the passion to learn this job means more to him. It was a month before I was offered the position, and I graciously accepted it.

We had a call about my compensation before starting. It was rather low, but we both agreed that my skill level was quite an unknown.

A year later and my pay was bumped up a sizable amount. My skills are defined now and growing rapidly as new challenges are sent my way. I went from a naive hobbyist to a professional in a short period of time.

I realized that I was always a professional. I had a desire to learn and a desire to do things the right way. I may not have known what to call things. I didn't know some of the design patterns I had used over the years were standards that had names and meaning.

I basically work two jobs now. My full-time job and also on the game that helped propel my career forward and gave me the confidence to reach for it.

As for my hobby? I turned to electronics and the maker community. It's a nice marriage with my programming skill set, and I never knew how rewarding a blinking LED would be. :)

As a human being, you're multithreaded. You can type with multiple fingers, you can drive and hold a conversation at the same time. The only blocking function we have to deal with is sneezing, where all current activity must be suspended for the duration of the sneeze. That's pretty annoying, especially when you're driving and trying to hold a conversation. You don't want to write code that's sneezy.

"There are two ways of constructing a software design; one way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C. A. R. Hoare

Hi,
I'm not a ranty person so I never actually thought I'd post anything here but here it goes.

From the beginning.
We use ancient technologies. PHP 5.2, Symfony 1.2 and a non RFC complient SOAP with NO documentation.
A year ago We've been thrown a new temporary project. An VOIP app for every OS.
That being iOS, Android, MAC, PC, Linux, Windows mobile. With a 3 month deadline. All that thrown at 4 PHP developers. The idea being that They'll take it, sign the delivery protocol, everyone happy. No more updates for the app needed. They get their funds they needed the app for and we get paid.

Fast forward to today...

Our dev team started the year with great news that We'll most likely have to create a new project. Since the amount of new features would be far greater than current feature set, we managed to finally force our boss to use newer technologies (ie. seperate backend symfony4 PHP7+/frontend react, rest api and so on). So we were ecstatic to say the least. With preestimates aimed at a minimum 3 month development period. Since we're comfortable with everything that needs to be done.
Two days later our boss came to me that one of our most annoying clients needs a new feature. Said client uses ancient version written on a napkin because They changed half of the specification 2 weaks before deadline in a software made not by a developer but some sysadmin who didn't know anything. His MVC model was practically VVV model since he even had sql queries in some views. Feature will take 3 days - fixing everything that will break in the meantime - 1-2 months.
F*** it, fine. A little overtime won't kill me.
Yesterday boss comes again... Apparently someone lost a delivery protocol for a project we ended that half a year ago. Whats even better at the time when we asked for hardware to test we never got any. When we asked about any testing enviornment - nothing. The app being SEMI-stable on everything is an overstatement but it was working on the os'es available at the time. Since the client started testing now again, it turns out that both Android app does not work on 8.1/9 and the iOS app does not work on ios12. The client obviously does not want to pay and we can do little with it without the protocol, other than rewriting the apps.
It will take months at least since all of those apps were written by people that didn't know neither the OS'es nor the languages. For example I started writing the iOS one in swift. Only to learn after half of the development time, that swift doesn't like working by C Library rules and I had to use ObjC also. With some C thrown in due to the library. 3 unknown languages, on an unknown platform in 3 months. I never had any apple device in my hand at that time nor do I intend to now. I'm astonished it worked out then. It was a clusterf**k of bad design and sticking everything together with deprecated apis and a gum. So I'll have to basically fully rewrite it.

If boss decides we'll take all those at the same time I'll f***ing jump of a bridge.

“Don’t learn multiple languages at the same time”

Ignored that. Suddently I understood why he said that. Mixed both languages. In holiday rechecked it and it was ok.

Sometimes mistakes can lead to good things. After relearning I understood it much better.

“Don’t learn things by head” was another one. Because that’s useless. If you want to learn a language, try to understand it.
I fully agree with that. I started that way too learning what x did what y did, ... But after a few I found out this was inutile. Since then, I only have problems with Git

Another one. At release of Swift, my code was written in Obj-C. But I would like to adopt Swift. This was in my first year of iOS development, if I can even call it development. I used these things called “Converters”. But 3/4 was wrong and caused bugs. But the Issues in swift could handle that for me. After some time one told me “Stop doing that. Try to write it yourself.”

One of the last ones: “Try to contribute to open source software, instead of creating your own version of it. You won’t reinvent the wheel right? This could also be usefull for other users.”

Next: “If something doesn’t work the first time, don’t give up. Create Backups” As I did that multiple times and simply deleted the source files. By once I had a problem no iOS project worked. Didn’t found why. I was about to delete my Mac. Because of Apple’s WWDR certificate. Since then I started Git. Git is a new way of living.

Reaching the end: “We are developers. Not designers. We can’t do both. If a client asks for another design because they don’t like the current one tell them to hire one” - Remebers me one of my previous rants about the PDF “design”

Last one: “Clients suck. They will always complain. They need a new function. They don’t need that... And after that they wont bill ya for that. Because they think it’s no work.”

Sorry, forgot this one: “Always add backdoors. Many times clients wont pay and resell it or reuse it. With backdoors you can prohibit that.”

I think these are all things I loved they said to me. Probably forgot some.

Sometimes I have really loose the will to live and find myself face palming multiple times.

I added live chat software a web frontend for a client. Very easy job that consisted of pasting in some embed code. The actual software is very good and has native ios/andriod apps - something specifically requested.

I got a call from my client about an hour ago, saying there is a "serious issue with the live chat".

My client stated the live chat won't work when his staff go home. He asked me what my solution to this was.

Saying "wtf" many times to myself I directed him to a settings within the chat software i.e. an "away mode" where an email is sent when no chat agents are available.

This apparently wasn't good enough and said I hadn't followed his brief of "adding life chat software to the website", which I had.

After a lengthy discussion I found the root of his frustration. He'd signed a contract with a client of his own, stating there would be 24/7 support via live chat on the website.

Obviously there a huge difference between adding a chat widget to a website and committing to having it manned 24/7 :)

After a further 10 minutes of trying push the blame on myself, the client insisted of having the chat software "appear" as someone was always online, even when they are not (people need to sleep ya know!).

Bu design, the chat software requires at least one agent be logged in before the chat status changes to "online" - why wouldn't it.

After a little while I was seriously wondering why I'm involved in this conversation. I jokingly stated: "Well you could always install Andriod/iOS app on your phone, login and permanently leave it running in background. You'd get lots of notifications, but the site would say the live is always online".

The latter was something I said in jest. To my surprise the client said he'd do that on his own phone going forwards. He actually thanked me for my "resourcefulness", lol.

I'm looking at the same dashboard now and there are 407 pending chat requests - his phone must literally be blowing up notifications :)

I think we're going two sides:

For one, more and more technology is being developed/engineered which is even more and more and more intrusive as for personal privacy, I'm genuinely worried how this'll go as privacy isn't just a about not exposing certain things like passwords/bank account details and so on, it's also about being an individual who has their own thoughts, opinions and so on. If we keep taking that away more and more often, society will change and go towards the Orwell scenario (we're on our way there right now). We can change this as software/design/server engineers but that's up to us and I sadly don't see that happening quickly, also due to the 'nothing to hide' bullshit.

Second one is that were going more and more towards open source.
This is a good thing as this:
- gives freedom to devs around the world to improve software and/or modify it to suit their needs.
- gives people the opportunity to look through the source code of softwares in order to verify it as for backdoors and find security vulnerabilities which otherwise can remain hidden for the general public while spying agencies have way more resources to go vulnerability hunting.

For the people who think this isn't a good idea (even more open source), without it we'd be completely fucked as for moving forward/security/privacy. (I can give examples if wanted).

I just told my biggest client that they have to start changing things or they will need to find a different company to work with.

I'm hired to program what they want. They are suppossed to do all the concepting, functional designs, QA, testing.

So they tell me to program feature x, not realising that this interact with feature y. And then complain about the change in feature y. Make me do a lot of extra work and then complain that my estimates are way off.

So I told them they also need to hire my company for the software design and QA and prefferable testing because I'm done getting blamed.

Designing a new software product: 1000 hours

Designing a logo and picking a color scheme that pleases everyone: 689236323447876 hours

Help.

I'm a hardware guy. If I do software, it's bare-metal (almost always). I need to fully understand my build system and tweak it exactly to my needs. I'm the sorta guy that needs memory alignment and bitwise operations on a daily basis. I'm always cautious about processor cycles, memory allocation, and power consumption. I think twice if I really need to use a float there and I consider exactly what cost the abstraction layers I build come at.

I had done some web design and development, but that was back in the day when you knew all the workarounds for IE 5-7 by heart and when people were disappointed there wasn't going to be a XHTML 2.0. I didn't build anything large until recently.

Since that time, a lot has happened. Web development has evolved in a way I didn't really fancy, to say the least. Client-side rendering for everything the server could easily do? Of course. Wasting precious energy on mobile devices because it works well enough? Naturally. Solving the simplest problems with a gigantic mess of dependencies you don't even bother to inspect? Well, how else are you going to handle all your sensitive data?

I was going to compare this to the Arduino culture of using modules you don't understand in code you don't understand. But then again, you don't see consumer products or customer-specific electronics powered by an Arduino (at least not that I'm aware of).

I'm just not fit for that shooting-drills-at-walls methodology for getting holes. I'm not against neither easy nor pretty-to-look-at solutions, but it just comes across as wasteful for me nowadays.

So, after my hiatus from web development, I've now been in a sort of internet platform project for a few months. I'm now directly confronted with all that you guys love and hate, frontend frameworks and Node for the backend and whatever. I deliberately didn't voice my opinion when the stack was chosen, because I didn't want to interfere with the modern ways and instead get some experience out of it (and I am).

And now, I'm slowly starting to feel like it was OKAY to work like this.

I work as a software developer for a small and specialized company on a very popular, albeit niche, piece of system software.

This software has been around for a while, and in that while it has ages. If there is one thing you could say to have aged gracefully--well, this thing ain't it. The codebase itself is what anyone would expect of a large-ish C++/C product started in the mid 2000s: documented poorly (and where it is documented, documented *wrong*), full of obscure bugs, full of idiosyncratic design choices that caused the obscure bugs in the first place, and a code style--or rather a general approach to software engineering--taken straight fom the 80s.

It is also fair to say that the product has been developed by marketing. What started out as a company-internal project to help others get work done was perceived as valuable for others, quickly rushed out to market, and "developed" by listening to whichever customer screamed loudest at that point in time. ("Developed", in the "duct tape and WD40" style of development similar to an early 90s web page: the result has no class, no style and everything users find "interesting" to interact with is a java applet.)

About six months ago the powers that be finally acknowledged that a codebase that has not seen a single line of refactoring since its inception over ten years ago is not a solid foundation for further business. What was once an openly hostile attitude towards refactoring and general improvement of the codebase itself rather than the set of user-visible functions slowly morphed into a secretly hostile attitude. Upper-level management continued to denigrate developers seeking to improve the system citing their own experience ten years ago as reason why things must still be done exactly as they have did. Parts of this upper-level management were soon complimented on their work and it was suggested they take the next step in their carreer.

Which they did, with two toes of one foot. The other eight remained in internal discussions and, more importantly, inside the head and arse of the new managers. Which promptly turned just as secretly hostile and blocked all attempts at improvement. Instead it is highlighted that the developers are clearly not smart enough to do their jobs.

Meanwhile the entire project is falling behind deadlines. We've failed to deliver on three accounts already and are now nine months behind on another plan that was set for 15 months nine months ago. (Yes. We have officially started working on this thing, but no work has been done. More to the point, work has been *started*, but is stalled or rejected continuously because "that's not what we would have done five years ago" or "you can't change that, whoever wrote it must have thought about this a lot.")

And now upper-level management has begun reverting changes that same upper-level management has requested and signed off on. Without communication. So that developers don't start work on things they have not signed off on (because they don't read the plans or give any feedback). Because developers are not qualified for their jobs and must be closely monitored to ensure they don't break stuff. Which was already broken. Because the product has been bitrotting since birth.

Fuck my life.

So far all designers I worked with do the following:
1. Use "creativity" to come up with stuff that the system does not allow implementing, for example: Changing clock color in mobile statusbar to Blue!
2. Use "creativity" to come up with a heavily customized calendar for a windows software which requires building the control from scratch, but they explain their creativity by saying: Can't you use CSS?
3. Provide iOS only design which follows android guidelines and refuse to provide android styles for at least pages that to be handled differently on each platform, for example, we had a checkout page in an app, and they wanted the same style for both WITHOUT building custom control for it, they said: Can't you use the android custom control inside iOS
4. They design for a website and send same mockups for me to implement on mobile apps, the problem is a web page runs on a big screen when the mobile app doesn't have room for half the stuff they designed but they must look exactly the same as website !!
5. They send entire PSD with no color codes and say: You can extract icons, and colors from psd ... When they should provide them as per our request which is: SVG for Android and PDF for iOS with the color codes, but no, they are lazy!
6. They ask the team to create a page in the app which is almost production ready just so that they test different font sizes and see how it will look on the phone
7. Same as #6 for images that contain text

The list goes on, but those are by the far the ones that made me one step away from resigning, some of them made me resign...

Person 1 : Dude you should try using GNU/Linux it's the best OS.

Person 2: Why?

Person 1: Umm well it doesn't get viruses, kinda

Person: 2: Can it play games?

Person 1: Steam sorta works. There's wine, and RetroArch is available even though it runs like shit

Person 2: Hm, what about productivity?

Person 1: Are you a programmer?

Person 2: Not really

Person 1: Oof. W-Well you can kinda do word processing... Forget about video editing, umm.. GIMP and Krita are there available.. Um, web apps?

Person 2: Is it updated regularly?

Person 1: Oooh yeah. Many of them are so bleeding-edge that they end up running untested software, breaking/screwing up the entire distro at times. Not that the software is good anyway.

Person 2: Is it customizable?

Person 1: You'll be customizing your distro with the same shitty software everyone else does. And theming? If you hate flat design, you're fucked. Most themes that have a bit of techy masculinity to them end up not working or have a hellish setup process.

Person 2: Well how do I try it out?

Person 1: *Rambles on for 20 minutes about the one billion distros there are when really the only thing important is the package manager & repos*

Person 2: Sounds like Linux is kinda shit

Person 1: HEY FUCK YOU ITS THE BEST OS ITS BETTER THAN WINDOWS MAK ALL OF THEM!111

A PCB I designed on the job over the last weeks shipped today! A benefit of hardware is the haptic element you have at the end of the design process - you made something touchable. (I am proud.)
Also, errors made earlier in the design process are permanent now. But other than on my software my design got reviewed, so I'm optimistic it'll not contain many if any.

I'm on vacation right now for moving stuff but I'm looking forward to do the "pick'n place" on monday. Soldering manually is quite relaxing for me, you should try it, too! ;)

In other news, I'm no longer sleeping on the floor in my home-office while the paint is drying in other rooms.
I already moved the most of my stuff - books and tech equipment are the worst - and I moved my furniture yesterday.
My new roommates are considerably quieter and my sleeping rhythm is slowly shifting back to normal.

So, I love scribbling ideas on a whiteboard, like I'm sure most developers here do!

It's a release of creativity and a starting point for many sources of software I've developed in the past. And something that doesn't happen all too often where I get an overflow of ideas and put them on a board.

This week was one such rare week where the ideas just came streaming in and the floodgates weren't able to hold them back...

Then came the dam wall down river... MANAGEMENT!

They had already sold a product to the customer that didn't exist yet and tasked a junior developer (I'm talking fresh out of school) to deliver. Of course, this was promised last year already and now the customer had paid and is waiting for the goods!

Along I come with this design which will enable the product to grow, allow the junior development to learn, me to mentor and for us all to let the creative juices flow, all while I get to flex my web dev muscles.

But management wants something now! A temporary solution for the customer to keep them happy, seeing as they've paid some money, which is to be developed by the junior dev on his lonesome.

Meanwhile my beautiful design has been snuffed out and are mere streaks and smears on a whiteboard, and the creative juices seem to have dried up since.

I am feeling somewhat despondent at the moment...

Dear non-webdevs,

We don't talk bad about you. Why somayou mad at us? :D

There are 2 kind of programmer.

The first kind is the kind who love to create useful software/product, they would use the same tool/language/technique over and over again but focus on the use case. They end up having few really good softwares.

The later kind have more tendency about clean code. They are passionate about algorithms and design patterns. They can write a todo list app in 100 of different ways. They often pick up new technology, they rarely have something made coz they feel superior knowing different kinds of framework.

Which one is better software developer? Either one is better than the other, coz it's different pursuit. Like Thomas vs Tesla, we need these 2 kind of people in the industry.

Client support ticket: we printed the ID cards without leading 0’s can you fix it with software?
Me: unfortunately we cannot because the ID number can be any length. ID 123, 0123 and 00123 can exist. What barcode would 123 go to?
Client: this is ridiculous we will cancel our contract.
Me: i’m sorry we can’t correct for a mistake on your end.
(Side note: I know allowing 0123 and 00123 is dumb but my team didn’t design the business logic)

Describe the most hellish development environment you can imagine for yourself:

Me:

Workstation OS: Windows Vista with network boot, no hard disk and can't save local files

Server OS: Closed physical appliance of Windows Server 2000 with no possibility of installing extra software

Languages: Visual Basic, Perl, Php, assembly, ABAP

IDE: None, just echoing code lines to files

Web technologies: IIS, Sharepoint, Java applets, asp

Network: No internet access, internal company network only

Web browser: IE 6

Graphical design software: msPaint

Version control: Emails

Team communication: Emails

Software distribution vector: Emails

Boss: some 40 year old guy who knows nothing about computers

Not kidding most of these stuff were actually real in my previous workplace.

LONG RANT ALERT, no TL;DR

* Writes an email to colleague about why I can't create a page on our CMS without at least a H1 title. She wants to me to put up an image with text on it (like a flyer), for multiple reasons, I say I need a textless image. *

30 minutes later:
* Casually plans a frontend optimization project, by looking at files on the CMS, in order to make further development easier and less time-taking*

*** EMAIL NOTIFICATION ***
* clicks *

"Hello, this is [Graphic designer] from the company who created the image with text on it. I do not understand why you can't put display:none on your <h1> tag. Also, being a web company, we are used to making themes and my solution of display:none will work. It's pityful to work on a design only to have it stripped out from most of its concept. If you can't do that, do tell me what resolution you need."

My first reaction:

"Dear [Graphic designer], I am managing our corporate identity, our backend and frontend codebase, I am a graphic designer myself, and am also SEO-aware. For at least 8 reasons (redacted, 'cuse too long), I will need an image without text. As told to my colleagues, I need a 72/96 DPI 16:9 ratio image, 1920x1080 is a good start but may be bigger. Also, looking at the image, it'll have to be in JPG, at 100% quality, exported for the web. Our database software will optimize the image by itself."

Reasons are about SEO issues, responsiveness issues, CMS tools issues, backend and frontend issues.

Instead, I sent following email "We can't. Image please."

I mean seriously. A bit of clarity for you:

In my company, nobody has the slightest idea what I do. They don't understand how a computer works (we all know it works by magic, right?). So of course, when one thinks what we don't know, we know it better than the one who knows, my colleague thought our CMS was like a word document, and began telling me how I should display her bible-length text-infected image, by using some inline css styling display:none.

I tell her "nope, because of my 8 reasons". She transmits that to the agency who's done the visual, now I have this [Graphic designer] not understanding that there are other CMSs than Wordpress on the web, and she tells me, me being one of the most aware on this CMS we have, how I should optimize my site?

Fucking shit, she connects on our CMS for 1 second and she'll get cancer since it's so bad. I'm in the process of planning a whole new rewrite so the website is well designed (currently I am modifying a base theme made by an incompetent designer). I know the system by heart and I know what you can, or can't do.

Now I just received an answer: "so it's only a pure technical problem". NO, OUR WEBSITE WAS CODED BY A CHIMPANZEE WHO THOUGHT WEB DEV WAS AS EASY AS WRITING "HELLO WORLD" ON A SHITTY CMS THAT FORCES DEV USERS TO USE A FUCKING CUM-WHITE-THEMED EDITOR TO EDIT THE WHOLE SITE!!!

I can't just sneeze and "oh look, it's working!"

Remove all the outdated and unwanted topics which were taught during Indus Valley civilization like: 8080 microprocessor, Java 6, Software Testing principles etc. And add more interesting and realistic topics like: Algorithm design, graphs and other data structures, Java 8 (at least for now), big data, Basics about AI, etc.

You know what really grinds my gears? As a junior webdeveloper (mostly backend) I try my hardest to deliver quality content and other people's ignorance is killing me in my current job.

Let's rant about a recent project I had under my hood, for this project (a webshop) I had to restructure the database and had to include validation on basicly every field (what the heck, no validation I hear you say??), apperently they let an incompetent INTERN make this f***king webshop. The list of mistakes in this project can bring you close to the moon I'd say, seriously.

Database design 101 is basicly auto incremented ID's, and using IDs in general instead of using name (among a list of other stuff obv.). Well, this intern decided it was a good idea to filter a custom address-book module based on a NAME, so it wasn't setup as: /addressbook/{id} (unique ID, never a problem) but as /addressbook/{name}, which results in only showing one address if the first names on the addresses are the same. Lots of bugs that go by this type of incompetence and ignorance. Want to hear another joke? Look no further, this guy also decided it was a great idea to generate the next ID of an order. So the ordernumber wasn't made up by the auto incremented id on the order model, but by a count of all the orders and that was the next order number. This broke so many times, unbelievable.

To close the list of mistakes off, the intern decided it was a great idea to couple the address of a user directly to an order. Because the user is able to ship stuff to addresses within his addressbook, this bug could delete whole orders out of the system by simply deleting the address in your addressbook.

Enough about my intern rant, after working my ass of and going above and beyond the expectations of the customer, the guy from sales who was responsible for it showed what an a**hole he was. Lets call this guy Tom.

Little backstory: our department is a very small part of the company but we are responsible for so much if you think about it. The company thinks we've transitioned to company wide SCRUM, but in reality we are so far from it. I think the story below is a great example of what causes this.

Anyway, we as the web department work within Gitlab. All of our issues and sprints are organized and updated within this place. The rest of the company works with FileMaker, such a pile of shit software but I've managed to work around its buggyness. Anyway, When I was done with the project described above I notified all the stakeholders, this includes Tom. I made a write-up of all the changes I had made to the project, including screenshots and examples, within Gitlab. I asked for feedback and made sure to tag Tom so he was notified of my changes to the project.

After hearing nothing for 2 weeks, guess who came to my desk yesterday? F**king tom asking what had changed during my time on the project. I told him politely to check Gitlab and said on a friendly tone that I had notified him over 2 weeks ago. He, I shit you not, blantly told me that he never looks on there "because of all the notifications" and that I should 'tell him what to do' within FileMaker (which I already had updated referencing Gitlab with the write-up of my changes). That dick move of him made me lose all respect for this guy, what an ignorant piece of shit he is afterall.

The thing that triggers me the most in the last story is that I spent so much free time to perfect the project I was working on (the webshop). I even completed some features which weren't scheduled during the sprint I was working on, and all I was asking for was a little appreciation and feedback. Instead, he showed me how ignorant and what a dick he was.

I absolutely have no reason to keep on working for this company if co-workers keep treating me like this. The code base of the webshop is now in a way better condition, but there are a dozen other projects like this one. And guess what? All writen by the same intern.

/rant :P

Software Architect - The person who write code that most of the developers can't understand. Reusable component he says. Motherfucker a simple todo list app has more than 200 functions?!

1. Read about software engineering/design patterns, tools etc.
2. Adopt information to my requirements
3. Write code
4. Delete my shitty code from point 3.
5. Goto point 3

1 - I have this incredible software idea
2 - I start coding right away
3 - I get stuck because I don't know how to use some function and start googling
4 - I don't find a solution for the coding problem I had, but instead I find out that someone already made the brilliant software I was trying to make, with more use cases covered, better design and stuff.
5 - I remember the uncountable times this had happened before
6 - *goddammit*
7 - Think about making a tattoo that says "google it before coding it"

Hello World! First post here. I'm literally done with frontend stuff. I want to design code, not to code design. Unless it's Processing. I find it cute. So.. I have a somewhat handy grasp on C++ because of a class in electronics course, Python seems quite easy to catch. I'm totally new to programming. I'd like to get into software, game development and android development (but I would like to do things cross-platform).
Which paths, resources, languages, useful books, videos, or just anything would you recommend?

To be fair, I have no coding friends so mentorship or simply finding code buddies would be great. 💜

Some Quotes to Read :

1. The best thing about a boolean is even if you are wrong, you are only off by a bit. (Anonymous)

2. Without requirements or design, programming is the art of adding bugs to an empty text file. (Louis Srygley)

3. Before software can be reusable, it first has to be usable. (Ralph Johnson)

4. The best method for accelerating a computer is the one that boosts it by 9.8 m/s2. (Anonymous)

5. I think Microsoft named.Net so it wouldn’t show up in a Unix directory listing. (Oktal)

6. If builders built buildings the way programmers wrote programs, then the first woodpecker that came along wound destroy civilization. (Gerald Weinberg)

7. There are two ways to write error-free programs; only the third one works. (Alan J. Perlis)

8. Deleted code is debugged code. (Jeff Sickel)

9. Walking on water and developing software from a specification are easy if both are frozen. (Edward V Berard)

My first real programming job was a 30-hour per week part time job for a large multinational company. The division I worked in was a mechanical engineering group which designed truck gears, located in a two-building campus in rural Michigan, literally surrounded by corn fields. The entire organization was steeped in Dilbertesque dysfunction, as will be made clear below. (The saving grace was my boss, who, in addition to being a really great guy, was universally recognized by his peers as being the smartest guy in the room. Naturally he got very little respect from his "superiors". I want to go back in time, grab him by the tie, and shout "get your ass to Silicon Valley! And stop wearing ties.")
Most of my work involved making updates to an in-house document approval workflow system in C++, but one day my boss and his colleague came into my cube, handed me a thick stack of red paper, and said, "we need you to port this to C++." I looked at it, and it was several hundred pages of printed BASIC code. I started asking the obvious questions: "What is this?", "Is this the only copy we have?", "Why don't we have the source files?", "Why is it printed on red paper?"
The answers were that this was a very important program that did some mathematical functions/algorithms/calculations related to gear design; that it was written by a mathematician in the Manchester UK office; that we needed some modifications done to the software but the Manchester group wouldn't cooperate, and they wouldn't give us the source code; that one of "our" guys, in an act of justifiable internal corporate espionage, swiped the printout on a recent trip to the Manchester facility; and that they needed me to port it to C++ so we could enhance/maintain it, because the current BASIC implementation was unintelligible. As for the red paper? Well, it's because this program contained extremely valuable proprietary trade secrets, so it could only be printed on red paper, to make it harder to photocopy.
I started looking at the code. It was old-school BASIC, full of GOTO's and GOSUB's. There were a lot of global variables, and their names were all two or three characters in length -- "a1", "a2", "b1", "b2", "aa1", etc. It's worth pointing out that the source had not been run through an optimizer; this is how the guy actually coded it.
I do not have an engineering background (I didn't even know what a spline was), so had no way of comprehending what the program was doing, but there was a lot of math. I was a monkey, blindly translating incomprehensible code from one language to another, coming up with descriptive variable and function names as best I could. I figured if I could just get it into C++ in a more intelligible form, and get it to compile, someone who knows what he's doing could pick it up from there.
I found another job not long after starting on this task. The cool thing is, because I was only part time, and because my boss was well aware of what a crappy gig it was, I had no qualms about using him as a reference. I was sitting in the adjacent cube when I took the reference call, and got to hear him say wonderful things about me. When the call was over he poked his head over the cubicle wall and gave me a grin.
In retrospect it's not surprising that they liked me so much. It couldn't have been easy to find someone who's any good, willing to work such a shitty job at such low pay; plus, I was a good sport about the red paper BASIC program project. The company tried to get me to stay with an offer of full time employment at a salary 30% higher than where I was going. Needless to say, I declined.

Software Design Guide:
step 1: Add dark theme support
step 2: ...

Was forced to do some work on Windows this week (CAD tools that runs only on Windows). I spent a few days just setting up the tools. There were quite a few things I realized I forgot about Windows (as compared to Linux).

1) Installation times are down right horrific. What exactly are the installer doing for 10 minutes?
2) .NET is a cluster fuck. Not even Microsofts repair tool can fix it, but rather just hangs. I ended up using another tool to nuke it and reinstall.
3) Windows binary installs are insanely huge, thus, takes forever to download.
4) The registry is a pointless database that must have been written in hell with the single intent of destroying users will to live. The sole existence of the registry is another proof that completely incompetent engineers designed Windows.
5) Rebooting is the only way to solve many problems. This is another sure sign of a fundamentally fucked up OS design.
6) What the heck is wrong with the GUIs designers? The control panel must be the worst design ever. There are so many levels to get to a particular setting I'm getting dizzy. Nothing gets better by the illogical organisation.
7) Windows networking. A perversion of the tcp/ip stack that makes it virtually impossible to understand a damn thing about the current network configuration. There are at least 3 different places that effects the settings.
8) Windows command prompt. Why did they even bother to leave it in? The interpreter is as intelligent as retarded donut. You can't do anything with it, except typing "exit" and Google for another solution.
8) Updates. Why does it takes hundreds of updates per month to keep that thing safe?
9) Despite all updates that is flying out of Redmond like confetti, it is still necessary to install antivirus to keep the damn thing safe. That cost extra money, and further cost you by degrading performance of your hardware.
10) Window performance. Software runs like it was swimming in molasses. The final stab in the back on your hardware investment, and pretty much sends performance on your hardware back a few hundred bucks more.
11) Closed source is evil. If something crash consistently, you might find a forum that address the issues you have. Otherwise you're out of luck. On the other hand, it might be for the better. I imagine reading the code for Windows can lead to severe depression.

I'm lucky to be a Linux dev, and should probably not complain too much... But really, Windows, go get yourself hit by a truck and die. I won't miss you.

So having gotten my hands on the books I need for the next semester I decided to go take a look at what's in them.

Now the first is mostly web stuff and the second is just about software design. It starts off with an introduction to HTML5, where they didn't really teach HTML5, more like they taught HTML3/4 but not in a way that was too dangerous. I can tolerate not having my semantic tags tbh. They also used spaces on both sides of the = for some reason.

Then a CSS chapter which was also surprisingly mediocre. They didn't use a dedicated CSS file, but I can live with that, for starters.

Then there were some surprisingly decent JS chapters. Although they did use newlines before their { kinda miffed me. There has also been a few developments since this books release, but tbh this isn't the worst case of outdatedness. (And at least they didn't use jquery when teaching JS)

Then a chapter on SQL which I ignored.

Then a chapter about PHP, and, uhm, when did this book get released? Well the ISBN is 978-0-13-215100-9 and using the power of Google we can reveal it was published in.. 2011..

I'm quite happy that I already know how to program

[Background]
My father works as a hardware developer in a medium-large company.

We(dad+me) also design and build test equipment to be used at said company.
Usually, these are Arduino controlled pieces of harware. I write the code for these projects.

[END BACKGROUND]

One of these projects had a simple communication system over serial(human readable commands).
I wrote a simple WinForms application (which loads a config XML and has a GUI to send these commands), because appearantly it's too hard for SOFTWARE DEVELOPERS(who are writing code for the device, which the test equipment is for) to use hyperterm(or some other serial monitor) to control it, when given a step by step maunal.

I get complaints, that this application(img) is 'not working' or 'too hard to use'. I works perfectly.
All you have to do is:
1. select com port(to wich the device is connected)
2. press connect; wat until it says "connected" After that, the option to "load config file" unlocks.
3. now, select the file(press '...' for openFileDialog) and press load.
4. Now the deafult settings are send immediatly. You can then, select the options from the list on the left, and change them with the radio buttons. The changes are automatically sent.

All these morons seem to be able to do is:
1. check the "expert mode" checkbox(opens up more options(unnecessary for their use case))
2. mess it up
3. complain

My father often complains, how bad the software devs(at that office) are.
They are (almost all, some exeptions) incompetent pieces of shit from India, who take age to do anything.
I had to look at some CVs and Resumés of them(both SW and HW). ( My father is the team leader and head HW dev and had to hire an HW dev They were full of bullshit and spelling errors, bad language and more.

Tl;Dr; Wrote software for use in my dad's company, software devs to stupid to use it.

This came up just now.. I can totally relate!

Okay so I have a lot of experience in UI/UX, graphic design, and Front End dev, but I hate it. My github and resume are full of front end shit because it makes up most of my experience, and so when I apply to software dev things I often don’t get interviews because of lack of exp.

Well today I got an email from a big company that I applied to over a month ago and they told me that I was an excellent candidate and that they’d like to interview me. I say “the position is still open? I applied over a month ago!” to which they respond “well, the position you applied to has closed, but we are looking to hire a UX developer and had your application in our UX pool of applicants”

I did not fucking apply for this. They saw my application and threw it into the pool for future UX gigs and I’m mad because I’m not in a position to not interview for this job but I also really want to work in software.

Do you think, assuming I got the job, that it would hurt my prospects further to work in UX?

First year: intro to programming, basic data structures and algos, parallel programming, databases and a project to finish it. Homework should be kept track of via some version control. Should also be some calculus and linear algebra.

Second year:
Introduce more complex subjects such as programming paradigms, compilers and language theory, low level programming + logic design + basic processor design, logic for system verification, statistics and graph theory. Should also be a project with a company.

Year three:
Advanced algos, datastructures and algorithm analysis. Intro to Computer and data security. Optional courses in graphics programming, machine learning, compilers and automata, embedded systems etc. ends with a big project that goes in depth into a CS subject, not a regular software project in java basically.

Working as a part time student on an app and until now I thought I was the king of software development.
Well, fuck me and my high horse.

Today the stuff we send from the client to the server didn't arrive, so I asked the backend guy if he could take a look at the packages arriving. He did and told me the data was messed up.
I did only design stuff the last week or so, so I was very confused. After reverting back to one old commit after the other it struck me.
I still don't know how such a dumb mistake could have happened to me, the king of Android apps, but apparently I replaced all occurrences of a specific keyword in just the strings and comments of the whole project. Key became KeyList, so instead of <Keys> my XML contained <KeyList> which made no goddamn sense whatsoever.
Did I mention that we have an important deadline tomorrow? Yeah...

So now I leaned my lesson. Never trust XML.

JK I'm dumb. That's the lesson here.

I once had a PM who would consistently ask us to fix one off "bugs" (read little design tweaks). He wouldn't even bother to write them down anywhere. He once came over and asked why we hadn't fixed one of his bugs. We had no idea what he was talking about. According to him, we were supposed to organize and prioritize according to his whim. He never logged into our task management system.

When it finally came time to sell off our work to some of the business owners, we showed some of the "bug fixes" we did because that's all we ever heard we were supposed to do. The business owners were mad that we hadn't done anything they had asked us to do. PM throws us under the bus saying that we didn't know how to do our jobs and that we never listened to him. I was so glad when he moved to be lead of the QA department. Then I wasn't so glad.

He would have bug quotas that his team would have to meet. He pitted the entire QA team against all of the devs saying things like, "All the devs suck at coding. It's our job to save the company and the world from their buggy software." He got the only good QA guy fired because he faked a bunch of documents stating that they had had performance reviews and no improvement was made (these meeting never actually took place), and that he hadn't been meeting his big quotas. He was outside of our department and was buddy buddy with one of the C-levels, so his word trumped ours.

Then one glorious day, after I had already left the company, his department was absolved into the technology group. That same day was the day he was fired.

I kind of pity him. I didn't know if he had a family, but how can a man such as that support his family? Perhaps he doesn't have a good relationship with his wife and that's why he sucked at his job?

I. HATE. DELL. WITH. MY. GUTS.

Their low tiers products are full black plastic overpriced fuckshit, if you press too much the cover you can actually destroy your display. Fuck shitty laptops and fuck this shitty laptop in particular. It's slow. It's so slooooooow. It's everflying fucking slow motion, being on the web is like being in the matrix while dodging bullets made of wordpress plugins. The only good thing I can say is that is living right now, it has been... Three years? I only picked it because of high discount and ubuntu preinstalled (that made me think: oh, maybe they have components that are linux compatible regardless of distros. It was not). I'm enjoying Manjaro, when I'll have the skillz i'm going full Arch.

I will start university this fall. It's going to be a math major. I absolutely need something better than this anyway. I am also freaking out because I don't know which genre of software they could want to make me install and if they're windows/mac only. In the meanwhile I do photography, video, design and as you may suppose Adobe is often my go-to; I also have to build a workstation at home. I am freaking out because WELL FUCK WINDOWS 10 AND ITS PRIVACY NIGHTMARE PERIOD.

Which laptop I buy?
How well does heavy software run in a Windows virtual machine (on the desktop, not the laptop)?

So, for the past...what, week or so? I've been working on a side project with @gianlu. It's the PretendYoureXyzzy fork - our attempt to rejuvenate an old shitty piece of software.

I had started working on a fork alone, and then he asked to team up so I was like "Sure, I got nothing better to do." So, he's working on the backend (and hooking JS up to the backend) and I'm developing the frontend.

I don't know why I thought tech would stand still. Google says they're putting MDL on life support and replacing it with a much more complex successor, MDC. It's not hard to use, but what really bugs me is the lack of notice on getmdl.io. If you are switching to another project as your main focus, why the fuck wouldn't you advertise in the most places possible?

Granted, I don't do web design and/or development on the daily. Yes, I can do it, but I'm not always as up-to-date with web technologies as I'd like to be.

However, the screencap captured is the third time I've taken the knife to the UI. MDC is great tooling, at least to me. That dialog? Not something MDL would've had out the box on the first day. You'd have to work for that.

I don't have an issue with MDC, I have an issue with the lack of PR around it.

How I felt after spending an entire afternoon planning and designing a new feature for a project only to realize half of my design was wrong after I started implementing it

OsCommerce is literally the most awful piece of software ever. Granted, I'm migrating a version from 2007, but even still.

The admin area has a screen to set related products to a target product.

The page takes an age to load, even longer to save and is god awful to use from a UI POV.

Why may you ask?

The OsCommerce devs decided to display a flat list, which check boxes of ALL products in the database.

So for the site in question, that's a single list of 167,000 products, without pagination. Some of the worst development/design on a single page I've seen since last week when I inherited a god awful butchered Wordpress site :|

I'm a junior dev less than 1 year into my first job out of college. I'm halfway done reading Clean Code (my first software book out of college) and I'm really enjoying it!

What should I read next? I was thinking something about design patterns. Should I go for the classic GoF book or continue with Robert C Martin and read "Agile Software Development, Principles, Patterns, and Practices"?

Customer: I want to be included in any and all design and development meeting in the future.

Me: OK, I mean, I'm just one person so there's not formal meetings as such...

Customer: Nevertheless, I wish to be included and ensure my needs are met.

Some time passes.

Me: So, I'm thinking of swapping out the old Beanshell interface, cos, really... Interpreted, scriptable Java isn't great and most users don't want to write Java just to run some jobs. Could you help me with creating an API that fits you and your departments needs?

Customer: No, I'm way to busy to deal with this right now!

Me: And when would be convenient for you?

Customer: I don't know, just not now.

To this day, despite successfully integrating the rhino js engine into the app, part of the software I develop has a bean shell interface rather than js, Python or lua.

-_- I hate bean shell...

A few months back, my Dad's friend (mother of a 10th grade student) asked me for help on her daughter video editing school assignment because I study 'computers'.

Me on the outside: 'I am sorry, I wouldn't be of much help here as I have zero experience with video editing'
Me on the inside: 'I am sorry, I design and develop software. I am not an all-knowing genius that knows everything even remotely connected to computers.'

- finish the app for my school
- FUCKING finish the google scholarship before time ends ._.
- learn git
- build a home fileserver, like a own cloud, which can be accesed even further away (has any one some tips on how to do it? ^^)
- attach a gps tracker to my moped, which I can then see on a mobile app (because I don't want it to be stolen...)
- rebuild my homevillages website
- learn python
- replace my android Java with kotlin
- apply to an internship for a software design company
- more and more and more
uff. ._.''

Hope you guys will have a nice and PRODUCTIVE 2018! :^)

!dev

I have this urge to get better at coding and software architecture and design. But fuck me if I'm not lazy about it.
All these crazy good books and lectures and here I am, doing jackshit to improve. Can't even finish my own personal projects. Bah.

I know how I'm supposed to go about it, how to keep engaged in a cycle of personal betterment. I lack self-discipline to do it though... Tried meditation for a time, but haven't really stuck to it. Currently trying to follow stoics (Seneca, Marcus Aurelius and some others), but the mindset is not so easy to adopt, and the practical philosophies even harder.

Oh well. Life is hard. Blah-blah-blah. Thanks for reading. Just wanted to vent, really.

I'm a .Net developer from Morocco, i'm currently working on an accounting software for this fucking company owned by an American boss. And i'm handling every single aspect of the project including the back-end (C#), Database (Sql Server), Reports (crystal reports, ABAP, VSTO), and design (UI, logos, animation...). For a salary of 300 USD/month, with no insurance, no transportation fees, and no fuck given about my health or my coworkers'. Not mentioning the shitty working hours and condition.
This is my first (job)

!Rant; Week40
Honestly, before starting my post secondary education in Computer science I had wanted to become an architect.
Since I was maybe.... 10 years old all the way till the semester before graduating from highschool I was sold on becoming an architect.
I love design; Interior design, art, unique use of colors, architecture. I love systems that looked good and worked as well as they appeared.
Over the winter break of my grade 12 year a friend said to me, "Why don't you become a UI/UX developer? You love technology, software and design, why not go into a career where you practice on all three?".
I was surprised to hear that. It had honestly never really occurred to me since I had always told myself I would become an architect.
I guess that leaves me to where I am now. Still a student, but loving my time learning the details behind software development. I do not regret choosing Development over becoming an Architect.

This picture represents a whole lot of things for me in software development when it comes to bad design or security... You add a new feature along the way and it seems to work well - but basically you f-ed everything up.

!rant

I know this may not be the typical post on Devrant and it may be a little off topic, but I could really use some advice from fellow colleagues here.

The thing is, I just finished engineering school and I got my first job as a software engineer. So far so good. I've never been a natural talent in this field, and I suck at writing code. I find things like architecture, system design, innovation, requirementsspecification, management and business development much more interesting.

These past weeks as a software engineer has been really challenging for me. I seem to be totally "in over my head", and fuck everything up. I can't understand how the code I'm supposed to write works, and can't solve even the simplest of tasks that are assigned to me if they involve any implementation of code, or fiddling with Github or build servers.

Is it normal to feel like this as an engineer with zero experience? Will things get better, or should I just resign or wait to be fired?

What would a natural next step for a software engineer who'd like to move more into business and management be? A MBA? Project management courses?

I hope to get some advice from you guys. Maybe you've felt like this when you started out as well? Anyway, any constructive feedback would be really much appreciated.

Rant rant = new Rant();
rant.type = Rant.REVELATION;
rant.content = "

Being depressed with recent stuff about my ex, I've been going out a lot more than I use to, thus engaging in conversation with people I've never talked to before, and it made me realize something. Maybe it's because the world it's more connected nowadays, but I think it's more about our career (be it CS Engineer, Software Dev, Web-Dev, etc...) and correct me if I'm wrong but I think we are the kind of people that knows about everything (maybe not everything, but know basic stuff that can't be considered general knowledge) because that's what we do, we spend our days updating ourselves, growing in knowledge.

What's my point? That, thanks to this ability, we can work, cooperate or even socialize in a rather easy way. For example, I learned bit of color theory and design principles for a school project. Fast forward some months, I meet this girl that had a degree in Digital Design and I could talk to her about her field, and even knew things she forgot.

I don't know, for me, it's amazing how we can shape shift and mold to the situation, easier than any other career.

Am I wrong or missing something? Let me know
";
rant.publish();

So client wants an android app that implements some legacy Epson printer SDK, works on a chinese Windows device with an android Emulator on it, connects to local Webservice that had to be configurated and ran (local Network) , sends and tracks data, if Server down then handle it on the Client and reconnect as soon as Server up, running own TCP Server on Android device that listens for specific http requests, which make the android connect to an Epson printer to start printing. The stuff that is being printed? A png file that has to be converted to a Bitmap, a QR Code that has to be generated by the bugged base64 encrypted stuff coming via http in (webserver-> Android TCP server)
Dont forget the Software Design (MVP), documentation, research etc.. Im about to finish the app , its my 5th day on this Project, the 6th day was planned to be full testing. Client Calls me and ask me how far I am, I reply, he says ok. 30 minutes later he tells me he wont pay me next time that much because this work should take 3 days, or even 2. "A senior Android developer could do this in 2 days"... When i sent him my notices he called me a liar, his webdev has alot of experience and told him it should take 2-3 days...ffs

Once again, I have to go with the guy that, after seeing my horrible (I can't highlight this enough) code, decided that even I wasn't hopeless, and went on teaching me the basics of software engineering, top-down design and unit testing. All of this in two days, but it gave me the motivation to work on it, and look at me now: I'm a devRanter :')

4 years ago I made a personal goal/plan to be a full stack developer. Meaning a good understanding of any development between os level code and web/front end user experience.

Over the years this term 'full stack' has been abused greatly and now basically means 'a javascript developer that generally knows what they are talking about'.

So now, devRant collective I ask you. What do you call a developer with good skills in:

- os level code (c, c++ and os apis)
- database level tech (advanced querying and db aglo/modeling)
- software architecture
- application level (workflow and business logic)
- transport level (protocol design and usage)
- front end tech (graphics programming and event driven paradigm)
- user experience

It's a toss up between a basic software portal for my old school as a volunteer thing or an old game designed around user content creation.

The portal is more of a personal success but the game was a success in the respect it ended up rolling past a Bethesda employee and he gave me a one on one Skype chat about there design methods.

I really lost my faith in our profession.
A Software&Hardware solution that costs more several 10.000€ is broken after every update.

The Producer even achieves to break untouched features in new releases.
No communication at all. If you report Bugs, they are your fault. The whole system has absolutely no security at all.
It is unsecure by design.

And even if they hear your Bug report you have to pray that they will fix it.
Most if the time you have to wait the whole year for a new release tio get your bugfixes.
But there are also bugs that are untouched for years.

WHY? WE PAY YOU!
I want to cry

The agency I own built a WordPress plugin for a client using a freelancer developer. The client, out of ambivalence, withheld information that would have drastically changed the design of the plugin, but by the time we found out it was much to late to start over. The developer moved overseas in the middle of it all and from then on was not very responsive to communications about the project which delayed things by months. I tried to find a replacement developer but nobody else had experience with the third-party API. The live version of the API ended up not being able to support what we were trying to get it to do with the plugin even though the test version of the API was fine and the vendor was unhelpful. And because we spent so much time and money on the plugin, we weren’t able to even begin on another part of the project. The client complained of over $30,000 in lost revenue due to these issues. Complete fail all around. I’m never doing another custom software project again. It’s all just website design from here.

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

> finds awesome front-end design software
> build a decent layout
> adds Phalcon stuff (started to use that a few days ago, works really nicely, just don't like the ORM as much as Propel2)
> software can no longer display the site layout properly

FML

Being a junior and part of a small team at a startup, working with a new software architecture, even the team lead is a beginner in it. It feels like I'm at an echo chamber, there's nobody expert enough to look up to if stuck, decisions seem to be based on opinions rather than an architectural design kinda point of view.

Ugh, I hope I'm not the only here ever feeling this way.

Everyone think google is trolling Apple’s notch. But as a software giant, google is tripped over css with its own material design🤦‍♂️

So opinions: should a software engineer get certifications? I mean, to me they seem like pointless wastes of money, but my coworkers don't seem to think so. I design and write code, why do I need MCSD or whatever? Follow up, if you feel they are useful: which ones and why?

Am I Data Engineer or Software Development Engineer ?

I design the infrastructure for analytics data, and I build the infra entirely including an development. Except making reports out of the data.

What I'm supposed to be called ?
Data Engineer ?
Software Development Engineer ?

Definitely not an Data Scientist. Official designation given by company is Data Engineer II. But what I'm ?

Confused, someone help me please.

Crazy deadlines> Director: "You need to design a new architecture that has failover, multi-AZ, automated deployments, CI/CD pipeline, automated builds/tests as well, for our new SaaS product. You have 3 days to complete it"

Me: "Ok cool. Do we have the new product developed? Can I have the spec docs of the new software, libs and packages required for the env?"

Product Lead: "No we dont have anything yet. The POC is on my local PC, but I dont know what packages are needed to run it"

Me: "So I cant design anything unless I have the minimum requirements to run the new software"

Director: "Just get it up and running in a live environment and we'll take it from there"

Me: *sigh*..this is going to be a big mistake

I think the worst thing I’ve seen from devs is lacking the curiosity to know how some software library works before using it which then almost always leads to bad design and code.

I want to read a good Software Engineering book. A modern one, which contains new agile approaches, useful diagrams, etc. Not the classical, not so useful, class diagram.

What do you recommend? I'm currently more into web and mobile apps, and I want to be able to describe my backend and frontend with useful diagrams which describe better to users and other developers my desired design.

Design and make an easily repairable laptop so I can graduate.

Figure out how to use blender for 3d modelling

Move the majority of software use to open sourced software.

!rant
Remember the Stress ball's TransOceanic Trackable Voyage? (Also called Devvie in a bottle.) Well, we're finalizing the design. But if you are interested in helping us with software, hardware, launching, recovery, or anything else that might help, join us at stotv.herokuapp.com. PS, we're also looking for sponsors, so if you are or know someone who is interested in sponsoring, send a message to @sven on Slack.

Worst architecture I've seen?

The worst (working here) follow the academic pattern of trying to be perfect when the only measure of 'perfect' should be the user saying "Thank you" or one that no one knows about (the 'it just works' architectural pattern).

A senior developer with a masters degree in software engineering developed a class/object architecture for representing an Invoice in our system. Took almost 3 months to come up with ..

- Contained over 50 interfaces (IInvoice, IOrder, IProduct, etc. mostly just data bags)
- Abstract classes that implemented the interfaces
- Concrete classes that injected behavior via the abstract classes (constructors, Copy methods, converter functions, etc)
- Various data access (SQL server/WCF services) factories

During code reviews I kept saying this design was too complex and too brittle for the changes everyone knew were coming. The web team that would ultimately be using the framework had, at best, vague requirements. Because he had a masters degree, he knew best.

He was proud of nearly perfect academic design (almost 100% test code coverage, very nice class diagrams, lines and boxes, auto-generated documentation, etc), until the DBAs changed table relationships (1:1 turned into 1:M and M:M), field names, etc, and users changed business requirements (ex. concept of an invoice fee changed the total amount due calculation, which broke nearly everything).

That change caused a ripple affect that resulted in a major delay in the web site feature release.

By the time the developer fixed all the issues, the web team wrote their framework and hit the database directly (Dapper+simple DTOs) and his library was never used.

They need to get rid of the Cook and employ a Chef.
It used to be creativity, foresight, instinct manifesting itself in great innovative design and software. Now we have everything focused on chasing the $. Just like Microsoft used to be, until that is they realised. Now Apple is the old Microsoft and Microsoft is the new Apple.
I live in hope.

I started fully exploring different aspects of tech in a middle school technology class where the teacher gave me a good grade as long as I did something that could be useful or interesting. I learned how to design webpages by playing with inspect element, and then decided to make my own with Notepad. One of my friends showed me how to use Sublime Text, and I found that I loved programming. Other things I did in there included using two desktops with NIC's wired directly to each other with an old version of Synergy and a VNC server, and at one point, I built a server node out of old dell Optiplex desktops the school had piled in a storage room.

Last year in high school, I took a class on VB.net and made some money afterwards by freelance refreshing legacy spaghetti, and got burned pretty badly by a person offering $25,000 for a major POS to backend CMS integration rewrite. The person told me that I had finished second, and that another dev had gotten the reward, but that he liked my code. A few days later, I was notified through a *cough*very convoluted*cough* system of mine by a trigger that ran once during startup in a production environment and reported the version number as well as a few other bits, and I was able to see that *cough*someone*cough* had been using my code. I stopped programming for at least six months straight because I didn't want to go back.

This year in high school, I'm taking the engineering class I didn't get into last year, and I realized that Autodesk Inventor supports VBA. I got back into programming with a lot of copy-paste and click-once "installers" to get my modelling assignments done faster than my classmates. Last week, one of my friends asked me to help him fix his VB program, which I did, and now I'm hooked again.

I've always been an engineer at heart, but now I'm conflicted with going into I.T., mechanical or robotical engineering, or being a software developer.

A little long, but that's how I got to where I am now. (I still detest those who take advantage of defenseless programmers. There's a special place for them.)

!rant
I decided to dive into programming by learning C#. Main reason behind it was to avoid the zillions of frameworks and technologies (which scare me) and most importantly dumb client requests. I already have a lot of xp as a designer and working for the web bizz was just UGH!

Nevertheless, I am still wondering if I should pick up some web technologies. I am planning to pick up .NET and C# design patterns next, but what then? Do you think it's smart to focus only on enterprise software development today? I don't mind developing a bigger web-based app or doing server-related stuff either. Everything but startups and developing sites for my cousin's friend's sister hair saloon.

What is the smartest way to go with C# as a starting point in terms of job opportunities?

Is it me or most developers just write code so it compiles and passes tests?

No documentation, no standards, no "good practices", no"good design", no software principles, no performance analysis, nothing.

1. Teach DS and Algos. Not basics but advanced data structures and the ones that are recently published.
2. DBMS should show core underlying concepts of how queries are executed. Also, what data structures are used in new tech.
3. Teach linkers, compliers and things like JIT. Parsers and how languages have implemented X features.
4. Focus on concept instead of languages. My school has a grad course for R and Java. (I can get that thing from YouTube !!)
5. Focus a little on software engineering design pattern.
6. It's a crime to let a developer graduate if he doesn't know GIT or any version control. Plus, give extra credits for students contributing to open source. Tell them if they submit a PR you get good grades. If that PR gets merged bonus (straight A may be ?)
7. Teach some design pattern and how industry write code. I am taking up a talk at school to explain SOLID design pattern.

Mostly make them build software!
Make them write code!
Make them automate their homeworks!

Make them an educated and employable student.!

Hi guys! I need your help.

I'm currently facing a big decision.
I've got a job offer a couple of days ago. The new job would involve an 80% raise to my current salary, and I would make another step on the hierarchy ladder.
BUT
The new place is not a software development company. They have a small team working on internal stuff, but they are basically maintaining a 12 years old garbage.
My job would be, to design the new system from the ground up. At the moment, the new system has to do the same things as the old one, just faster and better. Then they'd like to extend it further.
The first part is not challenging, but the things that they planned in the future sound interesting.

The problem is, that my current company just got a new contract and I'm supposed to conduct the deploy (speaking with their managers, prepare their sites for installation, and install). And since it is a small startup, the deploy depends highly on me.
If I take the new job, then I have to start in February which ultimately means that I screw my current company real bad. They'll probably survive, but they might lose this contract and/or lose money.

If I do what makes economic sense, then I take the job. (fuck it's almost 2x as much!!) But I have mixed feelings about it.
I've got 48 hours to decide.

What do you guys think?

principle software developer who does not code, design, or architect,

instead, do random eslint fixes which create conflict with everyone's branches.

1 line of code "fix" per commit.

there goes 26 commits

So, my job title is sql Developer, but recently I’ve been balls deep in A .Net application, not an issue, but there is a huge learning curve.

Anyway, earlier in the year I spent about 2-3 months manually entering price list and exchange rates into our ERP system. I proposed an app to help make this process easier, boss was happy so I knocked up a 20+ page software design document, covered everything, and laid out a road map I.e v1 would just be MVP, and additional nice to have features would be added incrementally.

Boss didn’t read the document, and didn’t mention it again.

5 months later I get an invite to a meeting to discuss my progress, which is this afternoon.

It was always going to be something I worked on in my spare time, so I currently have 5 models to show her.

Why not mention something for months and then ask for a progress update out of the blue?

My boss isn’t a dev so will just bury them in technical details which she doesn’t really need to know

Dear Microsoft: I don't care if Edge or any other of your in-house developed software is faster than the alternatives, it's about quality not speed.

If you design quality products people will use them, just because they are "faster" doesn't mean shit.

There are all these bad design ideas out there, like 20 popups on websites, facebook, apple software.

I only see good programmers who have self respect here. So what good programmer doesn't have self respect and programs those bad ideas?

(I'm just fucking with the apple guys, but the other two are legit)

I just hate writing comments and the Software Design Document for the code and changes done my me.

"Learn coding to make more money" ads are the funniest things ever. Like some underskilled graphic designer must've sat with his shitty laptop to design on a pirated software for a meagre wage, a poster that talked about how to earn more money.

Teach students the importance of clean code/architecture and testing. Even if they dont yet understand the more complex topics such as architecture, they should understand why quality is important and that software is a craft more than a science. You cant just apply principle X and insert design pattern Y and profit++. You actually have to think and constantly improve. AND TEST.
Think I would probably also cover things like build automation and continuous delivery. These are now important things for junior devs to know about going into companies.

So we finished our requirement ( barely) for a new client. Next is data modelling and system design.

We started with data modelling. Unfortunately the lead developer does not know the difference between database and data modelling.

me: hey bro, we'll do the database and stuff later, now let's focus on data modelling.

him: (acting like he knows) yeah I have developed a sample design for the "data model".

me: no this is database design.

him: what's the difference?

me: dude, they're totally different. Okay, simple explanation data model is what you want to store, whereas DB design is how you store it.

him: So, if I am not wrong, it's implied that you know what to store if you are talking about how to store it.

me: but you don't know what it is you want to store yet. And one of them precedes the other.

him: Okay, let's start with DB design.

me: What?????? you want to build a house without a plan??? That's it for me I am done !!!

I left the project yesterday, later I heard that, the team members are coders, who think that developing a software is all about coding and fixing errors.

Anyone in here have experience with UML in the real entreprise world?

As a student I've learned a lot about documentation and software architectural design, I've worked 3 different places and worked with customers that were developers and all of them seemed to not really do architecture and documentation that well. Personally I find having an overview/guideline for bigger project really helpful

how come you don't see better software documentation and UML out there?

Maybe I just haven't found the right place yet

happy rant 😄
just finished our group software project in uni (5 students, a way too complicated game) and just got the highest possible mark of all!!🤩🤩🤩
the project was focused on having a working, bug-free game, so yeah our game was UGLY AS FUCK😅 ... but 99% no bugs😎
best group in years😇
next chapter:
human-computer-interaction(is that the translation for Mensch-Computer-Interaktion?), we'll take our games and bitch about their usability and design😅
by the way i was responsible for the design/ux and did a kinda crap job because of too little time😐😅

so my friend and I are canvassing NLEs for our guys at the Post Production squad in our project (we were in charge in infrastructure). We looked at Premiere since it's kinda ok until we found Black Magic Design's Da Vinci Resolve.

First of all, I was suprised with the price. 299 for the Studio Version? Holy fuck, that's cheap as hell! Then there's a free as in free software version which has the core editing features with 1080p rendering. So we grabbed that and kinda suprised it requires postgres but as seeing Resolve having collab and render queues, it makes sense.

Installed them on the PCs the postprods gonna use, they were amazed. We literally saved 500 bucks for an NLE. When they asked how much is it. Our reply was:

"That's free".

and there was silence...

"And it's also 299 bucks for the cooler version".

And silence still ensued.

Guess our guys wasted alot of money on a pipeline that is cheap as hell but more jam-packed than any other NLE found in the market.

Props to you BlackMagic Design.

Hey Linux users!

I have successfully convinced a friend to change from MacOS to a Linux based system (because she needs new hardware).
Now I am asking myself which distribution would be most qualified for her. She is a relatively old lady and only knows Mac (no Windows or Linux knowledge), so it should be easier for her if the new system would look similar to the Mac environment she knows. (Using console is no problem.)
Another point is compatibility: She needs some (commercial) software (like GitKraken and design stuff), so it would be cool if the Linux versions of them would work on the distro (for one or two programmes Wine is needed).
After my own reasearch I came up with Elementary OS or Gmac.
Because I have no experience with Mac I want to ask you: Has anyone here some experiences with these two systems and/or with a change from Mac to Linux and could recommand a distribution or desktop environment?

Thank you!

What's your opinion about Dreamweaver? I haven't seen any web devs talking about it in all of the space of programming community. Is this because it's a software more focused on design itself or have some special motive either?

Hey DevRant!

Not really a rant but a question:
I just got accepted into a coding bootcamp. Have any of you been involved in one? How was it? What would you do to make it a better experience throughout? Any advice or suggestions?

It's full time, six months long and I start in October and I want to make sure I make the most of the experience and absorb as much as possible.

I'm super happy that the course appears to be less just learning JavaScript and more involved in the Computer Science side of things, even including bits about C/C++, distributed systems, algorithms and data structures, software design/testing, cryptography, database management, and computer architecture. It also, of course, covers tons of resume work, interview practice, and networking.

Thanks!

So I've been a professional software developer in variously named roles over the years since I was 18, now 35. I've had many ideas for my own projects over the years some great, some not so great, and as with most ideas, if you don't act on them, someone else will suddenly come up with it, which is frustrating as hell obviously. Anyway, I never find enough time to do these things in what little free time I have, so the idea of stopping working for someone else and work on my own stuff seems almost unobtainable. I've worked with companies (startups) that have had ideas that have never made anything significant but still keep going on investor money for some reason or another. I realise my question is quite vague, but how the fuck do you break away and do your own stuff? Time is running out (at least in my mind), anyone here actually done it, succeeded, failed?? Can't be writing other people's badly designed software my whole life, would be nice to design my own and see it through.

As a Software Design junky, I just enjoy using TypeScript for more conventional C-style programming structures in JavaScript !

My family had a very good understanding of what I'm doing.

My dad is working at a big software company as project manager (he himself did code years ago, but it's actually a physicist).

My mum is a language teacher, but has taught herself web design while she wasn't working in her job (taking care of us kids) and was working as self employed web designer from home for some years.

My youngest brother is studying business informatics.

My other brother is not studying anything technical, but very open minded towards these topics and has good knowledge about it.

My grandparents believe what I told them: "I (read as: software developers) create everything that happens in your computer after you've turned it on."

When I was in school days I didnt like computers that much. I knew how to use them but thought classes were lame.

It was a couple of years ago, in the last year of my first computers-related career (here there's no computer science like in USA). It was in the initial stages of my graduation project and our teacher took a look at our database design, fixed it all. And explained:

"The better you designed your database, the easier it'll be to code the project" Explained to us the importance of database normalization and all that.

I really understood it all and discovered finally what was the thing I was studying and how to do software.

From that day, in my early 20s, I've been loving software and knew this is my thing.

Same feeling 6 years later.

I design 3D CAD models in my office system. I need to keep saving the files every few minutes because software licenses are floating and once lost, I may lose data.
But another bigger problem is that we need to disable proxy to connect to VPN and work online. And the proxy always turns itself ON, every few minutes and if by chance you saved the file without turning the proxy OFF. Well then OFF goes all the work since you last saved. Because then CREO just stops responding.

Friday wisdom.

Software is not written. It is rewritten.

After spending 3 days approx. On thinking over a design problem. The first 2 days I was clueless how the problem is going ahead. Today I deleted all classes started again and voila.!! It works like magic and I did it with a TDD approach so got good test coverages too.

P.S. I didn't come up with that line. I got it from a tech talk and now understood it's meaning.

Had a course in software architecture. Our final project was to fully design a program with microservices. No explanation was given on technologies, tools or even the specific logic. We had a total of like 5 "lectures" and only one or two of them were about microservices. Also the guy didn't reply to emails and our questions remained largely unanswered.

We had 4 weeks for the job, and together with massive homework amounts and other projects we wrote a website in MVC which is, apparently, not designed in MSs. Also all the papers we had to provide with it (full design, UML diagrams and system analysis) were as clear as a fucking swamp. And the "lector" had a metric fuckton of issues with it when we presented it.

I fucking hate this course and this college.

TL;DR: Have you ever been on a serious company where you have to DRAW a high fidelity mockup of the software in the design phase?

So I'm in my last year of college and I have a class called Interactive systems design, which is basically about usability and how to design the frontend of your app so it's intuitive, pretty and easy to use.

So we work in groups to design a project for the entire semester, following a long and tedious process of research and planning which includes writing absurdly long documents, doing interviews with potential users and more.
Now that we've done all of that, the teacher insists that we make paper mockups of our app before we do a digital one using Balsamiq or other programs. He wants the paper mockups to be "interactive", so we have to draw them and then record a video where someone "clicks" on the mockup with their fingers and another person moves the papers around to make it look like an actual app that's doing something.

The teacher still insists this is something almost every company does when designing a project, so it's very important that we learn to do this kind of stuff. He's kidding, right? Have you guys ever drawn a mockup of an app instead of using some mockup software?

!rant
TL;DR: Can anyone recommend or point at any resources which deal with best practices and software design for non-beginners?

I started out as a self-taught programmer 7 years ago when I was 15, now I'm computer science student at a university.
I'd consider myself pretty experienced when it comes to designing software as I already made lots of projects, from small things which can be done in a week, to a project which i worked on for more than a year. I don't have any problems with coming up with concepts for complex things. To give you an example I recently wrote a cache system for an android app I'm working on in my free time which can cache everything from REST responses to images on persistent storage combined with a memcache for even faster access to often accessed stuff all in a heavily multithreaded environment. I'd consider the system as solid. It uses a request pattern where everthing which needs to be done is represented by a CacheTask object which can be commited and all responses are packed into CacheResponse objects.

Now that you know what i mean by "non-beginner" lets get on to the problem:

In the last weeks I developed the feeling that I need to learn more. I need to learn more about designing and creating solid systems. The design phase is the most important part during development and I want to get it right for a lot bigger systems.
I already read a lot how other big systems are designed (android activity system and other things with the same scope) but I feel like I need to read something which deals with these things in a more general way.

Do you guys have any recommended readings on software design and best practices?

Product presentation for a new module in our software suit in 5 hours.
And just now I got an email from my boss, asking if I could add the gui revamp we were planning for next version today...for the presentation...it's just a UI after all.

But yes of course, obviously I do magic and can design, implement and test a new UI from the ground...in less than 3 hours. Because we have to leave early.

Sometimes...

You have to love systems people who tell software people how the software works. Especially when you are trying to tell them why a problem is occurring in the software. Like software guy is like:

"this is breaking because a number is getting overwritten in the system by a product we interface with and have no control over"

"Well you need to stop the number from getting overwritten"

"then we're going to have to overhaul the design of the system"

"you don't have to redesign the system, you just need to circumvent the product that is overwriting the number"

"Yeah, a design change."

Dude is the interim system lead and starting to get uppity. Even though it's his group that is behind which is why we are driving changes to the system rather than them.

Why does nobody publish the software design in Github when publishing the code?

I know that theoretically there's no reason, and most have a good read me.md but why not publish the design?

Recently talked with someone who would like to design with FOSS tools like Krita, Gimp and Inkscape instead of the Adobe toolbox.

Made me asking the question how many companies are around that support this way of working. Companies that believe that using open source or even better free software is a core qualification for their employees and one of their core values.

Because many companies support open source but don't make it a requirement and focus so much on it. Even companies that produce free software :/

I've been lurking here for a little while now and I thought I'd post my first rant.

I'm an intern at a software development company and I have to design an application for the company, that will only be used in the company.
Both my frontend and backend are coming along decently, but still being new to the whole development scene, I didn't gather enough user stories from my colleagues.
So normally everybody is working hard, but has time. But the exact day I planned to gather some more user stories everybody is as busy as could possibly be.
Now I'm sitting here thinking what to do. My brain trembles from it and if I get can't get an idea of what to do soon, I'll feel truly slothfull.

I know my problem is far from horrible, when compared to some of the rants I've read here. But I really have no idea what I should do at the moment.

Oh, and if you got the two references I did to a certain series, you have suffered.

Question: is it common for lead software engineers to mostly do paperwork or is that just a quick of my current program?

Where I work it is very common for those titled "software leads" to be almost completely hands off the software. They deal in hiring, fielding user comments and commitments, and scheduling. I would like to be a lead but I was always under the assumption that dev leads had more of a design and/or architect role. Sort of a big picture thing rather than middle management which is what this feels like.

Was watching the Google live event. Must confess that I'm highly disappointed with the looks of the Pixel 2 . I guess 2017 is just not the year for Google! I mean I love the software improvements but let's admit it that inspite of us being software devs , we ourselves love good design! The pixel 2 just does not make the cut according to me. It looks like a brick. Google does need some hardware devs!

Systems guy: this is how you slow down development projects. By tying design to a software development ticket.
Software guy: yeah but that's how you get reminded to do the work and tie a design requirement to the software development effort in the ticket.
Systems: why do I need to be reminded of my design work?
Me: because you're a year behind software and at this point you are just documenting what software has already done?

Sometimes I feel like the design guys don't understand that if they want to be involved in the process they need to NOT keep us waiting until right up against the deadline to give us the design.

What tool do you guys use for the Ui/UX design , the mockup? Is it there any free good software

Ctrl+X followed by Ctrl+C to quit. Let that sink in. Think about :wq. Think about Ctrl+X. Think. Ask yourself how you think about it and then think again.

And if you say "well it's AWESOME" then start using your clipboard more when using a gui around the terminal or ssh and come back 1 month later.

People say vi is counter intuitive.. what the fuck is emacs then?

Big up front design with no requirements, waterfall methodology a distributed team around EU. Falling always behind schedule, software is bad, but everything is going OK

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

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

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

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

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

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

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

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

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

Story of my life - Feature creep, creeping featurism or featuritis is the ongoing expansion or addition of new features in a product, such as in computer software. These extra features go beyond the basic function of the product and can result in software bloat and over-complication rather than simple design.

What architecture or design principle related books would you recommend? Something like the gang of four's book. I have read that. What other great books are there?

Outlook warms me when opening excel attachments that it might contain viruses (PROTECTED VIEW).Ooooh fancy....
Only problem is that it's in Sent Items and if it had a virus I'm already f...ed

*phases of learning to program*

Phase 1:
Yeah its so easy i love programming i'm gonna be a top programmer.

Phase 2:
Uuuhg.. programming sucks,i think i'm not meant for it,should i give up do something else maybe...

#programming #100DaysOfCode #mumbai #love #indian #gujarati #vadodarabarodacity #instagram #vadodaradiary #msubaroda #aapduvadodara #vadodaranews #vadodarawomen #officialvadodara #vadodaracity #barodarocks #barodagoogle #vadodarafashion #vadodara_lover #barodadiaries #barodamirror #india #vadodarabaroda #geek #developerslife #webdev #php #design #css #java #developers #html #softwarehouse #softwares #softwaredevelopment #technology #coderlife #designer #softwareengineer #webdesigner #codingisfun #programmerproblems #programmerjokes #programmerlifestyle #programmergirl #webdevelopment #developerlife #devlife #webdesign #programmersday #softwareengineering #programmering #programmerhumor #development #dev #programmerlife #programmer #developer #vadodara #coding #software #baroda #programming #vadodaradiaries #vadodara_baroda #coder #webdeveloper #gujarat #programmerslife #javascript #vadodara_igers #codinglife #barodacity #code #vadodarablogger #programmers #softwaredeveloper #ourvadodara #goals #beyourself #happy #smile #lifeisgood #socialmedia #success #friday

Pick up and learn new tech like SignalR and Vue and many more while also focusing on design patterns and software architecture.

Get myself another promotion so I can afford more shit.

Learn rock climbing, get into boxing, and do a first aid course.

Yeah, I'm gonna be busy as hell this year.

Half of the courses we had in our college were about electronics. Except Microprocessors and Transistors, it's not relevant.
We even had chemistry and engineering drawing. So we essentially wasted more than half of our time.

Besides languages, weren't taught anything about real world software development.

Nothing about how to work with an existing code base, version control, design patterns, system design, creating a website, debugging, functional programming, scalability, reliability.

The industry should be involved in setting the syllabus and also contributing part time teachers.

I graduated college with double degrees in literature and marketing management. Web and software development and design was a hobby that became my way of life and eventual career path. I guess it's more of a challenge than a hurdle, not having a formal IT education as a foundation, but I'm happy to have learned a lot from my colleagues over the years to better myself as a dev in practice, if not in academics.

Hardware classes for software dev student?

Hey guys. Currently getting into second year of a 5 year curriculum to get an 'Integrated Master of Computer Engineering & Informatics' Degree here in Greece.

I'm already into software, I'm fooling around with java, go and php, making some games, web services and anything I find interesting in general. Recently, with the logic design class, I started liking hardware stuff (I didn't really like them before).

We're getting to a point where we might have to decide between picking hardware-centered or software centered subjects. I'm thinking that I can probably learn whatever is taught on the software side by myself (with a bit more studying of course), whereas hardware would be more difficult to study alone.

That said, I'm considering picking hardware, but I am skeptical. What do you think? I'll certainly miss out on the concurrent processing, data structure and how-a-compiler-works classes.

What do you think?

P.S. University here is free

Design patterns a solution to a problem, not a solution for the sake of a solution.

It comes from years of developers banging their head agains a problem and iterating a solution. It was not done person sitting down and thinking about rules for good (general) software development.

Thoughts on significance of Software Requirement Specification and Software Design Specification document in the industry?
Coming from a student struggling to understand the importance of it.

I'm beginning to design websites using WordPress. The issue is, every client wants their website to be styled differently. ive looked into creating my own themes, but a new theme for each client is just unrealistic.

Somebody pointed me towards dopewp.com, which is a Bootstrap based theme with a page builder. I've settled for the idea that I need one theme that'll do the job everywhere, but there's more questions past that.

should I develop my own Bootstrap theme, or use freemium software (which I hate) like dopewp? another option would be to build my own Bootstrap theme, or a completely new Bootstrap CMS.

I just don't know...

Oh my gosh, no one really knows here what is programming. Even teachers, which claim to be professionals in the subject doesn't know shit except for the basic theory. Nothing in practice.

It was evidenced by the largest job skill competition of Finland (Taitaja) that's for my-aged students (18). And yeah it's not higher education studies, just second degree, but that's where you should get the necessary practical skills for your work life.

The category I participated was website development, which is the only software development category.

It was a public event that is focused on showcasing different jobs. Well, what do programmers do, a viewer may ask. Even the responsible teachers and juries couldn't really answer properly. They just showed the specs we were following to create the crappiest of websites the short period of development time.

So we consume coffee and produce HTML, is that accurate representation of the whole industry?

All the other winners of different categories get a lot of job offers from companies when they win. I won gold last year (bronze this year) and I didn't get a single offer. Who would be interested in human HTML generator who can only make static websites anyway?

Programming is about problem-solving, not about graphic design and writing content.

And just to give you an idea the scale of the competition: last year I made a total of ~2000€ for the victory. And it is super easy if you just know what you are doing. That being graphic design and the making of a static page with a pinch of functionality.

Monday.
Hungover after birthday.
Software Design Lecture.
Lecturer has an accent, grammar mistakes and a Sonic the Hedgehog voice..
And she said Java numerous times.
I love Mondays..
😂 🔫 😭

Presented SDD and it turned out be amazingly screwed

I've noticed from the many pics of workspaces that software guys tend to be neat, tidy and ordered. The mechanical design engineers at work are messy

Ok so guys, I really love back-end, but sometimes I'd like to do a complete software to show off to friends in my free time, So question:

What programming language should I learn to make gui softwares?

I don’t want them to be pieces of art, just functional and with not too man " unintentional features".

I really love Python, but for gui heard it's meh, but may be wrong

I don't want web technologies

looking forward to learning C, but not necessarily for gui
could try c++ I guess

Don’t want .net (coz you know ms and their Java knockoff)

Ruby seems cool, but it seems to be annihilated by ruby on rails

Not Java but Kotlin seems really cool, could also go with scala, idk

Forgot the other things

A space game (obviously) where ships are built and broken in convex pieces. With in-game computers and ship design/construction software, of course. Because what would a game engine be without the ability to play a game within the game, with exactly the same visual quality as in the outer one?

Edit: Game-within-game premise based on the idea that it will be easier to write the ship-CAD software in a game engine than from scratch

Edit 2: may as well also be able to play the actual game within itself, since it would be like holodeck simulations

I have no specific story to tell (for now. Will post ke if i remember one) but i have had tons of CS teachers that are shit. From ones who don't know shit to ones who are so bad as a human being i am sure thrte are hundreds of people out there to kill them. I have had multiple teachers where all they did was read out a book and we'd have o site everything they read. Whole fucking semester. And not just one person or once. M-U-L-T-I-P-L-E TIMES AND TEACHERS. then I ve had ones who would rejection my code even if it's better, is right, can andle more edge cases, most likely magnitfrs of times faster and isn an eye sore with just effig if-else on op of if-else nested within if-else with many for loops. Then there are those who want you to do just what they want and expect you to not have a life of your own. Those who blatantly abuse their powers. Those who couldn't care less. Those who are not that bad a teacher but their attitude and style just makes you want to leave. There's one currently who wants a group of 4 people in second year to develop a full blown industry level application in mere 3 weeks. AND WE ARE HAVING OUR THEORY PAPRRS INBETWEEN FOR 2 EFFING WEEKS. So that's just like a month. Fortunately I have a group that's good enough that I can have them do the testing and filling up the documentation​ (did I mention that he needs full documentatiin for software plus a report on how our development process) and have them work on presentation (yup. We need to present this thing) all for just 50 marks. 1 uni credit. Our system still gives 80% weightage to pure theory. Plus the practical part is somewhat theory too.

Our HOD wants us *insists*forces** to stay back at college and work on projects (which is nice but what he ments is use the shitty outdated books from early 2000s to study something). Now I'd be happy to stay back if college provided decent internet (I am not asking for gigabit speeds. Even 1-2Mbps would work) and place to sit. But nope, our college non-teaching staff is eager to send us out of their department and by extention college building. There is literally nowhere you can sit. Plus yup, there is no internet and nowhere for you to plug your laptop in. That's a moot point anyway because they don't want you to use your laptop in college library or anywhere anyways. Plus you don't get much of mobile data too because of the building design. Those work only near windows. Why would I be at college if I can get a 50+Mbps down, area to sit, snacks, port to charge all at home. And you'd say we should talk with him about this – well it's not his issue is all he has to say.

Well, such is life in Indian colleges. And my college/uni is one of the better ones.

i just learnt how much clearcase sucks the hard way. i always used git for personal projects and am used to finding a simple solution to any problem at most one stackoverflow away, i just messed up my local repo, and experienced people could not manage to undo it. i mean come on, this is a f**king versioning software, how hard can it be to delete everything local and re-pull from remote without messing up configuration files? either clearcase has some serious design shortcomings for my understanding of a versioning software, or it is so overly complicated that nobody actually knows how to revert this mistake.

some questioned my software design techniques after putting ID as ma last attribute.... then I asked him to check if it's not working... he didn't give me feedback.

In high school I had a digital media class, where we mostly learned Adobe design software and video editing and whatnot, but one project was to actually code using Programming (the software) and I loved it. Later that year I used a free project in the class to learn arduino per my teachers recommendation. Absolutely loved every second of that project, and have been coding ever since.

And why is symfony so fucking slow? Well I guess it has something to do with depending on code annotations for everything, or every simple task requiring a whole cloud of a thousand classes, stupid design decisions....I fucking hate symfony, piece of shit software

!rant
Does anyone know a good (and possibly free) mockup software mostly for web design (desktop would be nice too).

Had my first lab for software development today, something I was looking forward to as a non CS student.

The class is using MATLAB/Simulink to generate code for us because it is important to learn "model based design"

Found out the enterprise app for which I am writing Python code is interpreting it through asteval. Which means no more classes, no imports, no decorators, limited built-ins, and limited code testing strategies. 😰

Burn my own harvest? Don't mind if I do! Goodbye code which wasn't half bad. The thing which comes to replace you will be written of in horror stories.. 👾

On the flip side, a new software design challenge! 😅

I have actually two, but I'll write the other one in the week.

So we had classes about software engineering. The class was interesting but the teacher wasn't. Too soft, too slow, too low, too monochord (usual french), it was boring. So we ended up not listening to him. Kinda regret this.

We got a first exam, where we were in group to develop a Test Manager for Unit Test (yep.)
We had instructions, like the note would be multiplied by the percentage of coverage of code, etc.

The thing is, we really didn't get the point of the project. Now that I think of it, it seems obvious, but it wasn't back then as it was too new. In the four people of our group, one worked real hard on it, I tried to do my best, the others too.

But like I said, I didn't get back then the point of the topic, which is to apply design pattern, unit testing, etc. It was furstating af and we ended up with a 9/20.

I got the point of the topic only for the second exam, the most classic one, on a paper sheet with questions to answer. (We were allowed only one cheatsheet, I understood the topic while doing it. Sad, huh ?)