nkassis

Yes a capacity increase from the developer side is great but it's supply side and we need to figure out how to accelerate transforming needs into demand. This is what I foresee developers turning into (at least some capable of this). Articulating logical solutions to be built to problems and evaluating results from what's generated to ensure it meets the needs.

Aka Devs can move up the chain into what was traditionally product roles to increase development of new projects. This is using the time they have regain from more menial tasks being automated away.

That's argument is easily contradicted by plenty of worldwide examples of opposition trying to use the courts to combat dictators. Dictators often ignore court decision they dislike because they have the ultimate power of enforcement.

SolarWinds comes to mind they haven't fully recovered but they are still around and kicking.

Replaced the TV from the 80s and 90s.

I think it could be argued that the language used in universities is unlikely to be the one used professionally. I remember when the derogatory term "Java school" was commonly used for schools that shoehorned Java in all courses just to try to match the language of the day in enterprises. It really should be about what is the best pedagogical tool to teach the concepts the student is expected to understand irrespective of future professional tools used. If racket exposes those concepts better without making it onerous on students to learn that's great.

When MIT switched from scheme to python for their undergrad classes there was a big debate here aboutit. I think the argument was that python won't make learning the concepts any harder but is less of an issue for students to learn and has some long term value professionally so win-win. I don't fully agree but I can see the logic.

I'm my opinion good CEOs know when to press that emergency button and to use it sparingly. Some CEOs like Musk manage exclusively by it and I don't know that it's the healthiest of long term strategy. He does get away with it for the most part it seems.

Securing that would be interesting.

Very reminiscent of James Clark building the largest sail boat with automation with the money he made from Netscape. See "The New New Thing" by Michael Lewis from some fun and comical account of that boat.

It's not necessarily individuals. From what I saw years ago there are tons of project kicked off to see if they pan out but are probably not going to succeed. The company has some core teams around retails, mobile and AWS that do the majority of the table stakes work. The rest is a lot of team doing things that may or may not have any value. My pessimistic view is that required teams are like 10% of the company leaving 90% of maybe useful. That isn't to say the 90% should be let go. If they did you'd see no growth but it's unclear how much of it is actually useful. In good times that's fine, in rougher time they have to reduce that extra a bit.

He seems to disagree with their conclusions based on gut feelings.

I was thinking the same. Why not just a railway?

Some people have YouTube channels as hobbies ? I don't see the issue.

https://indicodata.ai | Python | Mid or Senior Software Engineer | Remote | Full-Time

Indico Data, the Unstructured Data Company, provides an innovative AI and ML powered software solution that enables organizations to automate, gain insight from, and apply their unstructured data to a wide range of automation workflows.

As software engineer on the Core Platform Engineering Team at Indico, you would write the software that powers Indico’s award winning Intelligent Process Automation product and keeps our services running smoothly. You’ll work closely with the product and R&D teams to effectively execute on our roadmap. You’ll write lots of Python and learn tons about machine learning as we work to make modern deep learning practical and accessible. We’re constantly building new features so you’ll have regular opportunities to work on greenfield projects.

Apply Here: https://jobs.lever.co/indico/0e309efd-8bd7-4304-865f-bff81f5...

I've always found value in at least scanning some articles and books for general overview of what is possible. Many dev get to a point where they learn a method and abuse it. It's the method they know and have never been exposed to an alternative. They found something that solves the problem sorta so why go look for something else.

While reading a lot of articles and books gives you a wider view, you don't have to memorize but as the article says, know it exists.

Reading a lot of the comment there seems to be a recency bias towards complaining a more recent set of policies to change police funding and ignoring the more long term problem that police may not be meeting the people needs even with large budgets.

The issue might not be funding level but misuse as you point out.

Actually I was a Math major the biggest thing for me is 1. notes can be very cryptic after the class without the verbal context. A lot of course also have that advantage where the teacher would provide notes afterwards so yeah focusing in on what was said was the highest value.

It was my fault that I zoned out, that's why I had to find a way to avoid it.

I was not a great student but at one point in college I realized that I wasn't listening while taking notes. I was just mindlessly copying everything exactly as was written on the white board missing out on what my teachers said.

I stopped taking notes at this point and started paying attention instead. My grades improved. This might not work for everyone but something to try if you struggle retaining lecture content even as you take a bunch of notes.

> "Ever wonder why overcomplicated technical solutions are hyped so much? Why does everyone and their dog need to run Kubernetes? Why is it all Maschine Learning instead of good old fashioned methods that would do much better? Well those corporation have just the fitting cloud computing offering! "

Simpler explanation than some nefarious plan. Software engineers love to play with the coolest new thing over working with some proven solution that might have worked well enough. I think these corporation just exploit that with cloud offering. They don't really get to pick what people like (they try but suck at it) but have the money and resources to exploit whatever ends up being the popular new thing anyway.

Researchers usually have well research and evidence to back their claims which wouldn't put them at risk like Giuliani. Giuliani has also repeated these claims that have so far been unsubstantiated repeatedly even after being asked to retract them. There is some willful level malice implied in this lawsuit that is I think is not applicable to security researchers so I'm personally not worried but I do get the general sentiment whenever libel laws are brought up.

Football team coaching staff are almost like another team. Position coaches usually are ex players of that position but as you move up the chain it gets more into strategic management and thus by the HC level it's more of a manager role with architects underneath for offense and defense so less position technical knowledge more game knowledge.

I would bet it's just the influx of traffic post holiday with systems that haven't been updated in so long maybe some annoying memory leaks have crept up and gone unnoticed or some other bad state that was exacerbated by return to work day for most NA folks. Code freezes were good at identifying bugs that only show up after long periods.

Doubt anyone releasing big changes Monday morning.

You'll just end up with no SLA or pay a hefty amount to use services because that's an impossible standard to support for any service of a size like this.

I believe they can, comcast actually has injected javascript into websites in the past using a similar technique.

https://gizmodo.com/comcast-to-customer-who-noticed-it-secre...

It doesn't have to be a black and white a binary choice as you suggest. Maybe that's what you'd like because it makes the rule easier to grasp but it's possible to allow a threshold on how much they can interfere before things get to a point where a heavy handed solution like government involvement is needed to regulate them.

> "shut your call off"

I fail to see how those two are equivalent, shutting off would be removing the tweet, they did not do that. Labeling something is not equivalent to censuring the tweet or cutting off communication.

Warning users is similar to phones letting you know they think a caller is spam.

The part about having a genuine choice is basically ignoring the choice of not interacting with the website beyond reading the cookie message. I understand that it's a shitty choice but it's at least there. This essentially forces the site owner to provide content without it's side of the terms being allowed to be required.

Pay scales are idiotic on purpose to force the government to fail to hire required employees and pay 5 times as much by hiring a private sector company. This is all working as designed.

Observe how well and quickly new engineers come up to speed in your system. What problems do they hit? Think about them while designing. For example what hinders them from solving issues as they come up with customers.

Their experience in my view is a representation of the architectural complexity and cognitive load you are inflicting with your design.

That's a good question, a lot of the issues we hit now are mostly due to early assumption informed by our business requirements at the time that didn't hold true long term (argh blaming the business trope sorry). Our company being a a startup still learning market fit for our product went from being SASS first to doing mostly on prem and private cloud installations for example. That changes a lot of how I would have approached the design to reduce operational complexity had that been obvious early on.

Similarly, we did a lot of learning from the tools we used that is probably very much just something you earn with battle scars. For example the behavior and issues we hit with our choice of core stack components (celery, redis, rabbitmq, kubernetes,...) are often things you learn by using them and gaining experience.

The next thing is there were a lot of conscious tradeoffs that I would still argue we would take today. We prioritized speed of building features to make the product viable and attractive to customers at the expense of quality of those features and reliability. Doing the hard real world testing instead of relying on simple unit/integration tests before shipping. That's something we now are having to address but the question is was that something we should have done differently? No sure I would, we may not be around now if we hadn't built the feature we needed to sell the product and prove market viability.

On the topic of this video. I think the issue it not using microservices or building a monolith but controlling complexity. The biggest thing I dislike about our current infrastructure is the cognitive load and complexity that a new engineer joining has to deal with to be productive. That can happen in any architecture if you aren't careful. Sure having to run multiple services, tracing and testing acrross them (basically the usual gripes about microservice architectures) dealing with inter-service calls, performance tradeoff etc.. is not as good as I'd like it to be but it could be improved. What sucks most is there a lot of raw edges we left exposed that trip new people and that I think was a mistake we should be prioritizing fixing those as they come up and think of them while buidling up our core framework and components more thoroughly.

This was linked to me right after coming out of a meeting with my product team where I was the engineer in this video. Worse, I had a large hand in defining how our software architecture is designed so I can't even blame other people. It's largely my fault.