So i was playing around with terminal apps in node.js a few weeks ago and made a CLI version of devrant. Images get converted to ascii just for fun. This is about was far as it goes for me though - anyone want to take it over? (The code is shit - this was a midnight proof of concept). Currently there's pretty much just the rant listings, the login works too but I think @dfox would need to approve it's use.

Next script I'm writing is going to be a terminal rant posting tool so I can rant from my server 😉

$ rant -m "fml" -f ~/screenshot.jpg -t "lol"

Boss: make this thing
Me: yeah no worries. Where is the spec?
Boss: We don't have enough one but we outsourced the design so call him

Designer: haven't started yet
Me: excellent

Boss: I'm going on holiday. I'll leave this to you.
Me: erm ok. I'm having a few problems getting stuff out of the designer though.

*2 weeks later and still no designs*

Boss: I'm back. Where is the progress?!
Me: indeed.

*1 week later i get half designs that sort of make sense*

Boss: hurry up!

*1 week later*

Me: designer you're busting my balls here
Designer: yeah lol

Me to boss: still having problems. No idea what I'm doing.
Boss: deal with it

*2 days later*
PM: we are demoing it to clients tomorrow
Me: brilliant. I'll become a magician then.

* Meeting goes well and no one notices the thing is a bit buggy*

*2 days later*
Me to boss and pm: you already know whats going on but I'll keep trying.
Boss: ok it's just a proof of concept anyway.
Designer: yeah here's the rest of the designs lol

*1 week later, the designs made no sense, no idea what they wanted but hey it's a proof of concept so I'll just do my best...*

*suddenly again, hey you have 1 week before we sell it. Lol. smashes a product together as fast as humanly possible, due to half designs and no time to do it right even html classes and CSS aren't right - didn't know things would be repeated at the time. No time to fix entire thing. Luckily just a proof of concept*

New senior developer: hey boss just said this is being sold tomorrow.
Me: wtf..It's a proof of concept and i was given longer...
New senior developer: no
Me: :(

Senior developer and all colleagues: it's full of bugs and doesn't work
Me: yes that will happen without specs, random tight deadlines, no designs that made sense and a total of about a week and a half to make an entire system for multiple user types to make applications, send messages, post jobs, handle all paperwork and move paperwork among different user types as they go through applications. I told everyone what was going on but i get no support...

*Silence*

Boss: wtf i gave you so long! All i know is my entire staff is working on a product that should be done ages ago
Me: ok, however i have said almost every day i need-
Boss: I'm not interested

*I finish my placement year and never get any promised work or the job offer*

Seems legit?

Every goddamn time.

Boss: Hey, how is the project going?
Me: promising. We have some basic functions working, but at this point it is more like a proof of concept.
Boss: Ah ok, I see.

Couple of days later...

Boss: I talked to a client who was very interested in the stuff you are just building. Made a really good deal! We need to be live by the end of the week.
Me: What?
Boss: What?

God damn it, i said so many times that this functionality is proof of concept and needs more investigation into technical/legal details...why the flugzeug mr account manager have you gone and emailed all your client accounts telling them we are now offering it?... why are you messaging me starting your sentence with "now that we provide..." god...damn...it

Client: "We want you to build us a quick prototype / proof of concept. Don't make it too neat, we'll rebuild it before we go live."
Also client: "We already have a working version, why would we rebuild it?"

Product team having a proof of concept demo with client:

Sales to client: "Just for the record, we are not selling this to a rival company. Because we really want this technology exclusive to you"

Me (thinking to myself): "Oh really? We just had a demo with them last 2 weeks"

One of the core values of our company is Integrity, and I am not just seeing it.

When your company hires a third party to develop 2.0 version of your product after doing a proof of concept... Fml

A few years i had wrote a little script as a proof of concept for remote injection via torrent files.

Yesterday, some doofus bruteforced into my seedbox and tried to install a miner using the same script🤦🤦🤦

Did some digging, found my way back to him and wiped the drives on his system as a gesture of thank you. Anyways, I hope he didn't have anything important on his 16TB volume, cause good luck recovering that

Friend of mine: so I wonder how do you test your applications in the startup?

Me: testing? *grabs his coffee laughing*

Actually we have a complete build pipeline from commit/pull-request to dev and production environments. No tests. Really. We are in rapid product development / research state.

We change technologies and approaches like our underwear (and yeah, this is frequently). If we settled some day and understood the basic problems of the whole feature palette, we'll talk about tests again.

Today's project was answering the question: "Can I update tables in a Microsoft Word document programmatically?"

(spoiler: YES)

My coworker got the ball rolling by showing that the docx file is just a zip archive with a bunch of XML in it.

The thing I needed to update were a pair of tables. Not knowing anything about Word's XML schema, I investigated things like:
- what tag is the table declared with?
- is the table paginated within the table?
- where is the cell background color specified?

Fortunately this wasn't too cumbersome.

For the data, CSV was the obvious choice. And I quickly confirmed that I could use OpenCSV easily within gradle.

The Word XML segments were far too verbose to put into constants, so I made a series of templates with tokens to use for replacement.

In creating the templates, I had to analyze the word xml to see what changed between cells (thankfully, very little). This then informed the design of the CSV parsing loops to make sure the dynamic stuff got injected properly.

I got my proof of concept working in less than a day. Have some more polishing to do, but I'm pretty happy with the initial results!

!rant
The more I learn about advanced C++ the more I love this language. C++'s template system is so insanely cool!
Just made a proof of concept expression templates based linear algebra library for my own projects. It was actually a lot of fun to make, and seeing it spit out optimized, loop-fused code with no temporary variables...magic.
Long live C++.

Anyone else suffer from this.

Have a brilliant idea, start computer, open you IDE, write a few lines of code as proof of concept and then just loose interests coz it's no longer a challenge !

I work in a fintech company and our product is a point of sale app. Two senior indian dev contractors just spent 3.5 months on a feature where all they had to do was map two tables by using a third mapper table and display 2 lists to the user so he could update the data in those two tables.

After hearing same excuses (that they are working in it) for the past few weeks, I took it upon myself and made a proof of concept for them.

Yeah our codebase is kinda shit but even me, a fcking junior with 3 years of experience managed to do it in 1 week.

Meanwhile these fuckers spent 14 weeks beating around the bush and couldnt even save data to a fucking database. They just added UI and thats it. When asked how investigation is going fuckers couldnt even come up with any findings. For weeks. Seniors my fucking ass.

If not for me, I guess they would have taken till the end of the year. No, fuck you, here is an example now pickup your slack.

Im tired of picking after you. God damn incompetent leeches

I've been working on a proof of concept for my thesis for a few days and the async query calls drove me nuts for quite a while. I finally managed to deliver all query results asynchronously while still very much relying on a strong architectural design pattern. I am filled with caffeine, joy and a sense of pride and accomplishment.

I'ma done did a POC today, arr!

I used to work IT in an entertainment startup, and now I’m an iOS dev at a big entertainment company. Several people from my old company have been reaching out to eagerly tell me about their new app idea I just have to hear, asking me to help code their app— and have even hinted at me quitting my nice safe job to join their great new startup that doesn’t even exist yet.

I know this must happen to app devs all the time. What do you say?

How do you deal with telling these nice people who just don’t understand it doesn’t work that way, without crushing their dream? I have a coffee meeting planned to tell one of them “You should learn to code so you can make a proof of concept,” but I fear that won’t be received well.

What’s the standard protocol for telling people you won’t be able to code their magic app idea?

Some non-IT people wrote a crappy software tool. Others have started using it for business critical processes.

Asshats: "People are starting to use our tool and that means it's production ready!"

Me: "If and when this breaks are they going to call you to fix it?"

Asshats: "Well it's really just a proof of concept."

They want the glory but not the work that goes with it. And they dont want anyone else to develop it. They have been a huge pain for me lately.

So I've started learning Rust and I must say it feels great! But some parts of the language, like enums, are quite different than what I'm used to.
As a proof of concept I've reimplemented a small API (an Azure Function App) in Rust with Actix Web and it's FAST AS FUCK BOIII.
The response is served about 5x as quckly and the memory footprint shrinked from some 90 MB to around 5 MB.
In my small scale usecase it's not a huge difference, but I think it can be massive at large scales...
What is your experience with Rust (at scale)?

I wish I could quickly reimplement the whole fucking CMS Of Doom™ in Rust... but no time and resources :(

My story about ego boost was when client came one day that they want some system that was prommised to him but guy who promissed him it forgotten about it.

Well, i quickly estimated things in head (i wasnt on meeting, was next to this room so i heared whats up), i pulled out my boss from meeting ("hey i need you urgently for sth") told him that i can make proof of concept to show him for next day (it was +-15) and sure enough, next day 10:00 first version that worked but was kindda rough around edges and with TON of technical debt was created. Than I told client that I just need a little bit more time to work on this as he can see it is here, it works, and it does what he needs, but it would be good to add some polish to it.

He bought my version and i saved company a client, that was lost becose some moron forgotten about him hah

Oh, yes, i got all i needed in return, day off and some extra $$

Has anyone installed Elasticsearch on Linux - centos to be specific.

Trying to workout why the fucker won't install. Setting up a proof of concept so don't want to use it currently as SaaS.

From why I can tell, it only needs Java, (check) and to be ran as a user other then root (check) but running ./bin/Elasticsearch hangs after a while and starts powering up 100 odd threads with no progress.

Customer: as soon as you get a proof of concept could you send it to me?

Me: sure *sends app to test* here is what it currently does and does not do.

Customer: thanks, here is a list of 59284 things that dont work or need changed.

No shit sherlock. It's not done, you wanted a very early version, and of the things you listed I already mentioned half of those.

I've learned over the years that there's no such thing as a Proof of Concept app. You might as well call them beta versions since some salesperson or manager will see it and immediately tell clients about it who will buy it and then you have to support and expand it.

"One misstep from developers at Starbucks left exposed an API key that could be used by an attacker to access internal systems and manipulate the list of authorized users," according to the report of Bleeping Computer.

Vulnerability hunter Vinoth Kumar reported and later Starbucks responded it as "significant information disclosure" and qualified for a bug bounty. Along with identifying the GitHub repository and specifying the file hosting the API key, Kumar also provided proof-of-concept (PoC) code demonstrating what an attacker could do with the key. Apart from listing systems and users, adversaries could also take control of the Amazon Web Services (AWS) account, execute commands on systems and add or remove users with access to the internal systems.

The company paid Kumar a $4,000 bounty for the disclosure, which is the maximum reward for critical vulnerabilities.

In my short career, I've seen projects become legacy before their first release. Hell, I've seen proof-of-concept apps turn into technical debt because to management as long as it works we won't rewrite it.

TL;DR:
JuniorDev ignores every advice, writes bad code and complains about other people not working because he does not see their result because he looks at the wrong places.

Okay, so I am really fed up right now.
We have this Junior Dev, who is now with us for circa 8 months, so ca. a year less than me. Our first job for both of us.
He is mostly doing stuff nobody in the team cares about because he is doing his own projects.

But now there's a project where we need to work with him. He got a small part and did implement that. Then parts of the main project got changed and he included stuff which was not there anymore. It was like this for weeks until someone needed to tell him to fix it.
His code is a huge mess (confirmed by senior dev and all the other people working at the project).

Another colleague and me mostly did (mostly) pair programming the past 1-2 weeks because we were fixing and improving (adding functionality) libraries which we are going to use in the project. Furthermore we discussed the overall structure and each of us built some proof-of-concept applications to check if some techniques would work like we planned it.
So in short: We did a lot of preparation to have the project cleaner and faster done in the next few weeks/months and to have our code base updated for the future. Plus there were a few things about technical problems which we need to solve which was already done in that time.
Side note: All of this was done not in the repository of the main project but of side projects, test projects and libraries.

Now it seems that this idiot complained at another coworker (in our team but another project) that we were sitting there for 2 weeks, just talking and that we made no progress in the project as we did not really commit much to the repository.
Side note: My colleague and me are talking in another language when working together and nobody else joins, as we have the same mother tongue, but we switch to the team language as soon as somebody joins, so that other colleague did not even know what we were talking about the whole day.

So, we are nearly the same level experience wise (the other colleague I work with has just one year more professional experience than me) and his work is confirmed to be a mess, ugly and totally bad structured, also not documented. Whereas our code is, at least most of it, there is always space for improvement, clean, readable and re-useable (confirmed by senior and other team members as well).
And this idiot who could implement his (far smaller part) so fast because he does not care about structure or any style convention, pattern or anything complains about us not doing our work.

I just hope, that after this project, I don't have to work with him again soon.
He is also one of those people who think that they know everything because he studied computer science (as everybody in the team, by the way). So he listens to nothing anybody explains to him, not even the senior. You have to explain everything multiple times (which is fine in general) and at some points he just says that he understood, although you can clearly see that he didn't really understand but just wants to go on coding his stuff.
So you explain him stuff and also explain why something does not work or is not a good thing, he just says "yes, okay", changes something completely different and moves on like he used to.

How do you cope with something like this?

I built a basic MVP for a client as a proof of concept for his startup. It was a quick thing just to prove a point do I rattled it out in procedural php.

Sadly it was successful and has somewhat taken off. It’s also grown arms and legs.

It works. The user will never know, but the code is SHIT. I never thought it would still be here.

I’m want to re-write it now in laravel.

But...... ugh

If I had to audit my current code I'd definitly stick a cactus up my arse shouting in the mirror:

ALL YOUR CODE IS GOOD FOR IS ULTIMATE DELETION. YOU FILTHY MAGGOT! LEARN TO CODE... *rage quit*

Really, coding shit because of spare time simply makes me ripping my face of 💀

Most successful? Well, this one kinda is...

So I just started working at the company and my manager has a project for me. There are almost no requirements except:
- I want a wireless device that I can put in a box
- I want to be able to know where that device is with enough accuracy to be able to determine in which box the device was put in if multiple boxes were standing together

So, I had to make a real time localization system. RTLS.
A solo project.

Ok, first a lot of experiments. What will the localization technique be? Which radio are we going to use?
How will the communication be structured?

After about two months I had tested a lot, but hadn't found THE solution. So I convinced my manager to try out UWB radio with Time Difference Of Arrival as localization technique. This couldn't be thrown together quickly because it needed more setup.

Two months later I had a working proof of concept. It had a lot of problems because we needed to distribute a clock signal because the radio listeners needed to be sub-nanosecond synchronous to achieve the accuracy my manager wanted. That clock signal wasn't great we later found out.

The results were good enough to continue to work on a prototype.
This time all wired communication would be over ethernet and we'd use PTP to synchronize the time.

Lockdown started.

There was a lot of trouble with getting the radio chip to work on the prototype, ethernet was tricky and the PTP turned out to be not accurate enough. A lot of dev work went into getting everything right.

A year and 5 hardware revisions later I had something that worked pretty well!
All time synchronization was done hybridly on the anchors and server where the best path to the time master was dynamically found.

Everything was synchronized to the subnanosecond. In my bedroom where I had my test setup I achieved an accuracy of about 30cm in 3d. This was awesome!

It was time to order the actual prototype and start testing it for real in one of the factory halls.

The order was made for 40 anchors and an appointment was made for the installation in the hall.

Suddenly my manager is fired.

Oh...
Ehh... That sucks. Well, let's just continue.

The hardware arrives and I prepare everything. Everything is ready and I'm pretty nervous. I've put all my expertise in this project. This is gonna make my career at this company.

Two weeks before the installation was to take place, not even a month after my manager was fired, I hear that my project was shelved.

...
...

Fuck

"We're not prioritizing this project right now" they said.

...

It would've been so great! And they took it away.
Including my salary and hardware dev cost, this project so far has cost them over €120k and they just shelved it.

I was put on other projects and they did try to find me something that suited me.

But I felt so betrayed and the projects we're not to my liking, so after another 2-3 months I quit and went to my current job.

It would've so nice and they ruined it.
Everything was made with Rust. Tags, anchors, RTLS server, web server & web frontend.

So yeah, sorry for the rambling.

Our team - if ever existed - is falling apart. Pressure raising. Release deadline probably failing. No release ready for Big Sur.

Almost seemed we were getting somewhere: More focus on code quality, unit tests, proper design, smaller classes. But somehow we now ended up in "microservice" hell; a gazillion classes, mostly tested in isolation, but together they just fail to do their job. A cheap and dirty proof of concept from March is still more capable than this pile. I really start to doubt all that "Clean code", TDD, Agility rhetorics. What does it help you, if nobody cares for the end result? It's like a month I try to hammer down that message: we have to have testable artifacts, we have to ensure code signing works, our artifact is packaged and installable, we have to give QA something they can test - but time just passes and this piece of shit software is still being killed or does nothing.

Now my knee is broken and can do no sports and are tied to my chair even more. To top it all my coffee machine broke and my internet connection was abysmal this week. Not the usual small disconnects, after which it would recover, but more annoying and enduring: often being throttled to 1.7 MB/s (ranking my connection in the slowest 7% even in Germany). My RDP sessions had compression artifacts all over the screen and a mouse click would only take effect 5 sec later.

But my Esspresso machine was just repaired. Not all hope is lost.

Listened for about a half-hour yesterday to DevA ‘beat down’ DevB writing a console app for trying out a proof-of-concept idea he had.

DevB: “What’s the URL of the development server?”
DevA: “Why? What are you doing?”
DevB: “I’m needing to throw some messages to it so I can capture data for something I’m working on.”
DevA: “How are you calling the service?”
DevB: “I wrote a console app”
- you could almost hear the eye roll -
DevA: “A console app? Why in the world would you write a console app?”
DevB: “Oh..um..no reason. I just need log some test data for something I’m playing around with. How should I do it?”
DevA: “If it’s test data, you should have wrote a unit test. You see, unit tests …”
- yammer on and on for about 5 minutes about the virtues of unit tests…never really explaining anything -
DevB: “Yea, I’m not needing to test the result or anything. I just need to log some data.”
DevA: “Then you should use a unit test for that, not a console app. With a unit test, you’ll be able to validate the data. That’s what unit tests are for. Microsoft should have never put in console apps in Visual Studio. It just leads to bad coding practices.”
DevB: “Um…I don’t care. It’s a console app because I just need data…thanks anyway”

Today, DevC was talking to DevA

DevC: “Charlie is testing the order module, but there isn’t any test data. Do you still have the data generating script?”
DevA: “Oh yea, I’ll send him my console app that populates the database.”

It was all I could do from screaming “You stupid –bleep-er!! What the f–bleep-ck was all that yesterday?!”, but none of my business. Better to devrant about it than start a fight.

Things that I will do during the next few weeks at work because I am an asshole:

Write an entire CLI utility in Rust for internal processes, no one on my city understands or even knows that Rust exists.

Write a small desktop app as proof of concept for another department that had made the idea some time ago in either: GnuSTEP Obj-C or Lazarus Pascal for the same reason as the Rust application.

Job security people. And I have a tendency to write things in stuff that no one else uses.

Ah, the little subtle things we have to iron out as we progress from Junior Developer to Medior Developer.. things like:

- knowing the difference between a carriage return and a line feed (although having worked with analog typewriters helps) and later knowing that Unix-based systems and Windows NT-based systems implement it differently..

- knowing that serialization is important because not all computers interpret data the same way and some computers allocate 4 Bytes for a construct, others 16 Bytes.. and then we get the funkiness of transferring character sets between machines..

- knowing that a whitespace character is not only an actual space (as is known in ASCII as code 32). This one can cause even medior developers a headache, as in: why the fuck does this string function say that "hello I am a duck" and "hello I am a duck" are not the same?! Turns out then in the debugger that when you expand every character in the string you see that string1 contains 32 32 32 32 as usual.. but then string2 contains -96 -96 -96 -96 and you're like.. what the fuck..? Then you know you have to throw \\h regex at it. Haha.

- finalizing our objects and streams (although modern languages do that for us).. otherwise we have to do funky shit like trying to find what's locking a file, which is not so easy to figure out.

- figuring out why something won't work often requires you to not only break down the problem in smaller steps, to use a debugger, but sometimes it's even better to just create a proof of concept, slap some minimal code in there and debug that.. much easier.

- etc.

:)

Gave a recommendation to the boss to do a thing. He said “Go and do the thing.” I wanted to do a proof of concept but there was no time. We got the contract. I tried to do the thing. It didn’t work. It WON’T work because the vendor’s marketing far overpromises what the product can do. No way to back down because the client is already fully invested in the solution. I want to quit my job AND my career now because I apparently suck at all of it.

Architect: I know we said we would never do The Thing because doing The Thing is really bad, but can we do The Thing for a proof of concept?

Me: How about Fuck No! Unless you are proposing a solution to fix The Thing, we are NOT doing The Thing just to satisfy some perverse curiosity you may be harboring.

In This Rant: A mildly satisfying piece of mind story.

Using code to prove yourself right is a hell of a drug.

A few weeks ago I whipped up a tiny program that downloads configs from hardware we manage. Since the vendor's API documentation is hidden behind a pay wall, my method of extraction is different. It results in bigger files, but testing showed it to still be valid.

Enter today. Interns at work downloaded a config to load onto a spare machine and it won't work.

"TheCapeGreek, your configs don't work"

I was confused since I tested the files when I built it and it worked. I am also currently fleshing out that download utility's features so the fear that I've been wasting the past 2 weeks on improvements is looming.

Last 15 minutes of the day and nothing else to do so I figured I might as well whip up a string comparer. The smaller file's content is scattered in the big file so a direct diff won't work.

Code it all, quick hardcoded proof of concept code, bit it got the job done. I was right, my bigger file is still correct!

Turns out the issue was with the machine they were configuring. They found this out before I finished my test code, so I'm off the hook already, but it was good to have piece of mind haha!

The project is nowhere near complete, the customers are waiting for demo/proof of concept. the code is spaghetti and I'm burned out.

Oh, and I'm a solo dev.

Adding a proof of concept directly to production and handing it over without a single test is God's blessing.

Fucking regulations, can’t play with twilio api.
Waiting for verification of my identity to make a fucking test call to myself.

Wanted to make a proof of concept during weekend, but won’t happen cause some fucking policies.

Fuck you government pigs.
Probably need to wait to fucking Monday. I will forget what I wanted to do till that time.

We are making your life easier all the time in the news, yeah right eat those popups motherfuckers.

Next regulation - government code reviews before push to master and programmer certification, for sure those fuckers are able to do it.

Really considering emigration from Europe right now.
No fucking point to start a business on this continent.
More fucking law please so we would need a lawyer before wiping ass.
Need to watch that southpark episode about security toilet checkout once again.

Why for fucks sake can't I motivate myself to finish my thesis?

I mean I guess it is because I already got my third raise in my current (full-time) job because of hard work, which left not much time for side projects (or thesis writing).

On top of that, there is nothing which forces me to finish. My Prof. does not really care. I would probably not earn more because of a higher degree. Only thing is I have to pay the fee for enrolment once a semester.

Also, going back to my thesis project after some time, and having to upgrade all the npm modules in there does not help.

Even though I already have a working backend and proof-of-concept app, something blocks me from finishing all this work.

It is a curse. I would do so many side projects, but I tell myself that I first have to finish my thesis before doing anything else.

It is some kind of loop and I have yet to find the return condition.

I was asked to make proof of concept small frontend app with some simplified requirements, they asked me because it should be written in the stack I done most of my career work with. I do it in 3 days instead of 5, using those 2 days to optimise the app and explore different approaches. I noted down my findings, what to avoid and reasons and also what is good to use and reasons and shared with everyone.

We waited for the project to start, I started working on another project in the meantime and there was a big rush to make project go live etc., so I was consumed 100% on that new project.

So they put in charge backend php developer to do frontend js work. I said ok, do you need help in starting out? Nah, my proof of concept repo is enough.

4 days before that small project goes live they asked me to do code review. All things I noted down to avoid are in the codebase, few bad practices but everything is over-engineered (in a very bad way), some parts should be more flexible as current setup is very rigid, having almost all kinds of CSS, I saw SASS, CSS variables, 2 different CSS-in-JS tools with some additional libraries that is used to toggle classes.

I don't know how to approach this as I am not asshole as a person and I don't want to say to my colleague that his codebase is completely trash, but it is.

The worst parts: They called me to help finish the app and budget is almost spent!

I would rewrite the whole app as the state of the current app is unusable and everything is glued with bad Chinese ducktape that barely holds.

Additional points because it won't bundle as everything is f**ked.

I am seriously thinking of duplicating master branch and refactor the whole fricking app but won't do that as I am burning midnight oil on other two projects. Don't worry overtimes are paid.

I hate those shitty situations, this project was supposed to be tiny, sweet and example of decent project in this company but it is instead big fat franken-app that will be example how smart it is to avoid putting backend dev to do frontend work (I also agree for vice versa)!

Joined a new startup as a remote dev, feeling a bit micromanaged. So this week I joined an established startup as a senior mobile dev where I work remotely.

Previous two devs got fired and two new guys got hired (me as a senior dev and another senior dev as a teamlead, also third senior dev will join next week).

Situation is that codebase is really crappy (they invested 4 years developing the android app which hasn't even been released yet). It seems that previous devs were piggybacking on old architecture and didn't bother to update anything, looking at their GIT output I could tell that they were working at 20-30% capacity and just accepting each other MR's usually with no comments meaning no actual code reviews. So codebase already is outdated and has lots of technical debt. Anyways, I like the challenges so a crappy codebase is not really a problem.

Problem is that management seems to be shitting bricks now and because they got burned by devs who treated this as a freelance gig (Im talking taking 8-10 weeks pto in a given year, lots of questionable sick leaves and skipping half of the meetings) now after management fired them it seems that they are changing their strategy into micro managament and want to roll this app out into production in the next 3 months or so lol. I started seeing redflags, for example:

1. Saw VP's slack announcement where he is urging devs to push code everyday. I'm a senior dev and I push code only when I'm ready and I have at least a proof of concept that's working. Not a big fan of pushing draft work daily that is in in progress and have to deal with nitpicky comments on stuff that is not ready yet. This was never a problem in 4-5 other jobs I worked in over the years.

2. Senior dev who's assigned as the teamlead on my team has been working for 1 month and I can already see that he hates the codebase, doesn't plan on coding too much himself and seems like he plans on just sitting in meetings and micromanaging me and other dev who will join soon. For example everyday he is asking me on how I am doing and I have to report this to him + in a separate daily meeting with him and product. Feels weird.

3. Same senior dev/teamlead had a child born yesterday. While his wife was in hospital the guy rushed home to join all work meetings and to work on the project. Even today he seems to be working. That screams to me like a major redflag, how will he be able to balance his teamlead position and his family life? Why management didn't tell him to just take a few days off? He told me himself he is a senior dev who helped other devs out, but never was in an actual lead position. I'm starting to doubt if he will be able to handle this properly and set proper boundaries so that management wouldn't impact mental health.

Right now this is only my 1st week. They didn't even have a proper backend documentation. Not a problem. I installed their iOS app which is released and intercepted the traffic so I know how backend works so I can implement it in android app now.

My point is that I'm not a child who needs hand holding. I already took on 2 tickets and gonna push an MR with fixes. This is my first week guys. In more corporate companies people sit 2 months just reading documentation and are not expected to be useful for first few months. All I want is for management to fuckoff and let me do my thing. I already join daily standup, respond to my teamlead daily and I ping people if I need something. I take on responsibility and I deliver.

How to handle this situation? I think maybe I came off as too humble in the interview or something, but basically I feel like I'm being treated like a junior or something. I think I need to deliver a few times and establish some firm boundaries here.

In all workplaces where I worked I was trusted and given freedom. I feel like if they continue treating me like a junior/mid workhorse who needs to be micromanaged I will just start interviewing for other places soon.

Hmm... Okay crazy deadlines. We hacked together a really makeshift application to handle streaming content to end users. The proof of concept was demonstrated to a partner company on a Wednesday. They said they wanted it on Saturday. Our CTO agreed. We didn't sleep.

saw an SSIS project once used for basically string replacement and file tasks. Asked manager permission to rewrite this Proof of Concept to something more suitable language.
manager: you can't but you have to support it.
me: but i tought it's a PoC
manager: yes it is
me: so what to support?
manager: it's been sold to a customer and in production for 6 months now
So it's a PoC which is sold and moved to prod...
I hate sales and management douches sometimes... like 98% of the time....
(already left the company)

We’ve been discussing it, from a lot of angles. We mixed in the domain constraints for this feature and how to build it. I’ve been at the drawing board, and at the keyboard trying to get it into code. FINALLY I have something to show for the hard work, a working proof of concept. It felt good. There are a lot of things still left to polish, but we have most of the building blocks. If that ain’t the best feeling and the reason to work in this field. Left the job yesterday with the feeling that I’ve accomplished something, that’s not often since it’s otherwise mostly meetings and boring code reviews. Satisfaction.

(As of Tuesday at 10:00 PM) We have a project with a hard due date Sunday.

We have yet to get a proof of concept finished.

My team has no grasp on reality or how long this project is going to take.

I'm screwed.

As silly as it sounds, but migrating our company's web application from Ember/JSON API --> React/GraphQL would be a pretty solid achievement.

We're almost to read-only feature parity at the moment with a single developers side time as a proof of concept.

Continuing my saga, I'm now tasked with creating a .NET Web Form app and then converting it to ASP.NET Core as a proof of concept.
Problems:
- Web Forms are not supported in Core and are not planned to
- After 3 weeks I still do not have a work laptop
-- My personal laptop is a Chrome book running Linux
--- I can't install VS2017 on my laptop, I need it for this project.
- Working from home, where I have the resources available, is apparently against company policy (I'm not 100% on this yet, can't find it myself)
- I'm likely going to be sent back to the offline computer lab at a different location to work on this, where I doubt the programs/packages are installed

Perfect.

Me: finally we have automated deployment to production
Team Lead: No production deployment still requires manual approval
Me: ok how do you want to handle it slack, webhook, what do you suggest
Team Lead: let's do a proof of concept (POC) for this
Me: Ahh... Poc for this ?
Team Lead: you don't know sh*t ?
Me: well I know you're are creating that here

Next day team change...

Before my vacation I’d been chatting with one of our dbas about an etl tool we needed for a customer we’d already signed all the contracts with saying we would provide one for a historical database of old data. They had been looking at one from SAP but in typical fashion a license was worth more than the actual contract.

Anyway long story short on the weekend before I went back to work I rattled together a little python proof of concept using a couple of azure databases and when I went back demo’d it to the pm and dba they loved it and we built on the poc to have a working loader which saved us about £30k by not buying the SAP product and just wrote our own.

Just completed a 24 hour hackathon at my school in which the 'best software' winner purely had mock ups of yet another mobile app and had no proof of concept. Meanwhile my team developed a scaling platform online that adapts to groups of user's trends to create optimal results.

I guess I keep misreading the definition of 'software' in the dictionary each morning. (RULE #8.2 - Software Engineers shall read the definition of the following phrases each morning excluding Saturday: software, heap, ego, scrum, algorithm, the documentation of C)

Our business partner just tried to deliver a motivational pep-talk to the dev team that ended up sounding more like a sermon. Instead of hearing we did a good job, we heard we could be doing a better job. Never mind that the project is rushed, lacking funding and built on an unstable codebase inherited from a proof of concept demo. I just lost all respect for the guy, who I thought appreciated how hard we've been working. Apparently he's just another administrative cog who wants to climb the ladder of success while standing on other people's hard work.

Right, no more extra miles for this project. Time to just coast on and see it sink in its own excrement.

First go through any getting started guides or introductory tutorials. Then depending on comfort level and available time, either start exploring further on your own or search for more advanced tutorials.

Try to make use of what you learned, either at work or in hobby projects or small proof of concept programs, as the case may be.

//long rant ahead!

I need to plan a Wiki with SharePoint for not connected Sites.
Im now in dispute with my CoWorker since 3 Months, this is how the conversation goes. My two bosses are involved in this and also unhappy about SharePoint.

[C refers to CoWorker, M for me]
C: Hey, we finished SharePoint with Selfservice Storage Rooms. They even have a Wiki.

M: Okay cool, will check it out

C: Well we need to also plan the Wiki inside, I already asked our Department Head and he agreed, that you will be the one.

M: Okkkkaaayy, normaly it's your job to do such things, but welp, I will look into it, if we can work with it.

(2 Weeks pass)
M: I checked SharePoint out and tested everything. The Wiki is a Nogo, we need a other solution or programm for ourself a Wiki Integration/Engine. Did you maybe check out Confluence? It has also a SharePoint integration plugin.

C: We wont do Confluence, too expensive (already overspent the budget for SharePoint in six digits 🤬). Also we wont add to SharePoint Custom Code, it needs to stay standard.

M: Thats impossible, SharePoint Wiki is shit and also handels sites just like documents, no brain behind! Also you overspent the Budget and now it's my Problem?!

C: You need to do the best out of it.

(3 weeks passes and we get a meeting with the department heads)

M: Alright I made a UseCase and documented where the essential flaws are in SharePoint Wiki and why we cant use it.

Boss: Ok if it's impossible to use, then we will stay on our Fileserver for Documents and wont use SharePoint.

M: Thats not my Point, my statement is, as status today, SharePoint Wiki is not the right solution, code or buy software to it.

Boss: We will do a Prove of Concept, if it doesnt work then we will aboard it.

M: Well it is only some missing essentials, like hierarchy and Groups for the Pages, Example Confluence has this. If we could built in this features in SharePoint, everything would work out.

C: (angry) I told you that we wont use Confluence!

M: (calm) I said we need Features, not Confluence. Please mind the consent.

(3 weeks passes, and one more meating with bosses)

M: alright here again is a analyses, why already in Theory the current SharePoint Wiki wont work. It's already flawed in the core.

Boss: Yea SharePoint is crap, I checked out confluence and thats a real Wiki.

C: Well I dont know anything about Confluence and never looked at it. But if SharePoint is a fail we need the Proof of Concept.

M: Why do we need to do a Proof of Concept, when it already doesnt work in Theory! Thats nonsence and unlogical.

Next meeting will be in 4 weeks and I will give him the FUCKING PROOF OF CONCEPT. I will be a Bastard and build behind CoWorkers back a Confluence Wiki to show the Departmentheads how to built it right.

I hate CoWorker now, he makes a part of my loved Job a hell, I will goddamn cuk Coworker to space, that fucking Cukatron of lazyness and shit 🤬. I provide the Solutions and you just say no, how dafuq will the project advance, if you always say NO! Are you so unflexible and fixed on your Castle of Ignorancy!

My college senior project has become a monster. I look at it and all the work put into between my friend and I and all I can think of is

"This shits fucked I'm glad it's not for sale"

Seriously it works for the most part, but we're up to ~2500 lines of code and about as many headaches and it's still missing so much functionality and has so many security flaws. It's a great proof of concept, but good lord I couldn't imagine building it into a feasible application. It'd take months of work full time!

Over the last few weeks, I've containerised the last of our "legacy" stacks, put together a working proof of concept in a mixture of DynamoDB and K8s (i.e. no servers to maintain directly), passing all our integration tests for said stack, and performed a full cost analysis with current & predicted traffic to demonstrate long term server costs can be less than half of what they are now on standard pricing (even less with reserved pricing). Documented all the above, pulled in the relevant higher ups to discuss further resources moving forward, etc. That as well as dealing with the normal day to day crud of batting the support department out the way (no, the reason Bob's API call isn't working is because he's using his password as the API key, that's not a bug, etc. etc.) and telling the sales department that no, we can't bolt a feature on by tomorrow that lets users log in via facial recognition, and that'd be a stupid idea anyway. Oh, and tracking down / fixing a particularly nasty but weird occasional bug we were getting (race hazards, gotta love 'em.)

Pretty pleased with that work, but hey, that's just my normal job - I enjoy it, and I like to think I do good work.

In the same timeframe, the other senior dev & de-facto lead when I'm not around, has... "researched" a single other authentication API we were considering using, and come to the conclusion that he doesn't want to use it, as it's a bit tricky. Meanwhile passed all the support stuff and dev stuff onto others, as he's been very busy with the above.

His full research amounts to a paragraph which, in summary, says "I'm not sure about this OAuth thing they mention."

Ok, fine, he works slowly, but whatever, not my problem. Recently however, I learn that he's paid *more than I am*. I mean... I'm not paid poorly, if anything rather above market rate for the area, so it's not like I could easily find more money elsewhere - but damn, that's galling all the same.

Selling a solution to a high-value client, promise them they'll get a Proof-of-Concept by Monday 10 am. You close yourself off your family the entire weekend as things weren't as simple as you thought. Present the demo to the client the Tuesday morning...

Throw out the baseline, then inherit the new baseline we paid contractors to develop as a proof of concept using tech you don't know and maintain that.

So, my simulations started to take about a week to complete.
Productively invested the time in getting into Python!

I'm really liking its syntax and relative simplicity (coming from c++) and I'm kinda digging it at a sort of proof-of-concept producer: instead of talking in pseudocode I can just put down a python script to show what I mean.

When a proof of concept goes into production because everyone else is like "care".

Did an assignment where we had to emulate deadlock using C and openMPI, I wanted to make a generalised resource manager process and create deadlock by locking some resources using the other processes, but my teammate said that would be too hard and instead the resource manager was hardcode with for loops for the number of transactions we were gonna make cause it was just a proof of concept.

Then my marker literally leads with, let me tell you the story of a good programmer, and a better programmer. The good programmer writes a function called destroy_earth(), but the better programmer writes a function called destroy_planet(earth) and passes in earth. I sighed so fuckin hard, I should have spoken up.

Just finished a little proof of concept of a reprojected multisample antialiasing technique and daaaaamn it's looking good. First time ever a rendering technique I invented isn't complete shit so that's an improvement

It still has some (pretty big) issues with both spatial and temporal ghosting but I have some ideas in the pipeline

I wish I could show you guys comparison images but as it turns out most anti aliasing techniques look pretty good on still frames but only the good ones stand up under motion and I don't know of a good way right now to capture pixel perfect clips like that

So I read about how NAND mirroring worked as a proof of concept on brute forcing the pass code in Iphone 5c. After reading a few paragraphs, I didn't understand how the researcher came to know what to do with certain challenges along the way. What the hell did I do in my 5 years of studying engineering? I better go back to the basics.

We need to test the last step in our proof-of-concept chain before putting our project proposal... but just before testing what we believe will be (finally) a functioning scenario, the key service we need and have no influence over stopped working. I am pretty sure, it will start working like 5 minutes before I usually leave.. one has to love this waitNRush development.

My client recently asked for help with a product idea he has. He already got his lead developer to hack a proof of concept together.

My client knows I have more time and would start progressing the whole project. He says that he is fed up of all of these huge plans for some huge product...

I said ok, let's start getting the next few features on and using the product with the team.

He then said he wanted a big plan for the whole thing... so I said the whole point was to just get on with it and see how we get on as there are so many unknowns.

Somehow, due to a lack of other work, I have decided to help make a proposal that is far too long for this project. Would have just been better to get on for a few days and make a MVP of the product that works.

Instead I am waiting to see if this latest proposal will actually land me this work...

I'm pretty sure all of this back and forth is proof I don't want to work for this client!

As a junior in a print communication agency, my boss wanted me to make their portfolio.
Their requirements were: a full animated flash website (in 2010...). Understand, they had been bought the Adobe license...
After several months of works and ton of alerts about flash death, the website has been deployed.
My boss did not understand why he could not visit the website with its iPhone...
The website had lived 2 months and will was replaced by a static "wix" alternative... So much work for nothing because the boss did not trust a junior dev.

Biggest lesson: Always begin with fast proof of concept to validate your hypotheses for you and for your boss ;)

Do you know where to get Windows App Signing Keys for a reasonable price?

The cheapest ones I've found were still ~€150 per year, too much for a proof-of-concept :( Not signing the app is not an option...

I get a paper and a pen and write down what I know I have to do, what I don't know how to do it and I suspect I don't know yet what I'll have to do.

For the parts I know I'll have to work using a new framework or new tools I try to create a proof of concept project I can reuse later.

I tend to write a bit in paper before coding just to wrap up my head on what I'll have to do.

2 weeks+ ago I made a PR into our codebase containing sample refactor that streamlined a significant portion of code. Also, I did refactor only on two handler packages (for MVC folks, that's Controller) as proof of concept, to figure out how convinient / logical the part would be for everyone.

We have rule of 2 approvals for merge (for 5 team members)

While writing refactor, it obviously blown up a lot of unit tests, but still coverage was fairly poor (that stuff was rushed, there was back than no time for unit tests). After my refactor I spent couple of days writing tests that hit fairly sweet (comparatively) coverage. (I managed to bump coverage from low 20s to high 80s, and have less code for tests)

I got first approve pretty much immidietely, other team member was on vacations, and 2 of them forgot.

We generally try to close PRs fairly quickly (usually same day kind of deal), but that one was just.. hanging in there. So I pinged everyone to re-check it to greenlight it but of course, loo and behold, merge conflicts arised. I ended up fixing actual logic (just some method signatures changed, not a big deal) and ran the units.

So, one of that handlers got quite a few of edits, and guess who is pretty much rewriting unit tests for second time now...

Dude, sometimes I question why tf I even bother with these tests... Feels like sabotaging my productivity, especially with bullshit like that

My office at the weekend, it’s quiet so no one annoys me, setup is good and my main side project at the moment involves a modification I want to proof of concept (to try and get funding to do it properly) to our main product so all my resources are there

Working with nightly builds and concept tech is such a fucking hassle...

I'm currently working on a WebAssembly proof of concept where I need to generate a unique id, but since threading is currently not supported (rust and webassembly) I cant use half of the libraries currently out.

And the ones that does work... guess what... are not compatible with the nightly build of the compiler I'm using for Rust. Just fucking end me.

The legit only workaround I can find is to make a server request and get the unique id from there... piece of cunt software...I need a break 😑

Anybody know where to find the bluesniff android app? It used to be able to see undetectable bluetooth devices. I go to the apk download pages and it is just gone. There was source code available in an archive but that is gone too. I found some proof of concept scripts on github, but nothing that can easily be turned into an app.

I've said it before and I'll say it again: I believe in theoretical study prior to proof of concept.

At least for me, it takes me a 100 times more time to make a proof of concept the 'quick and easy' way rather than properly studying the theoretical knowledge and then applying it.
For example, it took me one and a half months to build a small website in ReactJS without much prior knowledge. It took me exactly one day performing the same task when I properly had studied all its internals and theoretical knowledge before I started.

If I know what I'm doing, I can easily create; if I don't, then I'm just messing around, looping myself into problems ad infinitum.

Teach a man to fish..

How is it that a customer ends up "failing" some development work which was our (my) idea, presented to them as a proof-of-concept solution to a problem?
Mentioning some phantom specification and saying "it's not this and it's not that".
You'll get what you're given you fucking little retard piece of shit. Sorry I opened my fucking mouth, you can struggle in future you stupid, inconsiderate fucking hollow-brained bastard. Shove it up your arse and take your manager's dick out of your mouth. They think you're a fucking prick too, just like your parents.

So I finally had a good idea.
I have programmed a proof of concept and now dont now what next.
I would like to make it open source and let people benefit from it. But at the same time I would like to make everybody using it to generate money pay a part to charity and a part to me.
How could I do this? Do I need a patent or a licence or what?
Is this even ok?

recently, I was working on a project to playback archived call recordings, and another developer was hired. part of my job is also to support a third party automation framework for customers, so I got "seconded" to support a proof of concept. the original project had now been messed up, it works, however, the functionality that made it secure has been MASSIVELY compromised for the sake of effort. I've tried to cause a stink as we have a major customer who will fail the next PCI audit. opinions on the situation. the other developer has a lot more experience, but seems to have chosen to satisfy management on deadlines over the original spec...