jecxjo

Well the President thinks it will go away when it's warm out. He is trying to play to stock market fears and is failing all of the citizens.

The three major things I did was automate everything, document everything and require justification in every task I do.

Whenever I had a task that recurred more than once, the second reoccurrence was when I implemented automation of that task. Didn't matter what it was or how much time it actually saved. The purpose was to have documented, reproducible results on any task I do. I often switched roles and then a year or two later I suddenly had to perform an old task I was "really efficient at." With automation i was able to do the task right away with almost no need to jog my memory.

Documentation requires you to get in the habit of writing. Doesn't have to be good, doesn't have to be smart and color coded. You just have to do it. I have vimwiki setup to a git repo and every discussion, every meeting, every project or note I took ends up here. Searching is easy enough and I don't have to worry about losing anything.

The last one deals with people so it requires tact. Whenever I'm asked to do a job that is a one off of something else or has additional work attached to it, I ask what the justification for the added engineering time would be. The point is to make me available for as much development as possible so if I'm stuck doing things that aren't actually needed it wastes resources. It also reduces complexity as there are minimal special cases for things.

You don't need to write a server to use it. You need to recognize you're using the wrong tool to solve your problem.

I've used SQLite as an embedded database, as a log file, it's even possible to use it as a virtual filesystem in tcl starkits. But a high demand, multiaccess data solution it is not. Yes you can make it work but you need to justify the costs of doing all that server work when you could just use a SQL server that already meets your needs.

For most PLC customers this is a no-go. They aren't in the market to save money on hardware. They save money by reducing downtime and eliminating failures. Without certifications for industrial control protocols (which take years and lots of engineering time to get passed), these will only be useful for those who don't really need a PLC.

My two year old can read numbers up to 10. It takes a little while to go from the symbol to the amount but generally speaking she can do it. It's typically around 2 where you can start to learn letters and numbers and basic counting.

I've found that while I can keep a lot in my head, my ability to prioritize doesn't maintain the life of the thoughts. Everything is some form of Todo list but they range from tasks I need to do to ordering my purchasing habits to fit within my financial constraints to listing books, movies and TV shows I want to watch. Working an 8 to 5 plus a side business with kids means my time is very limited. The less I need to remember the better and trying to go from work mode to relax mode needs to be as easy a transition as possible. Otherwise I just stay working.

No. What you're describing is the problem people have when teaching/providing insight/responding to questions online. They all use their current understanding and apply it to the question not assuming the other person has no knowledge of the subject.

Haven't you ever seen someone ask a question online that had a "newbie" answer that is generally correct, only to have a ton of people flood your response with all the caveats ignoring who their audience actually is. The default for most people is to use your current knowledge.

Whenever a non-technical person makes these claims I wish someone would standup and ask what sort of repercussions they believe would be acceptable for breaking the law and using the key illegally. Equifax royally screwed 147 million people, and no one did any time for it. Even if they had we'd be talking microseconds per person they screwed over.

It becomes unfathomable how huge of a problem this could cause and then when it happens it get swept under the rug and not a big deal. If the PM thinks its ok to have a key under the mat then I wanna know how much time he should be doing when someone gets my personal information and makes me have to deal with identity theft. Would 10 seconds of jail time for my life long struggle be acceptable? For the Equifax CEO that would have been half a year.

I wouldn't event say it was a cost issue. It was much more security through fences. When hardly any systems were connected together it was far more difficult for the non-authorities to access information, especially at the scale we are seeing today. You really needed to be able to infiltrate multiple systems simultaneously to get the kind of access you can now with a simple internet connection.

It makes the argument extremely ignorant when you realize we didn't have this problem in the past because it was just too difficult.

>they are willing to sacrifice their rights to ensure the laws on illegal information are enforced.

I think you meant to say "sacrifice everyone's rights." This isn't an opt in scenario, it would be your right to privacy being forcibly taken away.

The next question needs to be (assuming they feel it should be allowed) is do they feel there should be allowances for someone to be above this law? In our current climate we are seeing criminal looking behavior in the US by people within the Executive branch of the government. They have been citing Presidential Privilege but if mind reading became legal there would be multiple issues here.

This law would rid us of the last safe harbor, your own mind. At that point allowing some individuals the ability to skirt this law would create a class definition of ultimate scale. Those who are allowed to keep their own thoughts to themselves and those who aren't allowed to.

I always found them to be funny BECAUSE all they showed off was speed and a new camera. Past the first iPhone release much of the technology was already in Android phones before Apple. The whole "but we perfect the technology" was such a BS answer that I never really cared to see how Apple now had multi-touch, or Biometrics, or whatever else last year's tech you're adding it and charging crazy prices for.

Really just depends on what you wanted to specialize in. My degree is basically the VLSI portion of an Electrical Engineer and Operating Systems portion of a CS degree. There were many students in my HDL classes that were purely CS but had an interest in software based processors. Not as many EE's taking classes on Big-O notation.

Isn't the issue of being selective on who can view the content? If I, random Joe User views the publicly available content you have no issue. But if someone scrapes that data them you'd want to charge them. Unless I click on the ad, the act of using your bandwidth doesn't change based on who the viewer is. You'd want to apply fees based on the future use of the data rather than on your actual costs.

You basically have to look at the availability and cost of transport of the goods. Salt was abundant in the Dead Sea area so the need to import salt would have been pretty low.

As for the movement of writers, or the scrolls post creation, you'd look at where scripts were generated and where they sourced their materials. Just speculating, as I haven't read the background material on this new discovery, but it would make sense that the monasteries in Jerusalem would have a reproducible sourcing process since they would be generating manuscripts often. Same would go for monasteries around the Dead Sea.

I totally concur. It took me over a year, after being the lead developer for a decade with tons of technical and business experience. Thank goodness for digital resumes cuz I sent out at least 200. If it weren't for the fact that I had my current job down to a science, giving me a lot of free time to interview, it would have been impossible to find a new job.

I once has the most honest interviewer ever ask me:

> Where do you see yourself in 3 to 5 years?

I gave my typical response of technical lead, driving projects from the engineering side of things. His response was interesting.

> What would you think about not working here after 5 years?

The way they were able to run their shop was to use turn over to their advantage. They were custom software/hardware company that basically used as contract workers to make the widgets a company either has no time to make or doesn't know how to make. Their business model was to have you work on the project to the point where the contractor decides to hire you on full time to support the thing you helped make.

It was an interesting idea but showed they had no concept of stability for anyone besides upper management. Opted not to work there.

In this context I think they are the same.

Can I ask why?

I came from low level language background but my "fun programming" went from Lisps to MLs and now I have difficulties going back to Lisps for projects. Always wanted to like Clojure but never had a need for JVM in anything I worked on.

If you are writing in a Functional paradigm you'll most likely create a lot of small functions that perform very direct actions and then chain them all together to get a more robust operation. When I write Haskell I'll often annotate the larger functions and keep all the smaller ones to auto-generate. They will either determine the type based on the larger function's definition or by operations inside the smaller ones. No point in me writing an extra line for a one line function when its obvious the type.

I've been working my way through all the sci-fi and mystery radio shows on archive.org over the past few years and there have definitely been some cringe worthy material. Gender roles, racism, and excessive use of derogatory terms for just about any condition...wow was some of that stuff just horrible. Covering nearly 30+ years I can hear the world getting better the later you listen.

The start of your working relationship is really important. I'll get interview offers all the time and if the compensation is off by more than 3% I just tell them no, due to compensation. Usually I get a contact back asking what I was looking for and I just tell them that I am not in the market to be making my compensation an issue each time I want a raise. They had an idea what they wanted to pay and I am not who they are looking for.

>> People who currently have good jobs are unwilling to consider contract-to-hire

> In US, there is practically no difference between those three. You can be fired any day anyway. But yes, if you have a secure job that is good, the bar for switching is high, but so what? Why even switch? It's your choice then... Luxury problem!

It seemed weird to me that we are one of the only industries (well I guess engineering in general) who gets a contract that is contingent on each day until it is completed. At any given point you could be let go and yet if I contract someone to work on my home to legal work you setup a contract that states you owe them the money unless you are willing to go to court to contest their work.

When I last did a contract-to-hire it was basically "you can be let go for any reason, from slow output to your boss having a headache." Unless you get a sweet deal its difficult to pull a job with a set start / end time with guaranteed payout regardless of employment. I busted my hump at that last job so instead of doing my 6 months for the hire option they offered me the job before then 2nd month was over.

The thing I have never heard anyone talk about is what the repercussions should be for those asking for a back door when the door is used by malicious actors. We have seen companies like Wells Fargo commit company wide bank fraud...no one goes to jail. We have seen companies like Equifax lose millions of people's worth of personal and financial information...no one goes to jail.

When Barr and Trump push through legislation that requires back doors put into all our security, who is going to do jail time when all our personal information is leaked again? I try to put the least amount of info out there but when I do I use crypto that I know works, that I know who and how it was designed, who and how it was audited. When the government comes in and some intern loses a USB stick with keys to the back doors I wanna know who's head is gonna roll for it.

Do you have a better example from this code base? I'm looking but unfortunately I'm not seeing anything that isn't either trivial or just a lot of monad stack handling.

I worked for a large global company and this matched exactly what I was seeing. I had projects with year or more development cycles before something was deliverable so "meets expectations" was difficult when you had nothing to show for your work as they only cares about final results. We even had an unwritten rule where everyone must have at a minimum two "needs improvement" because "everyone should be working on making themselves better." This lead to a dark rabbit hole and a lot of engineers leaving.

With such a messed up evaluation process engineering demanded direct, documented process for doing evaluations. Instead we had managers trying to gauge output based on defects fixed and lines of code committed. You could tell management had no clue.

I've done so much air travel for work and would love to catch a train on the way back. But the fact that it costs such a ridiculous amount just doesn't work. The price really need to compete against driving your own vehicle. If you plan it right air travel can be very cheap, just wish I could afford taking a slow train on a Friday to be home in time for work Monday and cost me $100 or less

Where is the management of requirements? How do you force LTS versions? Or roll back if a version has a vulnerability? When things are automatic you are unable to stop bad things from happening.

I ran Pis at home for a bunch of services and I agree it did a great job. But when you put actual loads on it the device craters because they are so under powered. This is where THE issue is going to be. To get speeds you expect out of server hardware its not just about making a 64 core ARM. Single Core ARM vs Single Core x86 has an obvious winner. So you need to make node and .net core and python and everyone else really push their limits on using multiple cores without developers knowing about it.

But that is just the first step. You then need developers who write applications on top of those languages be multi-core aware and design their applications to fully use the huge number of cores. At that point you'll loose a lot of your power efficiency because you'll need a lot more hardware running to do the same tasks. You'll also need developers who know how to think in an extremely multi-core way to get the extra performance boost.

The part you're discounting is just how resource intensive desktop apps are and how much optimization goes into iOS apps.

To really see the benefit of changing they would need to add a lot of cores, and then cross their fingers that 3rd party app developers know how to do true multi-core development.