Well apparently my compression algorithm actually made the file bigger. Back to the drawing board I guess?

You need to answer your manager, but don't have a clue, try these randomly:

I'll circle back to you
I will run the numbers on it
Let's go back to the drawing board
Let's touch base in a bit. Ping me
I don't have the bandwidth right now
It's on my radar
Let's put this on the back-burner
I have too many balls in the air right now
I have a lot on my plate
I'll get back by close of play tomorrow
I'll have to deep dive/drill down into this and get back
I have a hard stop at X hours
Let's park that for now
It's in the pipeline

Unity3D Game Dev Interview

Interviewer: What is reflection and why would you use it?

Me: Gives overview of system and how I've used it in games before.

Interviewer: Sorry that was a trick question, Reflection is really dangerous and slow. You need to go back and learn the basics.

Me: ???...

A huge portion of Unity is built upon Reflection based systems, the entire Monobehaviour base relies on it. Their events system uses it, animation and timeline. I guess their team needs to go back to the drawing board.

How is this person a senior dev?

While reviewing a PR from one of our newer FE devs, I ended up spending more time than I would like mulling over its composition. The work was acceptable for the most part; the code worked. The part that got me was the heavy usage of options objects.

When encountering the options object pattern (or anti-pattern, at times) in complex scenarios, I have to resist the urge to stop whatever I'm doing and convert it to the builder pattern/smack them in the head with a software design manual. As much as I would like to, code janitor is one of the least valuable activities I engage in daily, and consistently telling someone to go back to the drawing board for work that is functional, but not excellent is a great way to kill morale. Usually, I'll add a note on the PR, approve it, add a brown bag or two on that sort of thing, and make attendance mandatory for repeat slackers. Skills building and catharsis all rolled up in a tiny ball of investing in your people.

Builders make things so much cleaner; they inform users what actions are available in a context; they tend to be immutable, and when done well, provide an intuitive fluent interface for configuration that removes the guesswork. As a bonus, they're naturally compositional, so you can pass it around and accumulate data and only execute the heavy lifting bits when you need to. As a bonus, with typescript, the boilerplate is generally reduced as well, even without any code generation. And they're not just a dumping ground for whatever shit someone was too lazy to figure out how to integrate into the API neatly.

They're more work in js-land, sure; you can't annotate @builder like with Lombok, but they're generally not all that much work and friendlier to use.

If 13 hour days on Friday are the norm, I'm going to have to go back to the drawing board. Fuck that.

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

I have had to work on a project with a pc104 stack running yocto. I have had this since December last year and the image has always just randomly crashed 🤔. Yesterday I found out why!!
I am able to read the sensor of the cpu temp this has never been over 60/70 degrees C (yes I am English), however after running multiple tests and finally hitting my last wits I made the Kernel output over serial as no msg was shown on crash.
The company we have got the HW from always said this board won't over heat it throttles the cpu blag bla bla... And you guessed it in the mid of nothing but mess was a message "thermal_zone0 critical temp 127 degrees shutting down"
I didn't know if I was happy or about to cry as I didn't know if after working on this project for the last 6months I was back to the drawing boards as I need new HW or my gut at the start of not trusting the Company we are using!

Needless to say I have no idea what Monday will bring, I will keep you all posted as we all do care!

Much love

Jim

CTO needed me to add the some more functionality to a specific script and then test it out on the main site. 2 days later, I have it working from the command line, but it won't respond to the site. After some digging, I find out the script he pointed me to isn't even in use and the script that actually needs to be modified is like 1500 lines long and set up entirely different than the one I had already finished. Back to the drawing board.

Trying to install macOS on my PC and it keeps failing at the major install point during to "security".... For fucks sake!

Either get some form of 'stable' release of my current gang engine or just grow a pair and finally teach myself C and go back to the drawing board and build my engine with complete portability.

I had an idea for an open source project, but wanted to get some feedback before I committed a lot of time and energy to it. Seeing as how devRant is the only social media type app I use, I thought this would be a good place to ask.

The project would be an open source keyboard for iOS that would make it easier for devs to write code on their mobile devices. There's already a few "developer" keyboards, but they're either paid apps, or haven't been updated in a while.

Creating a custom keyboard isn't very complex, so it could be a good place for newer devs to actually contribute code and get comfortable with open source in general.

So my question is, do people use third party keyboards? Is this something people would be interested in contributing to? Should I go back to the drawing board?

Making board games in VB 6.0 with control arrays. Ah... The good old days... Control arrays were my answer to everything back then... 😎

Oooh and there was also the time I discovered the AutoIt scripting language and made MadLibs scripts that prompted for each part of speech and then typed the final result into Notepad. 😀

🤔 Or maybe if I go back even earlier... that time I discovered autoexec.bat and the escape codes for box drawing characters to make sweet startup screens for my Windows 95 install. 🤓