As an app developer with a focus on web apps, what can I possibly use bitwise operators for?

DDD encourages brute forcing a solution for quick value abstraction followed by later refactoring. Idk how I feel about that.

Im pretty convinced that you cant be an exceptional software engineer and not suffer from some form of OCD

I’m in the background check phase of my verbal offer. The check is on its second week pending which is normal and from the status update it looks like it’s almost done. But my recruiter told me yesterday that I would receive an offer letter by the end of the day that is contingent on the finalization of the background check. I received no letter by the end of the day. It makes me nervous because the VP has to sign off and approve this offer before it can be sent to me. Is it possible that they would put me through seven interviews, many recruiter calls, and now a background check just to tell me that it’s been unapproved last second? My mind goes there instantly , I know realistically the background check phase means I’ve got the job contingent on the fact that I didn’t kill anyone or lie about my résumé. But damn why tell someone they’re getting an offer letter the day of and then let it never happen? I’m losing my shit over here. So much time effort and mental well-being has gone into this process that I can’t even imagine it falling apart

I always have last minute panics during the last background process of hiring stages. I’ve seen people actually get offers pulled over degrees. Granted it was ibm which is a very old school org but it’s always nerve-racking. “Stay positive, stay positive”

I’m Just venting. I’m really not this dramatic in person. Just putting my clouded thoughts out there.

Just realized the PHP of a Pojo is a Popo 👮🏻‍♀️🥁

Got a very surprising call yesterday:

I got the job!! Getting converted 🥳

Pro tip for beginners: It is better to pick an algorithm that remains practical while being simple enough to remember and easily reason with then to have to look up and relearn the harder approach each time its needed.

Of course this comment is not directed towards any approach with highly varying results. If the simplified approach yields 2x the time to execute, by all means use the right approach. What I mean by example is: There are at least 3 different ways you can utilize a sliding window approach. If you combine every approach out there is prob more like 50. Some are complex with dictionaries to track seen values. They remain O(n) but are overkill. Some just use a temp value and call it a day while maintaining same tc. If one clicks with you but is not necessarily the orthodox approach, fuck it.

Use what makes sense. There are mathematical solutions to most problems that can reduce your code to one liners and absolutely no one including yourself will understand what it does. We have to understand that most of us are not math majors but are dedicated to writing comprehensive software.

Anyone in the Austin new silicone valley (round rock)? How are things feeling over there? Would you move into that market if given the chance and a good job?

A fair live code assessment includes at least an email with a description of the problem 10-15 minutes prior. Its a small enough window for the dev to digest the problem without the time to google a solution which if the problem is rephrased with care, should not be easily searched.

If your after the best talent the industry has, the guy that reads algorithm books on his spare time and is an absolute silo of a dev, go ahead and present your Josephus challenge and expect them to ramble off some formula they picked up in their 8 years of math centered schooling.

I’ll eventually be in the position where I’m interviewing regularly. I haven’t been due to the yearly lateral moves needed up until now I’m my career. And I can promise that will never be my expectation regardless of the ego around my team.

Code samples should be discussed, some of the developers best work should be brought to the interview to discuss his approach. If most of his works on private repos, bring their best personal work. If their not working on any open source or personal then 🚩.

Live performances are not realistic. It’s the one time in their careers that they will code for an audience and are expected to on the fly solve issues more complex then their regular work.

Let’s get real

7 days of interviewing and 5 days after no word …. I’m contracting here already. I get but would never condone leaving external candidates waiting. Those contracting on your teams even more so. Mutual respect

Interview question: "So given you have 800,000 orders that are placed an hour, surely this table will grow beyond what our architecture can handle rather quickly. How would you handle this".

Response: "Well indexing can only take you so far (eyes raised at this. They didnt like hearing this). Horizontal partitioning always feels like a quick and temporary fix. Ive heard its actually a sound approach, after a few weeks to archive orders in a json format and store them in an s3 or glacier bucket, depending on how often its needing retrieved. If the user needs their order history often, S3 is infinitely scalable and quick to access. If you want to save money and save it on glacier then customers can make formal requests for their history."

Their response: "..... ok but what if amazon was not at our disposal ?"

Like tf dude, im giving modern solutions to modern problems. Do you want to know that I understand the core basics of design or do you want someone who can keep up with tech and provide sound solutions ?

For those following my interview process with apple, I asked for feedback on one of my 7 interviews.

I’m glad I did. Was very insightful and, well discouraging but helpful. After rambling about the projects I’ve led, green-fielded and planned over the last 7 years for an hour, she replied:

“your very experienced…. But we have a few candidates who are more seasoned. You have the experience but just not the same seasoning”

It’s a senior role at big Texh so I knew what that meant. College graduate, 10+ year track record, neck beard in the industry.

That helped me take it less personal. They’re not after a 27 year old college dropout that clawed his way from startup to startup, leading every chance I took to finally get a shot at big tech while raising 4 kids. They don’t need someone who compulsively assigns two hours a night to get ahead in the industry. They don’t need my sympathy story or my best efforts. They need “seasoning”.

Discouraging and out of my control.

Todays been the worst day ive had in awhile.
Im already awful at doing in live coding interviews. The ability to demonstrate in front of people is just rarely the same as being able to perform without the pressure.

In the interview i was asked to take an array [1,2,3,4,5,6] as example. Provide an "nth" value (lets say 2) and recurse down in this ring around the rosey fashion like [1,3,4,5,6] -> [1,3,5,6] -> [1,3,5] -> [1,5] -> [5].

Just typing it out still makes little sense to me or for that matter, why I would ever need to know this. Has anyone else had to prove this kind of apparent hard skill in an interview ? Ive been contracting with the company and leading projects for half a year. They did a four hour analysis over what I did and felt confident.

This just f'in sucks

I still think node is gonna continue taking the F off server side, eventually becoming a norm of sorts. No matter what organization I join, it’s the same song and dance. Migrating slowly to node services.

I’m not marrying node here so slow the defenses but it’s an undeniably trending pattern

Its just rude to hand someone the ugliest service you wrote and ask them to fix the massive amount of issues with it. I dont care how well we get along, dont F me like that. I will leave jobs over that shit. Its not my job to maintain someones rushed filth when they're still here. You can argue that it is but I wont do it.

Instead of continuing to hand the guy that writes garbage more feature sets, have someone responsible do it while he cleans up his past services.

I had never heard the word cartesian used prior to apple. Now its all I hear. No one can form a complete sentence without using the word "cartesian" and "hollistic".

Every sentence goes like "When looking at thus issue holistically, yada yada cartesian product is restored". The terms lose their ability to project intelligence after being repeated in every standup.

I just about lost my job cause query logging to stdout was enabled and causing OOM crashes across the now live platform. It was a one liner to disable.

crazy how small of things in this field can to make or break you/it.

Personally I’m devastated and tired

Just gave a long overview of nodejs and building servers with it to someone coming from c#/.Net. Explaining the differences between the two kinda gave me more appreciation for node and the freedom it gives devs to build the way they wanna build. Agnostic tooling always wins. Save the opinionated software and visual studio for the birds.

When your given an in between phase at work, seize that shit. Find an excuse to Build something that could be useful and that pushes your boundaries. Do something crazy. Opportunities sometimes are made but most of the time created.

Im really liking python alot.

However I am not enjoying django. The framework feels dated. The documentation still has a template focused approach to it which is understandable sense its a MVTemplate approach. Even the Rest framework utilizes the same "views" convention that just feels wrong coming from years of MVC.

If I know anything at this point its that I learn the quickest by enjoying what im working with so im moving on to either flask or FastAPI which both seem to resemble modern server frameworks more.

Anyone have suggestions on the next thing to stab at ? Preferences ?

Ima post a rehashed meme from programmershumor. Let’s see if people pay it more attention then my thought out rants.

I just got my first kubernetes cluster configured and damn it get good. Like Bette then any code I’ve written in a long time. Am I...... am I turning to devops..?

The internet made going from sql to mongo so easy. We all already had sq concepts embedded so a Google search for “how to run explain in mongo” turns up hundreds of results. The concepts are there, it’s just translating them to a similar tool

One important lesson I've re-learned too many times: If your splicing, your approach is wrong.

I think this might be my managers first MVP hes worked on. We're 2 days away from go live and hes still stressing for us to push large changes up to UAT (staging). Core calculations are being changed right now and being stressed to deploy.

At the same time though hes learning that these things almost ALWAYS have some type of cascading affect so hes adding "but lets not break anything prior to going live". My response is pretty clear: "Shits going to break or experience adverse effects. Its inevitable". I can hear it in his voice. Hes struggling to learn the weights and balances between these decisions. His green fielding cherries popped and hes seeing what real product development is about.

I am leaving the .Net ecosystem.

I got into with one intention. To be an easy target for large companies and easily marketable employee. .Net is everywhere, I means absolutely everywhere. It is a great solution for large infrastructure and that is the very reason I despise it. It's big and its clunky despite all modern attempts with core to reduce setup.

More importantly, Im learning more about what kind of work I thrive in and want to perform in my career. I dont want to build large servers that uphold entire Saas platforms. I want to experiment with light weight solutions that are easily perceived and used in conjunction with other solutions. I dont want to be the .NET/microsoft stack guy, I want to be the solutions guy. These .Net roles rarely involve anything outside of the MS realm of things and its not a good look.

Im finding my niche in what we call today corporate incubators. Taking solutions that we can roll with quickly like django/laravel/symfony/Express and building out rapid prototypes that can get the job done. I guess its considered the more experimental side of development. All I know is anything beats the kind of slave labor required to just keep an oversized product running.

I know most of us help maintain and im not undermining that kind of work but FUCK its definitely not for me.

Is running a jenkins instance in kubernetes a paradox ?

I want someone to tell me I'm wrong but In my experience, Im finding all deeply experimental work to be inherently imperative in nature.

When im try to tackle a problem that I dont yet know if is possible, I don't first think through how the methods will be broken up or where composition is needed. I dont think through all the different classes that are needed to represent the domains or what abstractions could help. Its usually just alot of if/elses, a ton of variables holding on to everything in context of the train of thought I need to keep together.

Maybe its just that my mind still works in an imperative way and that paradigms have to intentionally be implemented, thus being an afterthought. Personally I think its better to abstract last anyway once you know what it is your working with. Why build something out in the most complex way just to find out that your architecture doesn't represent the domain layer in the way you had first perceived it ?

Well thats my thought for the day as I begin building out this CLI framework scaffolding tool.

I use to obsess over client work and being proficient with all the diff js libraries. Now I just want to focus on the data. Server work has this sort of structure to it that is satisfying compared to heaps of react digging day by day. Unfortunately most of the work out there today is SPA work. Fat clients are whats in. Even when hired on as a server specialist or dev ops specialist, we all somehow get sucked into front end stuff.Its really the biggest seperator Id say in this generations web technology, SPAs, fluid interfaces, NEXT/NUXT, all that flutter