And that would strain your eyes or force a bigger font. At that point, you'd be wondering, like me, on why I spent $$ to buy a bigger screen in the first place.
I got an open box lenovo 24 inch QHD monitor for years and it just works solid across windows, mac and various docking stations. I could imagine upgrading to a 27 or 30 inch but beyond that is just too much IMO.
Maybe taller, more square could be of more use than wider.
I advocated for a SQL solution at work this week and it seems to have worked. My boss is wary of the old school style SQL databases with their constraints and just being a pain to work with. As a developer, these pains aren't too hard to get used to or automate or document away for me and never understood the undue dislike of sql.
The fact that I can use sqlite / local sql db for all kinds of development and reliably use the same code (with minor updates) in the cloud hosted solution is such a huge benefit that it undermines anything else that any other solution has to offer. I'm excited about the sql stuff I learned over 10 years ago being of of great use to me in the coming months.
The last product I worked heavily on used a nosql database and it worked fine till you start tweak it just a little bit - split entities, convert data types or update ids. Most of the data access layer logic dealt with conversion between data coming in from the database and the guardrails to keep the data integrity in check while interacting with the application models. To me this is something so obviously solved years ago with a few lines of constraints. Moving over to sql was totally impossible. Learned my lesson, advocated hard for sql. Hoping for better outcomes.
I totally understand the apprehension towards SQL. It's esoteric as all hell and it tends to be managed by DBAs who you really only go to whenever there's a problem. Organizationally it's simpler to just do stuff in-memory without having to fiddle around with databases.
Another thing that worked well for me is to keep discussions very low and quick on topics like personal relationships, work, career and hot button topics like AI, weather, traffic, climate change, house prices, etc. Basically avoid anything that a newspaper would think is worthwhile for frontpage or editorial column.
I go heavy on food, travel, culture, rumors, art, movies, music, design, festivals, holidays, games. You could talk hours on stuff here, just pick an artsy cultural magazine or subreddit and keep up.
Side note, inviting views from both sexes makes for some very interesting short conversations. Both have very very different takes on the same things and therefore won't talk too long. Both being interested in very different things (think dress belts, hair supplements, birth control vs fishing, bourbon and soccer) brings some newness into the conversation.
I graduated right after the 2008 crisis, took 3 years and many temp jobs to get one where I would be paid to write software. Those 3 years were terrible and I estimate it set me back by around 5-6 real years.
Looking back, what would I have done differently ?
(0) mental health is the most important at this stage. Stay close to people who are with you in this difficult time. Never forget their contributions. For me it was my grandma.
(1) have unshakable belief in myself and my worth, never letting my employability be a measure of my worth and identity. Deep down you would question yourself and think its a lie. It isn't.
(2) I should have absolutely used that extra time to master the interview stuff (algorithms, data structures, OS and networking concepts, etc). Sooner or later I would interview at a FAANG which measure solely on these factors, so could have used that extra time to master interview skills. I wasted time on side projects, resume padding and niche upcoming tech stuff.
(3) tech surfing. Ride the latest wave with some side projects. Don't go deep. Just surf.
(4) All things, good and bad, will end. "This too shall pass"
On #0, there was a group that did this in SV around 2000 called itself "Recession Camp" where they did free/cheap group activities. Would be cool to see something similar, but more persistent.
On #2, with the dotcom bust and further complications post-9/11, I spent my year without work in a house without a decent enough phone line for dialup and learning C# with a big fat book and the command line compiler. I wouldn't discount side projects, etc... but yeah, staying up on interview skills is important. I'm a bit old, with a family/life so what hits me in those scenarios is there's less accounting for "experienced" developers a lot of the time.
No. As junior you feel the pressure to make senior. You can't be junior for too long.
As senior, if you choose, you can coast. By coast I mean you do justice to your job and the salary you are paid. Its a perfectly acceptable choice for someone to be senior for as long as they want.
The biggest bottleneck is going to be what other seniors and higher think of you.
Understandable. I usually only recognise AI assist cos someone in the comment section points it out. But the off putting tone of this was blatantly obvious. This is by far the most AI influenced article I have read yet.
Not my experience at all. The very notable engineers I know didn't do their most notable work because of engineering or coding skills. Instead it was finding interesting problems and making a start or thinking a bit differently about something and doing something about it and being approachable and available all along that made a difference.
If all they did was code all the time, write code for fun and interacted mostly with other similar people, they probably wouldn't be the first choice for these projects.
So is SQL. To me. But some otherwise rational people have an irrational dislike of sql. Almost like someone seeking to seal a small bruise with wire mesh because bandaids are hard to rip off. The consequence shows with poorly implemented schema-free nosql and bloated orm tools mixed in with sql.
But some folks just like it that way. And most reasons boil down to a combination of (1) a myopic solution to a hyper specific usecase or (2) an enterprise situation where you have a codebase written by monkeys with keyboards and you want to limit their powers for good or (3) koolaid infused resume driven development.
I dont see the point of smart watches either. I wear a casio / gshock with the backlight button that sticks right up on the front of the watch. i am on my second watch now cz my sister gifted it to me. the first is ticking away happy with 0 charging , battery changes to date.
0 reasons to change.
my sister otoh has an apple watch that she never charges, lies in a drawer which i hear about when she's trying to find her phone. conversation ends with "eh i should charge it maybe"
if i ever buy a smart watch, will likely be the pebble
Very interesting example. For me spaced repetition today looks very different than it used to till a few years ago.
My "system" is now some google docs, some google sheets and some html hosted on my domain. I have no black box algorithm to offload to.
I'm now curious if i could try applying it to everyday things i learn and want reinforcement on along with the technical stuff i want handy. Thanks for sharing.
I got an open box lenovo 24 inch QHD monitor for years and it just works solid across windows, mac and various docking stations. I could imagine upgrading to a 27 or 30 inch but beyond that is just too much IMO.
Maybe taller, more square could be of more use than wider.